Istqb:
i. Hi-level design == c. System tests
ii. Code == a. Unit tests
iii. Low-level design == d. Integration tests
iv. Business requirements == b. Acceptance tests

Verification is Checking that we are building the system right

The test plan describes one or more levels of testing,
the test design specification identifies the associated high-level test cases and
a test procedure specification describes the actions for executing a test.

A standard for software testing terminology is BS 7925-1

Structural Testing may not mimic real world situations

1.Decision Table Testing == Y. A test technique which combines combinations of inputs that might not otherwise have been exercised during testing.
2.Decision Testing == Z. A form of control flow testing based on decision outcomes.
3.State Transition Testing == X. A test technique used which may be used to verify different system re depending on current conditions or previous history.
4.Exploratory Testing == W. Testing carried out w boxes to achieve specific test objectives, possibly to complement structured testing.

static:
iii.Data Flow Analysis.
vi Inspections.

dynamic:
i. Equivalence Partitioning.
ii. Use Case Testing.
iv.Exploratory Testing.
v. Decision Testing.

Which activities are included in the Test Analysis and Design phase?
Test case design that is based on an analysis of the behavior of the component without reference to its internal workings.

Structural testing can be performed at all test levels

MAJOR test implementation and execution tasks are
I. Repeating test activities
II. Creating test suites
III. Reporting discrepancies
IV. Logging the outcome

Following statements is true of testing:
a. Testing can show the presence of defects.
b. Testing reduces the probability of uncovered defects.
c. Testing can show that a previously present defect has been removed.

What factors should an organization take into account when determining how much testing is needed?
I. Level of risk
III. Project constraints such as time and budget

Bug report:
c. Priority (to fix).
d. Severity (impact on the system).
e. Expected Results.
f. Actual Results.
h. Failing software function.

Failure is Incorrect program behavior due to a fault in the program

--test plan:
Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.
--test design specification:
Documentation specifying the features to be tested and their corresponding test conditions.
--test procedure specification:
Documentation specifying one or more test procedures.

--project risk:
A risk that impacts project success.
--product risk:
A risk impacting the quality of a product.

c. Define the objectives of testing.
a. Create bi-directional traceability between test basis and test cases.
e. Comparing actual results with expected results.
b. Check test logs against exit criteria.
d. Check planned deliverables have been delivered.

low risk system = Use case testing and exploratory testing
high risk system == Decision testing.


keyword-driven testing approach
Action-words are defined to cover specific interactions in system (e.g., log-on entries) which can then be used by testers to build their tests

Implementation and execution
creates test suites for efficient test execution

development testing
To cause as many failures as possible so that defects in the software are identified and can be fixed

structural testing
b. It can include statement and decision testing.
c. It can be carried out at all levels of testing.

Operational acceptance test is USUALLY performed by system administrators
Decision Table Testing, State Transition and Use Case Testing are all black box techniques

Test cases for component testing are usually derived from component specifications, design specifications, or data models, whereas test cases for system testing are usually derived from requirement specifications, functional specifications or use cases.

Decision testing is a structure-based technique

incident report - IEEE Std. 829 - most important information
Impact, incident description, date and time, your name.

test management tool is needed
to build traceability between requirements, tests, and bugs.
to provide an interface to test execution tools.

Error guessing is best used:
After more formal techniques have been applied

structure-based testing techniques
are used both to measure coverage and to design tests to increase coverage

Test plan and test design specification
specify features to - be tested, approach, and pass / fail criteria

Testing cannot prove that software is correct.

IEEE Std 829-1998
incident report
b) Summary -- 5. Revision level
c) Incident description -- 1. Expected results
                        -- 2. Actual results
                        -- 3. Procedure step
                        -- 4. Environment
                        -- 6. Date and time

pilot phase for tool evaluation
Decide on standard ways of using, managing, storing and maintaining the tool and the test assets.

Black box test design techniques all have an associated test measurement technique

white-box testing
includes loop testing

A failure is:
Departure from specified behaviour.

software reusability
The extent to which the software can be used in other applications

Confidence testing == Smoke testing

The following code segment contains a potential "divide by 0" error.
Source code inspection

Institute of Electrical and Electronics Engineers

Functional testing is useful throughout the life cycle and can be applied by business analysts, testers, developers and users.

USUAL sequence for performing activities during the Fundamental Test Process
a. Analyze the test basis documents.
d. Establish the traceability of the test conditions
b. Define the expected results.
c. Create the test execution schedule.

benefit of fault attacks
They can evaluate the reliability of a test object by attempting to force specific failures to occur

Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place.

Fundamental test process
iv. Test Planning and Control
v. Test Analysis and Design
i. Test Implementation and Execution
iii. Evaluating exit criteria and reporting
ii. Test Closure activities

tools for developers
ii) Coverage measurement tools.
iv) Dynamic analysis tools.

Impact analysis assesses the effect of a change to the system to determine how much regression testing to do.

KEY test closure task
Finalizing and archiving testware.

Implementation and execution.
creates test suites for efficient test execution