How to Misuse Code Coverage
暂无分享,去创建一个
In this paper, I'll use a somewhat more powerful type. Many commercial tools measure some variant of this coverage; few measure anything more powerful. Different people use different names for this type of coverage: "segment coverage", "multiple condition coverage", "branch coverage" (arguably incorrectly), and so on. I'll use "multiple condition coverage". It measures whether each logical condition in the code has evaluated both true and false (in some execution of the program, not necessarily in the same one). Suppose your code looked like this:
[1] Robert L. Glass,et al. Persistent Software Errors , 1981, IEEE Transactions on Software Engineering.
[2] P. M. Herman,et al. A Data Flow Analysis Approach to Program Testing , 1976, Aust. Comput. J..
[3] Elaine J. Weyuker,et al. Selecting Software Test Data Using Data Flow Information , 1985, IEEE Transactions on Software Engineering.
[4] J WeyukerElaine,et al. Selecting Software Test Data Using Data Flow Information , 1985 .