Professional Documents
Culture Documents
1
Contents
ISTQB FOUNDATION LEVEL .............................................. Error! Bookmark not defined.
1.1.1 Test objectives ............................................................................................................... 3
1.2 Why is Testing Necessary?............................................................................................... 4
1.3 Seven Principles of Testing .............................................................................................. 6
1.4 Test Process (test activities) ............................................................................................. 7
1.5 Good communication ....................................................................................................... 8
CHAPTER 2. Testing Throughout The Software Development Lifecycle .............................. 10
2.1 Software Development Lifecycle Models ..................................................................... 10
2.2 Test levels ....................................................................................................................... 10
2.3 Test Types ...................................................................................................................... 11
2.4 Maintenance Testing....................................................................................................... 12
Chapter 3. Static Testing techniques ........................................................................................ 13
3.1 Static testing (Review and Static Analysis) .................................................................... 13
3.2 Review Process ............................................................................................................... 14
Chapter 4. Test design techniques ............................................................................................ 17
4.1 Category of test design ................................................................................................... 17
4.2 Black-box Test Techniques (Specification based/ Requirement based) ........................ 18
4.3 While Box test design (Structure based) ........................................................................ 21
4.4 Experience_base techniques ........................................................................................... 22
Chapter 5: Test Management.................................................................................................... 23
5.1 Test independence .......................................................................................................... 23
5.2 Test Planning and Estimation ......................................................................................... 24
5.3 Test Monitoring and Control .......................................................................................... 25
5.4 Configuration Management ............................................................................................ 26
5.5 Risks and Testing ........................................................................................................... 26
5.6 Defect Management ........................................................................................................ 27
Chapter 6: Tool Support for Testing ........................................................................................ 28
2
CHAPTER 1- FOUNDATION TESTING
Tip trả lời
Câu trả lời thường đúng Câu trả lời thường sai
Should be Must be, have to
May be Only
Can be All, full
Prove
Test methods
Verify ( verification) Validate ( validation)
- Compare with the first documents - Compare with user’s need or
expectations
- Do it right
- Do right it
3
Kỹ thuật review Requirement và make QnA: 5W1H
Kỹ thuật design test case: success và unsuccess ( valid và invalid)
Change
requirement
Fix bug X
X-
Regression
test
X
x x
X
4
1.2.2 Quality Assurance and Testing
5
(Incorrect in documents or source code)
1.2.4 Defects, Root Causes and Effects
Identify the root causes of failure (Error/ mistake) can:
Reduce the occurrence of similar defects in the future
Lead to process improvements that prevent a significant number of future defects
5. Pesticide paradox
If the same tests are repeated over and over again, no new defects can be found
6.Testing is context dependent
6
Testing is done differently in different context
Test analysis - Review and evaluate the test basis (make QnA)
7
- Identifying test conditions (list of features to be tested)
- Reporting defects
1.4.4 Traceability between the Test Basis and Test Work Products
- Analyzing the impact of changes
8
- Emphasize the benefits of testing
Developer Tester
Objective design and build a product verifying and validating the product,
finding defects prior to release
9
CHAPTER 2. Testing Throughout The Software Development Lifecycle
2 models:
10
Test basis Detailed design Global design requirement (OAT) by
Code specifications Administrator
Use cases
Use cases - Contractual and
regulatory
Environm Development Specific correspond to the acceptance testing
ent environment with environment production
framework, environment - Alpha and beta
debug tool,... testing:
(Can’t find Alpha testing is
operational performed at the
defects)
developing
organization’s site
Beta testing is
performed at
Customer’s
locations.
- Impact analysis may be done before a change is made, to help decide if the change
should be made
12
Chapter 3. Static Testing techniques
13
Review: Requirement defects, security), code Coverage,
Design defects, Incorrect memory leak
interface specifications,
14
Issue - Communicating Facilitator (moderator)
communication
- Analyzing - Run meeting
and analysis
- Evaluating Scribe (or recorder)
(Review
meeting) - Records new potential
defects
15
and defect reports - metrics are collected
- improve process
3.2.4 Ad hoc: Scenarios and dry Role-based or Checklist-based
Review runs: Perspective-based:
- little or no - List of questions from
techniqu
guidance - Better - Based on different past defects or
es
guidelines stakeholder standards
- dependent on
viewpoints
reviewer skills - miss other - Miss defects outside
defect types (e.g., checklist.
missing features)
16
Chapter 4. Test design techniques
17
4.1.2 Categories of Test Techniques and Their Characteristics
Black box test White box test Experience based
( Specification based or ( Structure based)
Requirement based)
- Design tests from documents - Design tests from how the - Design tests from
software is constructed knowledge or
experience
- Measure code coverage
- Find defects that was
miss by black box,
white box
- Formal or systematical - Formal or systematical - Informal
Process: Process:
19
Don’t case
Space is enough? - - F T
Output
Login success F F T T
Restricted turn on - - T F
20
1 Use case includes:
+ 1 basic flow (mainstream)
+ n alternate flow (exception)
+ some errors
Test case types
GUI Function Flow
Purpose Test each field or item on Test combination of inputs, Test end to end of
a screen events, pre-conditions system
- Xác nhận dữ liệu đúng Test environment
format, đúng định dạng corresponding to
hay chưa production
environment
Test level Integration test Integration test System test or system
integration test
Acceptance test
21
Statement coverage Condition coverage: % of condition outcomes
exercised.
Decision coverage
Condition decision coverage
Path coverage
Condition Determination coverage
LCSAJ
Multiple condition coverage
22
Chapter 5: Test Management
outsource
Testers external
Testers from
the business
Test team or organization
group
Other
developers or
Author testers within
developers test team
their own code
23
- Execute tests, evaluate the results
- Automate tests (decide, implement)
- Evaluate non-functional
- Review tests developed by others
24
5.2.3 Entry Criteria and Exit Criteria
Entry Criteria (smoke test) Exit Criteria
When to start a test level? When to stop a test level?
When to release?
How much testing is enough?
Check available (readiness): Check 5 criteria:
- Documents - Coverage ( thoroughness)
- Prior test levels met exit criteria - Defect (functional, non-functional:
reliability)
- Test environment
- Cost/ effort
- Test tool
- Time
- Test data
- (importance) Residual risks: issues/
open serious defect, untested.
25
+ Set an entry criterion for bug fixing
5.3.1 Metrics Used in Testing
Metrics can be collected during and at the end
of test activities in order to assess:
+ Progress
+ Quality
+ Approach
+ Effectiveness
5.3.2 Contents for Test Reports ( IEEE 829)
- Summary of testing
- Analysis
- (Variances) Deviations from plan
- Metrics
- (Evaluation) Residual risks
27
Chapter 6: Tool Support for Testing
6.1 Test Tool Category
Data files store test input and expected results data files store test input, expected results
in table or spreadsheet and keywords in table or spreadsheet
29