Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 1 - Coggle Diagram
Chapter 1
1.3.Seven principles of Testing
1.Testing show presence of defects
Exhaustive testing is imposible
3.Early testing
4.Defect clustering
5.Pesticide paradox
6.Testing is context dependent
7.Absence of errors fallacy
1.2.Why is testing neccessary
1.2.1.Testing contribute to success
Rigorous test helps to reduce risks
Contribute to quality of software
Meet contract or regulatory
1.2.2.Quality Assurance and Testing
Quality: The degree to which a component or system satisfies the stated and implied needs of its various stakeholders.
Test case: A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
Test condition: A testable aspect of a component or system identified as a basis for testing.
1.2.3.Errors, defects, failures
1.2.4.Defects, root causes, Effects
Root cause: A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed
1.4.Test process
1.4.2.Test Activities and Tasks
Test Plan
Objectives:
Define objective of testing & approach
Maybe revisited based on feedback from monitoring and control activities
Includes:
information about the test basis
work products will be related
exit criteria
Test Monitoring
Included:
Test progress report
Test summary report
Refer to Test Plan, Test Execution
Objectives:
Compare planned test progress vs. actual test progress
Checking test results and logs against specified coverage criteria
Involves taking actions necessary to meet
the objectives of the test plan
Assessing the level of component or system quality based on test results and logs
Test Analysis
Evaluate the test-ability of requirement and system
Requirement specifications
Design and implementation information
The implementation of the component or system
Includes:
Defined and prioritized test conditions
Bi-directionally traceable
Test charters
Reporting of defects in the test basis
Test Control
Make decision
Take place during all activities
Initiate corrective actions
Provide information of testing
Test Design
Objectives:
Designing and prioritizing test cases
Identifying necessary test data
Define test environment, required infrastructure and tools
Work products:
High-level test cases
Bi-directionally traceable to the test
condition(s) it covers.
Test data, environment....
Test Implementation
Objectives:
Developing and prioritizing test procedure
Creating automated test scripts
Creating test suites
Arranging the test suites for efficient test execution
Verify that environment has set up correctly
Prepare and verify test data
Verifying and updating bi-directional
traceability
Work products:
Test data, test procedure, test suite, test execution schedule...
Test Execution
Objective:
Record IDs and versions of test object..
Compare actual result with Expect Result
Analyzing anomalies to establish their
likely causes
Reporting defects
Logging the outcome of test execution
Repeating test activities for abnormal case
Verifying and updating bi-directional
traceability
Work products:
Defect reports
Documentation about which test item(s), test object(s), test tools, and testware were involved in the testing
Test Completion
Objectives:
Checking whether all defect reports are
closed
Entering change request or product backlog for remain unresolved
Create Test Summary Reports
Finalizing test environment, test data, test infrastructure for later reuse
Work products:
Entering change request to Test Summary report
Action items for improvement of subsequent project or iteration
Change request or product backlog
Finalized testware
1.4.4.Traceability between the Test Basis & Test Work product: benefit
Analyzing the impact of changes
Making testing auditable
Requirement coverage (với các dự án đặc thù như Boeing cần ma trận này để tính toán mức độ đáp ứng chuẩ của phần mềm)
Improving the understand-ability of test process reports and test summary report
:warning:Test Basic: the body of knowledge used for Test Analyst and Design
:warning: Traceability between Test cases & requirement to provide report that test execution cover of the requirement
Test Closure activities
Finalizing and achieve testware
Checking which planned deliverable has been delivered
Analyze lessons.
1.1.What is testing
1.1.1.Typical objective of testing (10 items)
Evaluate work product
Verify specific requirement
Validate test object (product, user document)
Build confident
Prevent defect
Find (defects) as much as possible
No new defect introduced by changes
Provide information to make decision
Reduce risks of incorrect or untestable functionality being developed
Comply contracts & regulatory
1.1.2.Testing and Debugging
Testing:
Executing tests can show failure that are cause by defects in the software
Subsequent confirmation testing checks whether the fixes resolves the defects
Debugging:
Debugging is the development activity that finds, analyzes, and fixes such defects
Example:
Developers find and fix defects
1.5.The Psychology of testing
1.5.2. Tester & Developer mindset
Tester:
Curiosity, professional pessimism, a critical eye
Attention to detail
A motivation for good and positive communication and relationship
Ability to see what might go wrong
Developer
Difficult to find mistakes in their own work
Developer should be able to test their own code
More interested in designing and building solutions than in contemplating what might be wrong with those solutions
1.5.1.Human Psychology and Testing