The collateral coverage of data flow criteria when branch testing

Information and Software Technology

Volumn 48, Issue 8, 2006, Pages 676-686

  Malevris, N ^a   Yates, D F ^a  

^a ATHENS UNIVERSITY OF ECONOMICS AND BUSINESS   (Greece)

Author keywords

Branch testing; Collateral coverage; Data flow testing; Infeasible paths

Indexed keywords

CODES (STANDARDS); COMPUTER PROGRAMMING;

BRANCH TESTING; COLLATERAL COVERAGE; DATA-FLOW TESTING; INFEASIBLE PATHS;

DATA FLOW ANALYSIS;

EID: 33646888400     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.infsof.2005.07.006     Document Type: Article

References (35)

1. Beizer B. Software System Testing and Quality Assurance (1984), Van Nostrand Rheinhold, New York
2. Bertolino A., and Marre M. How many paths are needed for branch testing?. Journal of Systems and Software 35 2 (1996) 95-106
3. Brown J.R. Practical application of software tools. TRW report TRW-55-72-05, TRW Systems, One Space Park, Redondo Beach, California (1972)
4. Chaim M.L., Maldonado J.C., and Jino M. A debugging strategy based on the requirements of testing. Journal of Software Maintenance 16 (2004) 277-308
5. Clarke L.A., Podgurski A., Richardson D.J., and Zeil S.J. A Comparison of Data Flow Path Selection Criteria Proceedings of the 8th International Conference on Software Engineering (1995) pp. 244-251
6. P. Depak, http://www.programmersheaven.com.
7. European Space Agency (ESA) Software Engineering Standards. ESA PSS-05-0 Issue 2, European Space Agency (ESA), 8-10, rue Mario-Nikis, 75738 Paris Cedex, France, 1991.
8. Frankl P.G., and Deng Y. Comparison of delivered reliability of branch, data flow and operational testing: A case study. ACM - ISSTA'00, Portland, Oregon (2000) pp. 124-134
9. Frankl P.G., Hamlet R.G., Littlewood B., and Strigini L. Evaluating testing methods by delivered reliability. IEEE Transactions on Software Engineering 24 8 (1998) 586-601
10. Frankl P.G., and Weyuker E.J. An applicable family of data flow testing criteria. IEEE Transactions on Software Engineering 14 10 (1988) 1483-1498
11. Frankl P.J., and Weyuker E.J. Provable improvements on branch testing. IEEE Transactions on Software Engineering 19 10 (1993) 962-975
12. Gabow H.N., Maheshwari S.N., and Osterweil L.J. On two problems in the generation of program test paths. IEEE Transactions on Software Engineering SE-2 (1976) 227-231
13. Herman P.M. A data flow analysis approach to program testing. Australian Computer Journal 8 3 (1976) 347-354
14. Jorgensen P.C. Software Testing - a Craftman's Approach (1995), CRC Press, New York
15. Kernighan B.W., and Plauger P.J. Software Tools in Pascal (1981), Addison-Wesley, Reading, MA
16. Koutsikas C., and Malevris N. A unified symbolic execution system. Proceedings of the ACS/IEEE International Conference on Computer Systems and Applications, Beirut (2001) pp. 466-469
17. Laski J.W. On data flow guided program testing. SIGPLAN Notices 17 9 (1982) 62-71
18. Laski J.W., and Korel B. A data flow oriented program testing strategy. IEEE Transactions on Software Engineering 9 5 (1983) 347-354
19. Liang D., and Harrold M.J. Equivalence analysis, A general technique for improving the effiency of data-flow analyses in the presence of pointers. ACM SIGPLAN/SIGSOFT Workshop on Program Analysis for Software Tools and Engineering (PASTE'99), Toulouse, France, September (1999) pp. 39-46
20. N. Malevris, An assessment of the number of paths needed for control flow testing. 3rd International Conference on Reliability, Quality and Safety of Software-Intensive Systems (ENCRESS'97), Athens, Greece, pp. 32-43.
21. Malevris N., Yates D.F., and Veevers A. A predictive metric for the likely feasibility of program paths. Information and Software Technology 32 2 (1990) 115-119
22. Nguyen T.B., Delaunay M., and Robach C. Testing Criteria for Data Flow Software Proceedings of the IEEE Tenth Asia-Pacific Software Engineering Conference (APSEC'03) (2003) pp. 332-339
23. Ntafos S.C., and Hakimi S.L. On path cover problems in digraphs and applications to program testing. IEEE Transactions on Software Engineering SE-5 5 (1979) 520-529
24. Paige M.R. On partitioning program graphs. IEEE Transactions on Software Engineering SE-3 6 (1977) 386-393
25. Rapps S., and Weyuker E. Data flow analysis techniques for test data selection. Proceedings of the 6th International Conference on Software Engineering, Tokyo, Japan (1982) pp. 272-278
26. Rapps S., and Weyuker E. Selecting software test data using data flow information. IEEE Transactions on Software Engineering SE-11 4 (1985) 367-375
27. Requirements For Safety Related Software in Defence Equipment, Part 1. Defence Standard 00-55(PART 1)/Issue 2, Ministry of Defence, UK, 1997.
28. Roper M. Software Testing (1994), McGraw-Hill, Cambridge
29. Standard for Software Component Testing. British Computer Society Special Interest Group in Software Testing (BCS SIGIST), UK, 2001.
30. Testbed, LDRA Software Technology, Portside, Monks Ferry, Wirral, UK.
31. Woodward M.R., Hedley D., and Hennell M.A. Experience with path analysis and testing of programs. IEEE Transactions on Software Engineering; SE-6 (1980) 278-286
32. Woodward M.R. An investigation into program paths and their representation. Techniques et Science Informatiques 3 (1984) 273-286
33. Yates D.F., and Hennell M.A. An approach to branch testing. Proceedings of 11th Workshop on Graph Theoretic Techniques in Computer Science, Wurtzburg, West Germany (1985) pp. 421-433
34. Yates D.F., and Malevris N. Reducing the effect of infeasible paths in branch testing. Proceedings 3rd Symposium on Software Testing, Analysis and Verification (TAV3), Key West, Florida, USA (1989) pp. 48-56
35. Yates D.F., and Malevris N. The effort required by LCSAJ testing: an assessment via a new path generation strategy. Software Quality Journal 4 3 (1995) 227-243