Branch Decision Path Statement Coverage

Statement Coverage is calculated when test cases cover all statement in logic.

Branch Coverage, aka decision coverage, covers both true and false conditions.

Path Coverage covers the distinct paths that the test cases could be.



In a word:

1. Branch coverage and Decision coverage are one and the same
2. 100% LCSAJ(Linear Code Sequence and Jump.) coverage implies 100% Branch/Decision coverage
3. 100% Path coverage implies 100% Statement coverage
4. 100% Branch/Decision coverage implies 100% Statement coverage
5. 100% Path coverage implies 100% Branch/Decision coverage

Detail, please refers to:

https://guide2mobiletesting.blogspot.co.nz/2016/08/istqb-easiest-way-to-solve-statement.html

ISTQB Exam Definition Part E

How much testing is enough should consider:
Level of risk
Project Constraints

Validation :
Check if we have build the right software 

Verification:
Check if we have build the software right 

Black-box testing technique:
Equivaance partioning
State Transition Testing
User Case Testing

Test Incident Report Standard: ISO829

Drivers also known as:
Test Harness
Scaffolding

Selection of test approach:
Risk of project
skill and experience of team
Objective of test endeavor

Configuration Management:
Status Accounting
Identification to test version
Record change to documentation over time
Control Library Access

Purpose of integration strategy for Integration in small
To specific which modules to combine & how many at once.

ISTQB Exam Definition Part D

Software Product Quality Standard:
ISO1926

Reviewing test basis is part of:
Test Analyze and Design

Exit Criteria:
Checking test logs
Assessing if more test required.
Writing test summary report.

Maintenance Test
Breadth Test
Depth Test

Majority of system error occurs in:
Requirement Phase

Checklist:
A series of probing quesitons about completeness & attributes about product system.

Common testing technique in component testing:
Statement & Branch Testing

Configuration Management tool:
Support trace ability, recording of incidents or scale-ability of tests.

Test Closure Activity:
Check deliverable achieved?
Finalize & Archive test ware
Analyze Lesson

High Level Plan includes:
Function to be tested
Environment required.
Entry & Exit Criteria

Error Guessing is:
Most appropriate way of deriving system test

Data-flow analysis studies:
The intrinsic complexity of the code.

ISTQB Exam Definition Part C

Work of Tester
Prepare & Acquire test data
Implement test on all test levels
Create test specification

Why Incremental integration over big bang?
Incremental integration has better early defects screening & isolation ability

Definition of test item standard: BS7925-1

Defect Management Includes:
Defect Prevention
Management Report

Configuration Management:
Identify Version of software under test
Controlling version of test ware items
Tracking changes to test ware items
Analyzing needs for new test ware items.

Purpose of Exit Criteria:
Determine when a test level complete

Decision table testing:
A test technique combines combination of impacts that might not otherwise have been executed during testing

Decision Testing:
A form of control flow testing based on decision outcome.

State Transition Testing
A test technique used which might be used to verify different system re depending on current conditions or previous history.

Exploratory Testing:
Test carried out x-box to achieve specific test objectives, possibly component constructed testing.

ISTQB Exam Definition Part B

Test Planning:
1.Determine test approach
2. Evaluate exit criteria reporting
3. Measure & Analyze result

Design test case order:
1. Analyze requirement & Specification
2. Elaborate & Describe test cases in detail
3. Specific expected result
4. Specific execution order.

Impact Analysis:
to determine how existing system might be affected by change

Configuration Management:
All test ware are identified & version controlled.

Formal Review Steps:
Planning
Kickoff
Preparation
Meeting
Rework
Followup

Dynamic Testing:
Equivalence Partitioning
Use Case testing
Exploratory Testing
Decision testing

Static Testing:
Data flow Analysis
Inspection

Software Quality Standard:  ISO1926

PDCA:   Plan Do Check Act

Cyclomatic Complexity =
Edges/Links - Nodes + 2* Independent paths  (L-N+2P)

Release Note= Item Transmittal report

Case Effect Graphing Standard:  BS7925-2

Test Design Phase:
Test Data
Test Data Plan
Test Procedure Plan


Measure Dysfunctions:
Even though numbers you look at appear better, to achieve the number people are doing other aspects of their work less well.

ISTQB Exam Definition Part A

Tools used by Developer:  Statistic Analysis, Dynamic Analysis

Tools used by Testers: Performance testing, Test Management, Test Running, Test Data Preparation 

Inspection--------Led by trained moderator/leader

Peer review-------No Management involved

Informal Review-----Undocumented

Walkthrough-------Led by author

Test Term Standard:  BS7925-1

When reporting bug to developer, tester should:

1. Be Police

2. Firm about insisting a bug not feature

3. Diplomatic, sensitive

Component test standard: BS7925-2

Test control-------- re-allocating of resources when test overrun

Test monitoring------report on deviation from test plan

Test estimating ------ calculating of required resources

Incident-management-----track of conclusion test result

Configuration control----maintenance of test record

System testing:

1. Often performed by independent team

2. Functional

Oracle Assumption:

tester can routinely identify correct outcome of test

White-Box testing

a) Statement testing

b) Path Testing

c) Dataflow testing

Failure is :  departure from specific behaviour