計(jì)算機(jī)外文翻譯--測(cè)試多態(tài)關(guān)系的準(zhǔn)則(參考版)
2025-01-10 01:08本頁(yè)面
【正文】 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 Software. . Dissertation, Vienna University of Technology, 1994. 。這最終將導(dǎo)致軟件，可建更便宜，更可靠。該工具將被用于提供該技術(shù)的有效性的證據(jù)。該工具目前解析 Java程序，并生成多種圖表分析。 目前我們正在建設(shè)的概念證明的覆蓋分析工具來支持這種技術(shù)。 本研究針對(duì)開發(fā)形式化的，可衡量的標(biāo)準(zhǔn)，從面向?qū)ο筌浖y(cè)試產(chǎn)生的問題。這些標(biāo)準(zhǔn)依賴于一種新的類型的程序分析，準(zhǔn) 間分析。 5. 結(jié)論和未來工作 本文介紹了面向?qū)ο筌浖男碌募蓽y(cè)試技術(shù)。我們的方法考慮這一點(diǎn)，同時(shí)也相當(dāng)重視對(duì)測(cè)試所造成的 MUT 內(nèi)進(jìn)行方法調(diào)用之間發(fā)生的相互作用。這項(xiàng)工作還認(rèn)為，可能發(fā)生一個(gè)給定的對(duì)象引用可能的綁定。這里定義的標(biāo)準(zhǔn)主要是分層的，既考慮到細(xì)，之間的集成對(duì)象和方法，它應(yīng)該允許更嚴(yán)格的測(cè)試粗粒度的相互作用。他們的第二個(gè)標(biāo)準(zhǔn)，所有的都對(duì)，要求每一個(gè)定義明確的路徑的一個(gè)對(duì)象，該對(duì)象至少測(cè)試一次每使用一個(gè)定義之間。第一，全綁定，要求每個(gè)對(duì)象的每個(gè)可能的結(jié)合可以至少被執(zhí)行一次，并且進(jìn)一步結(jié)合所有可能的組合，當(dāng)表達(dá)式包含多個(gè)對(duì)象進(jìn)行測(cè)試。我們的想法是確定的定
公司管理相關(guān)推薦
鄂ICP備17016276號(hào)-1