ISTQB review P1

Question 1

Test Cases

Answer 1

-test cases describe how the software should work under normal, abnormal, and error operating conditions and are written as a set of instructions for testers

-process flows/descriptions detailing the typical use of the system

Question 2

Equivalence partitions

Answer 2

are a black box technique that allows testers to group input data into sets or classes so there are less test cases and you still get comprehensive coverage

Question 3

Experience based test design

Answer 3

a. based off a user’s experience and is best used when you don’t have time for a more structured approach and the requirements aren’t good enough or you don’t have any, and there is limited knowledge on the product
b. 1/3 types - error guessing where the tester focuses on the places prone to error
c. 2/3- checklist based where the person goes through a list of main functions that should be expected
d. 3/3 exploratory testing- where you just play around with the app and use basic life experience to see if you can comfortably use it

Question 4

Test planning vs test execution

Answer 4

test planning ensures testing is efficient and effective and test execution ensures the testing is thorough and that the product can be released

Question 5

User acceptance testing

Answer 5

a. is also called
i. beta testing where the
b. product is tested in real life by its intended audience or business reps

Question 6

Reliability of a product vs the quality

Answer 6

quality testing is if the product works at all, and how well it works, reliability and durability testing is how well the product will hold up, like how long, in what conditions

Question 7

Integration testing test level

Answer 7

is the 2nd level of testing after unit testing and is when you check how components or units of the software work together the way they should. Unit testing checks small pieces of code

Question 8

Test basis

Answer 8

the source of information or the document needed to write test cases and for test analysis

Question 9

Test leader vs tester

Answer 9

Test leader would:
create the test strategy and write the test summary report.
The tester would create the test specification and raise an incident report.

Question 10

Test strategy vs - test specification

Answer 10

the test strategy comes from the Business Requirement document (BRS) vs the software requirement specification (SRS) for the test plan. It’s a live document that gets updated as more information becomes available. The test strategy document is also called a Static document. It’s more vague than the SRS and is for the stakeholders. Test specification
focuses on scenarios and is a detailed summary of what scenarios will be tested, how they will be tested, how often they will be test etc for each feature.

Question 11

Decision table testing

Answer 11

design test cases based on the combos of inputs and outputs for a system or component. Black box technique

Question 12

Statement testing

Answer 12

ensures each line of code for that function Is executed at least once, covering each path from the source code. White box technique

Question 13

State transition testing

Answer 13

analyzes how the application behaves based on different input conditions.

It’s good when there are not that many input value options

the system depends on previous values.

Black box technique

Question 14

Equivalence testing

Answer 14

Using equivalence partitions

Question 15

Component testing

Answer 15

tests individual components separately from other components. It can be done white box or black box

Question 16

Fault attacks

Answer 16

causing an error on purpose to see what happens

Question 17

Black box techniques and why it’s useful

Answer 17

black box techniques check beyond functionality and gives more insight on how a function is completed, and if it’s usable, and easy to understand

Question 18

Project life cycle models

Answer 18

Sequential, iterative-incremental approach, waterfall, agile

Question 19

Sequential project life cycle model

Answer 19

means the following phase starts only when the previous phase is complete

The sequential methodology first discovers all steps in the analysis plane, followed by all steps in the design plane, followed by all steps in the implementation plane, and then followed by all steps in the testing plane. This can be accomplished because the environment is static and finite.

Question 20

Iterative-incremental approach

Answer 20

iterative approach is when the project is broken into fully working parts, incremental is when they work on everything enough to release it, but not till it’s perfect so you end up not building the whole thing at once

These parts, or iterations, are fully developed and tested in cycles, allowing for modifications after each completion

Question 21

Waterfall

Answer 21

is the most structured with time tables. It’s the most traditional and linear.

Follows a sequential and linear process. It consists of distinct phases: planning, requirements gathering, system design, implementation, testing, and deployment.

Question 22

Agile

Answer 22

i. is also known as the
1) adaptive life cycle
ii. and combines iterative and incremental
I think the agile part is the part where things are repeated till they are fixed, the iterative part

Question 23

Master test plan

Answer 23

document that describes how the testing will be handled and gives a birds eye view of how the testing will be handled across different levels

Question 24

Test objects

Answer 24

the product, system, module, functionality, or even line of code that is being specifically tested.

Question 25

Decision table testing

Answer 25

software testing method where you test the system based on input combos

Question 26

Configuration management

Answer 26

when you identify the parts that make up the software or system and then making sure each part is managed well during the product life cycle

How changes are handled systematically so a system keeps its integrity relating to performance, function, physical attributes, and requirements

Question 27

Traceability

Answer 27

the ability to trace tests forward and backward in the development life cycle. You are able to link a test to a set of requirements in the test case confirming that it works

Question 28

Test artifacts

Answer 28

Test artifacts(test deliverables) are documents and scripts created during software testing to ensure that the tested application meets the desired quality standards. These artifacts provide evidence of the testing process and valuable insights into the overall testing efforts

Question 29

Test analysis

Answer 29

Test analysis inspects and analyzes the test artifacts to create test conditions or cases. Test analysis aims to collect requirements and create test objectives to establish test conditions. As a result, it’s also known as Test Basis

Question 30

See example of test basis

Answer 30

System Requirement Document (SRS)
Functional Design Specification.
Technical Design Specification.
User Manual.
Use Cases.
Source Code.
Business Requirement Document (BRD)

Question 31

If user acceptance testing is beta testing, is there something called alpha testing?

Answer 31

Alpha testing is done by internal developer and QA teams, with its main goal being to ensure that the software is functional, reliable, and free of any defects or errors. Alpha testing generally attempts to simulate real user behavior by using black and white box testing techniques

Question 32

Types of white box testing

Answer 32

1. Statement testing
   2. Branch coverage
   i. This checks every possible path
   3. Decision
   4. Condition coverage
   5. Multiple condition coverage
   6. Finite state machine coverage
   7. Path coverage
   8. Control flow testing
   9. Data flow testing
   10. Penetration testing
   i. Used to expose security threats
   11. Mutation testing
   Used to find the best coding techniques for a software solution

Question 33

Positive and Negative input test values

Answer 33

Positive testing determines that your application works as expected. If an error is encountered during positive testing, the test fails. Negative testing ensures that your application can gracefully handle invalid input or unexpected user behavior

Question 34

What is test control

Answer 34

Test Control occurs based on the results of Test Monitoring. It refers to taking corrective action based on test monitoring reports to improve quality and efficiency. Some examples of test control activities would be: Prioritize testing efforts in a different way. Reorganize test schedules and deadlines

Question 35

Decision table testing: unit component or integration level

Answer 35

Component

Question 36

Statement testing: unit component or integration level

Answer 36

Component

Question 37

State transition coverage: unit component or integration level

Answer 37

Component

Question 38

Equivalence partitioning: unit component or integrative

Answer 38

Component