1_Chapter Flashcards
To learn first chapter
Software testing
is a way to assess the quality of software and reduce the risk of software failure in operation
A common misperception
- Testing only consist of execution of test
2. Testing only verify product
Objectives of testing
- To evaluate work products such as requierments, code, design, user stories
- To verify that all requirments have been fullfilled.
- To validate that test object is complete and works as the users and stakeholders expect
- To build confidence in level of the quality of test object
- To prevetn defects
- To find failure and defects
- To give sufficient informantion to stakeholders, to allow them to make informed decision about the level of quality
- To reduse the level of risk of inadequate software quality
- To comply with regularatory, legal, contractual requirments or standarts and to verify the test object’s compliance with such requirments or standarts
Seven testing priciples
- Testing show presence of defects, not that system free from bugs
- Excaustive testing is impossible
- Early testing or shift left testing
4 clustering of bugs
5 pestecide paradox
6 testing is contex dependant
7 error absence fallacy
Debugging
is the development activity that finds, analyzes, and fixes such defects
Test process
- Test planing
- Test monitoring and control
- Test analysis
- Test desighn
- Test implementation
- Test execution
- Test completion
Activities of Test planing
- define the objectives of testing
- define approaches for meeting test objectives within constraints imposed by the context
documents: Test plans
Activities of Test monitoring and control
- on-going comparison of actual progress against the test plan, using any test monitoring metrics defined in the test plan
- taking action necessary to meet the objectives of the test plan
documents: Test progress reports
Activities of Test Analysis
- Analyzing test basis
- Finding defects
- Define features and sets of features to be tested
- Define and prioritizing test conditions for each feature based on analysis of the test basis
- Capturing bi-directional tracebility between each element of the test basis and teh associated test conditions
Test conditions
the aspect of test basis, that is relevant to order to achieve specific test objectives
Test suite
A set of test cases or test procedures to be executed in a specific test cycle
Test case
A set of preconditions, inputs, actions, expected results and postconditions, based on test procedures
Test procedure
A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution.
Activities of Test design
- Designing and prioritizing test cases and sets of test cases.
- Identifying necessary test data to support test conditons and test cases
- Designing test environment and identifying any required infrastructure and tool
- Capturing bi-directional tracebility between test basis, test conditons, test cases, and test procedures
Activities of Test Implementation
- Developing and prioritizing test procedures, and potentially creating automated test scripts.
- Creating test suites
- Arranging test suites withing the test schedule
- Building test environment
- Preparing test data and ensuring it is properly loaded in test environment
- Capturing bi-directional tracebility between test basis, test conditions, test cases, test procedures, test suites