Fichas
Software testing strategies: Summary
Fichas del conjunto (30)
- 1What are testing objectives?Classed into 2 types,
direct and indirect - 2What are the 2 types of testing strategies?Big bang testing and incremental testing
- 3What is the direct testing objective?Identify/reveal as many errors as possible
Bring to acceptable quality level
Perform required testing in an efficient and effective way, within budget and scheduling limitations - 4What is the indirect testing objective?To supply records of software errors to be used for error prevention.
- 5What is Big bang testing?Tests the software as a whole, once the completed package is available.
- 6What is incremental testing?tests the modules one by one
- 7What are the 3 things incremental testing do?Unit, Integration and system testing
- 8What are Unit tests? (incremental testing flow)software modules are tested as they are completed
- 9What are Integration tests? (incremental testing flow)Followed by groups of modules composed of tested modules integrated with newly completed modules
- 10What is a System test? (incremental testing flow)Once the entire package is completed, it is tested as a whole
- 11Big bang testing strategy cons?Bad for programs that aren't small and simple.
Identification of errors in entire software package when perceived as one 'unit' is difficult and not effective.
Perfect error correction takes time.
Resources/schedule testing estimates are fuzzy. - 12Incremental testing pros?Performed on relatively small software units, so yields higher percentages of identified errors and facilitates their correction.
- 13Big Bang or incremental?Incremental is preferred
- 14What is top-down testing strat?- First module tested is the main module, the highest level module in the software structure;
- Last modules to be tested are the lowest level modules. - 15What is bottom-up testing strat?Bottom up is reversed top-down
- Lowest level modules are tested first
- Main module tested last - 16Bottom-up pro + con?pro: Relative ease of performance
con: Lateness of stage at which its possible to observe the program as a whole. - 17Top-down pro + con?pro: Early stage to demonstrate the program as whole, a condition that supports early identification of analysis/design errors.
con: The comparative difficulty of its performance. - 18What is black-box testing?Identifies bugs only according to malfunctioning of the software as revealed from its outputs, while disregarding the internal paths of calculations performed by the software.
- 19What is white box testing?Examines the internal paths of calculations in order to identify bugs.
- 20Advantages of black box?Allows tester to carry out almost all test classes.
For test classes that can be carried out by both white and black box testing
black box testing requires considerably fewer resources. - 21Disadvantages of black box?Allows for identification of coincidental errors as correct.
Lacks control of line coverage.
Lacks possibilities to test the quality of coding work. - 22Advantages of whitebox?Direct statement-by-statement code checking = better checking, e.g. if algos were correctly coded
Performance of line coverage follow-up with non-executed LOC. Test cases then can cover these.
Ascertains coding work quality+coding standards. - 23Disadvantages of white box?Vast resources utilised, more than black box testing of same software.
Inability to test software performance in terms of availability (response time), reliability, load durability, and other testing classes related to operation, revision and transition factors. - 24What is path coverage?Percentage of possible paths of software processing activated by the test cases.
Applicable for estimating white box testing coverage only - 25What is line coverage?Percentage of executed lines of code examined during the tests.
Applicable for estimating white box testing coverage only - 26How can we achieve full path coverage?Use path and line coverage with white-box testing, to try.
But achievement of full path coverage is impractical because the scope of resources required for its implementation. - 27What are the 3 types of black box tests?There are 3 factor testing classes:
- Revision
- Operation
- Transition - 28What are the 3 Revision factor testing classes for black box testing?(1) Maintainability [tests]
(2) Flexibility
(3) Testability - 29What are the 8 operation factor testing classes for black box testing? DA-Roosts(1) Documentation [tests]
(2) Availability
(3) Reliability
(4) Output correctness
(5) Operational usability
(6) Stress tests
(7) Training usability
(8) Software system security - 30What are the 4 Transition factor testing classes for black box testing? REPS(1) Re-usability [tests]
(2) Equipment interfacing
(3) Portability
(4) Software interfacing
Información
- Descripción
- BsC computer science Fichas sobre Software testing strategies: Summary, creado por harrymt el 15/01/2016.
- Creado por
- harrymt
- Visitas
- 170
- Valoración