Please enable JavaScript.
Coggle requires JavaScript to display documents.
ISTQB - Chapter 1 - Coggle Diagram
ISTQB - Chapter 1
Errors, Defects, Failures, Root Causes
- Human makes errors (mistakes), which produce defects (faults,bugs), may result in failures
- Root cause: nguyên nhân gốc rễ
- Root cause analysis can helps reduce similar defects in future
- Faults positives: not really a bugs
- Faults negative: not be detected
Test principles
- Testing shows the presence of defects, not their absence
- Exhaustive testing is impossible (Testing everything is not feasible except for trivial cases. Test techniques, prioritization, risk based testing be used to focus test efforts)
- Early testing save time and money
Shift left
- **Defects cluster together
- Test wear out - pesticide paradox
- Testing is context dependent
- Absence of defects fallacy** (System does not fulfull users'nees is not successful)
Test Activites and Tasks
Test planning
define test objective, exit criteria (Define of done DOD)
select test approach
-
Test Analysis
- Test basic: input for analysis (spec, requirement...)
- Test condition: output of analysis/ something can be tested
- Capture bi-directional tracaebility between test basis and test connditions
Test design
Design test cases, test data requirements, test enviroment, required infrastructure and tools
Test execution
Run tests, compare actual result and expected, analyze anomalies, log test results, defect reports
Test completion
- Sumary report, handing over, shuting down (archiving) test enviroment, lesson learned, improve test process
- Ocur at project milestones (release, and interation, test level completion
Test implementation
- Out put: test procedure, test suites, test script, test execution schedule, prepare test data, tbuild est enviroment (test harnes, simulator)
- Create testware necessary for test execution
- High level test case: abstract: chung chung
- Low level test case: concrete value, detailed descriptions : cụ thể
Traceablity
Support:
- analyze impact of changes
- make testing auditable
- meet IT criteria
- make test progress and completion reports more easily understandable
- comunicate technical aspercts of testing to stakeholders understabdbly
- provide information to assess product quality, process capability, projject progress again business goals
Testing roles
- Test management role: take respon for test process, test team and leadership, test planning, monitoring and control, test completion
- Testing role: technical aspect: test analysis, design, implemen, execution
Essential skills
- Bring bad new-> blame tester -> communication skills in constructive way
- Testing knowledge
- Thoroughness, carefulness, curiosity, attention to details, being methodical
- Analytical thing king, critical thinking, creativity
- Technical knowledge
- Domain knowledge
Independence of testing
Degree:
author < person from same team < testers outside team but within orgaiization < testers outside organization
Benefit:
- different kinds of failures
- different perspectives, biases
- verify assumptions made by stakeholders
Drawbacks:
- Isolated from team
- Lack of collaboration
- Devs may lose sense of responsibility
- Testers may be seen as a bottleneck, blamed for delays
Why testing neccessary
- Testing: a form of quality control, helps in achieving the agreed upon goals (scope, time, quality, budget)
- May be required to meet contractual or legal requirements...
Các khái niệm
- Test object: đối tượng test
- Test objective: mục tiêu test
- Verification: checking whether system meets specified requirements
- Validation: checking whether system meets user's and other stakeholder's needs
- Dynamic test: execute component/system
- Static test: not execute, includes Review and Static analysis
- Testing: not only technical activities
Test objective
- Evaluating work products (prevent defects)
- Finding defects
- Building confidence in the quality (aceptance test)
- Provide sufficient information to make decisions
- Reducing level of risk
- Verify whether requirements have been fulfilled
- Validate test object work as expected by the stakeholders
Testing and debugging
- Testing: Trigger failures and directly find defect
- Testing identifies a defect, debugging removes it
- Confiirmation test: check whether the fixes resolved the defects
- Regresstion test: check whether the fixes causing failures in other parts
- In Agile, tester may involve in debugging and component tesing
Debugging
- is development activities, not testing activities
- finds causes, analyzes and fixes defects
Debugging process:
- Reproduction of a failure
- Diagnosis (finding root cause)
- Fixing the cause
Contributions to success
- Provide a cost-effective means of detecting defects, indirectly contribute to higher quality test objects
- Provide a means of directly evaluating the quality
- Provide users with indirect representation on the development project
Ensure understanding of user's needs
- May be required to meet contractual or legal requirements, requlatory standards
Testing and QA
QA
- QA (quality assurance) focus on proper processes, process-oriented to generate a good product, contribute to prevent defects
- QA applies to both development and testing processes
- Retrospective meeting: analyse root cause, remove them, improve processes
QC/ tester:
- Testing is a form of QC
include formal methods,simulation and prototyping
- QC: product-oriented, achievement of appropiate levels of quality