Chapter 1 Flashcards
Test basis
Documents which requirements for components are inferred
Test item
Individual elements to be tested several built together create a test object
Test object
Components or system to be tested
Test objective
Reason or purpose for designing and executing tests
Test condition
Item or event of a component or system that could be verified by one or more test cases
Error
Human action that produces an incorrect result
Defect/bug/fault
Flaw in component or system that can cause component or system to fail to perform required function
Failure
Deviation of the component or system from expected delivery, service or result
Planning/Control
- Determine the test objectives, risk and scope
- Determine the test approach
- Determine the required test to resources
- Identify and interface the test teams
- Implementation of organizational test policy and strategy
- Schedule test activities
- Determine the exit criteria
Analysis/Design
- Reviewing the test basis
- Designing and prioritizing a high level test cases
- Identifying necessary test data to supporting the test conditions and test cases
- Designing the test environment set up including identification of tools and infrastructure
Implementation/Execution
- Implementing in prioritizing the test cases
- Prioritizing test procedures and creating test data
- Enhancing execution by organizing test procedures into test suites
- Verify the test environment has been set up correctly
- Executing test procedures both manual and automated
- Logging the outcome of execution known as test log
- Comparing actual results with expected results
- Reporting discrepancies as incidents
- Re-execution of a failed test
Evaluating Exit Criteria/Reporting
Closure activities occur at project milestones
- Analyze lessons learned
- Ensuring turnover of planned deliverables
- Closure of incident reports
- Documenting acceptance of the system
- Finalizing and archiving testware, environment and infrastructure for later use
Product Risk
Risk directly related to test object meaning risk related to component or system
Project Risk
Risk related to the management and control of the project
What are the 7 principles of testing?
- Testing only shows the presence of defects
- Complete and exhaustive testing is impossible
- Early and effective testing starts with requirements
- Defect clustering is when a few modules have the most defects focus testing there
- Pesticide paradox eventually the same testing goes stale constantly revise to avoid
- Testing is context dependent risk of failure influences where to test
- Absence of errors fallacy fixing all defects doesn’t warrant usability or a working product