【正文】 k 的隨之而來的方法，該方法具有第一利用 V 的一個節(jié)點。這個問題對于測試人員，那么，以確 定哪些標(biāo)準(zhǔn)來選擇一個特定的情況。最后，C 類包括方法命令狀態(tài)變量 v。當(dāng) T 是 A，則實際調(diào)用是到 A:: m 和 A:: n。但考慮其中 o 的類型為 C 的情況，方式 C:: m 定義了一個 A :: v，但不是 A :: u。困難之處在于，有一個必須被考慮為給定的方法，這取決于動態(tài)綁定的存在，并可能發(fā)生的可能的多態(tài)性的多個圖形表示。雖然技術(shù)已被開發(fā)，它可以識別在大多數(shù)情況下用于突變檢測，傳統(tǒng)的數(shù)據(jù)流測試，和路徑的測試技術(shù) [20]是不可行的路徑，該問題一般是不可 判定。 2 在 C ++作用域解析運算符 ::用于指示哪些方法和狀態(tài)變量都被提及。合同規(guī)定在一個類中的每個公共方法的前提條件和后置條件。他們通過，形成了系統(tǒng)類的集合定義路徑。（ 2）跨法檢測 。第一，全綁定，要求每個對象的每個可能的結(jié)合可以至少被執(zhí)行一次，并且進(jìn)一步結(jié)合所有可能的組合，當(dāng)表達(dá)式包含多個對象進(jìn)行測試。我們的方法考慮這一點，同時也相當(dāng)重視對測試所造成的 MUT 內(nèi)進(jìn)行方法調(diào)用之間發(fā)生的相互作用。 目前我們正在建設(shè)的概念證明的覆蓋分析工具來支持這種技術(shù)。 Reliability, 6(3/4):125– 252, September/December 1996. [8] MeiHwa Chen and MingHung Kao. Testing objectoriented programs an integrated approach. In10th International Symposium on Software Reliability Engineering (ISSRE’ 99), pages 73– 83, Boca Raton, FL, November 1999. IEEE Computer Society. 12 [9] L. L. Constantine and E. Design. PrenticeHall, Englewood Cliffs, NJ, 1979. [10] Donald G. Firesmith. Testing objectoriented software. InEleventh International Conference on Technology of ObjectOriented Languages and Systems (TOOLS USA, ’ 93), pages 407– 426. PrenticeHall, Englewood Cliffs, New Jersey, 1993. [11] P. G. Frankl and E. J. Weyuker. An applicable family of data flow testing criteria. IEEE Transactions on Software Engineering, 14(10):1483– 1498, October 1988. [12] M. J. Harrold and M. L. Soffa. Selecting and using data for integration testing. IEEE Software, 8(2):58– 65, March 1991. [13] Mary Jean Harrold and Gregg Rothermel. Performing data flow testing on classes. InSecond ACM SIGSOFT Symposiumon Foundations of Software Engineering, pages 154– 163. ACM Press, New York, New York, 1994. [14] Jane Huffman Hayes. Testing of objectoriented programming systems (OOPS): A faultbased approach. In E. Bertino and S. Urban, editors,ObjectOriented Methodologies and Systems, volume LNCS 858. SpringerVerlag, 1994. [15] IEEE. IEEE Standard Glossary of Software Engineering Terminology. ANSI/IEEE Std 7291983, 1983. [16] Zhenyi Jin and A. Jefferson Offutt. Couplingbased criteria for integration testing. The Journal of Software Testing, Verification, and Reliability, 8(3):133 – 154, September 1998. [17] Paul C. Jenson and Carl Erickson. Objectoriented integration testing. Communications of the ACM, 37(9):30– 38, 1994. [18] Bertrand Meyer. ObjectOriented Software Construction. Prentice Hall, Englewood Cliffs, New Jersey, 2nd edition, 1997. [19] A. J. Offutt, M. J. Harrold, and P. Kolte. A software metric system for module Journal of Systems and Software, 20(3):295– 308, March 1993. [20] A. J. Offutt and J. Pan. Detecting equivalent mutants and the feasible path problem. The Journal of Software Testing, Verification, and Reliability, 7(3):165–192, September 1997. [21] A. Orso and S. Silva. Integration testing of procedural objectoriented languages with polymorphism. In16th International Conference on Testing Computer Software (ICTCS’ 99), Washington, DC, 1999. [22] Jan Overbeck. Integration Testing for ObjectOriented So