Software testing fundamentals

Résumé du document

Cours guidé avec des exercices de la matière Software testing pour la spécialité informatique : white box, black box, LCSAJ, Data flow criteria et FSMIO testing.

Extraits

[...] E. Weyuker. Axiomatizing Software Test Data Adequacy. IEEE Transactions on Software Engineering, 1128–1138, Dec Rothermel, G. and Harrold, M.J., Analyzing Regression Test Selection Techniques. IEEE Transactions on Software Engineering Aug Lee, D., Yannakakis, M. Principles and methods of testing finite state machines-a survey. Proceedings of the IEEE, vol.84, no.8, pp.1090-1123, Aug 1996. P. G. Frankl , E. [...]

[...] Automating test oracles is a problem that has not a general solution. Moreover, building a “perfect” automatic oracle for a program P is as complex as building P In practice, the test designer must specify the expected result for every test case. The expected result can be approximated (“no matter what happens, the plane must remain to an altitude higher than 1000 meters”). Test program IUT Oracle verdict Figure 2 : Test oracle for reactive systems 2. White-box test selection criteria White-box test adequacy criteria are related to IUT code. [...]

[...] A well-known empirical assessment technique is mutation testing. What we actually want to know is if a test can find more faults than another or if choosing a criterion A will result in finding more faults than choosing a criterion B (that is, if tests satisfying A have a higher faultrevealing power than those satisfying B). But to know that, we should know all the faults in the program (and this is not usually true Mutation testing is an answer to this problem based on “fault injection” (this technique is well-known in hardware components testing). [...]

[...] For any level, tests may have several different objectives. Even if we very often test for functional correctness, many other test objectives can be considered: installation testing, alpha/beta testing, conformance testing, reliability testing, regression testing, performance testing, load testing, configuration testing (see the SWEBOK for definitions). Regression testing is a particular useful activity aiming at ensuring that a change in the software does not cause any loss of functionality. An interesting reading is A more complete survey of regression testing techniques is provided in [11]. [...]

[...] A variable use can occur in a condition while in which case it is a p-use as predicate) or in a computation (c-use). A def-clear sub-path for variable x contains no definition of x. For instance, in the program of Exercise the sub-path 6-9-10-13 is def-clear for variable sign but 6-7-8-9 is not. The resulting criteria are: - All-defs: execute a def-clear sub-path between every variable definition and one of its uses. - All-p-uses: execute a def-clear sub-path between every variable definition and every use of this variable in a predicate. [...]