skip to main content
10.1145/336512.336532acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
Article
Free Access

Testing: a roadmap

Authors Info & Claims
Published:01 May 2000Publication History
First page image

References

  1. 1.D. C. Atkinson and W. G. Griswold. The design of whole-program analysis tools. In Proceedings of the 18th International Conference on Software Engineering, pages 16-27, March 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. 2.T. Ball. The concept of dynamic analysis. In Proceedings of the Joint Seventh European Software Engineering Conference (ESEC) and Seventh ACM SIGSOFT International Symposium on the Foundations of Software Engineering, September 1999.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. 3.T. Ball and S. G. Eick. Software visualization in the large. Computer, 29(4):33-43, April 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. 4.B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, 1990.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. 5.A. Bertolino, P. Inverardi, H. Muccini, and A. Rosetti. An approach to integration testing based on architectural descriptions. In Proceedings of the IEEE ICECCS- 97.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. 6.U. Buy, A. Orso, and Pezzi. Issues in testing distributed component-based systems. In Proceedings of the First International Workshop on Testing Distributed Component-Based Systems, May 1999.]]Google ScholarGoogle Scholar
  7. 7.Y. F. Chert, D. S. Rosenblum, and K. P. Vo. TestTube: A system for selective regression testing. In Proceedings of the 16th International Conference on Software Engineering, pages 211-222, May 1994.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. 8.J. J. Chilenski and S. P. Miller. Applicability of modified condition/decision coverage to software testing. Software Engineering Journal, 9(5):191-200.]]Google ScholarGoogle Scholar
  9. 9.M. A. Cusamano and R. Selby. How Microsoft builds software. Communications of the ACM, 40(6):53-61, June 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. 10.R. A. DeMillo. Test adequacy and program mutation. In Proceedings of the 11th International on Software Engineering, pages 355-356, may 1989.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. 11.P. Devanbu. GENOA - A customizable, front-end retargetable source code analysis framework. A CM Transactions on Software Engineering and Methodology, 9(2):177-212, April 1999.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. 12.P. Devanbu and S. Stubblebine. Software engineering for security: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. 13.P. Devanbu and S. Stubblebine. Cryptographic verification of test coverage claims. IEEE Transactions on Software Engineering, in press.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. 14.R.-K. Doong and P. G. Frankl. The ASTOOT approach to testing object-oriented programs. A CM Transactions on Software Engineering and Methodology, 3(2):101- 130, April 1994.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. 15.N. S. Eickelmann and D. J. Richardson. What makes one software architecture more testable than another? In Proceedings of the International Software Architecture Symposium, October 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. 16.M. D. Ernst, J. Cockrell, W. Griswold, and D. Notldn. Dynamically discovering likely program invariants to support program evolution. In Proceedings of the 21 st International Conference on Software Engineering, pages 213-224, May 1999.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. 17.N. Fenton and M. Neil. Software metrics: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. 18.J. B. Goodenough and S. L. Gerhart. Toward a theory of test data selection. IEEE Transactions of Software Engineering, pages 156-173, June 1975.]]Google ScholarGoogle Scholar
  19. 19.M. J. Haxrold. Architecture-based regression testing of evolving systems. In International Workshop on the Role of Software Architecture in Testing and Analysis, July 1998.]]Google ScholarGoogle Scholar
  20. 20.M. J. Harrold, R. Gupta, and M. L. Sofia. A methodology for controlling the size of a test suite. A CM Transactions on Software Engineering and Methodology, 2(3):270-285, July 1993.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. 21.M. J. Harrold, D. Rosenblum, G. Rothermel, and E. J. Weyuker. Empirical Studies of a Prediction Model for Regression Test Selection. IEEE Transactions on Software Engineering, in press.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. 22.M. J. Harrold and G. Rothermel. Performing dataflow testing on classes. In Proceedings of the Second A CM SIGSOFT Symposium on Foundations of Software Engineering, pages 154-163, December 1994.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. 23.M. J. Harrold, G. Rothermel, R. Wu, and L. Yi. An empirical evaluation of program spectra. In Proceedings of ACM Workshop on Program Analysis for Software Tools and Engineering, pages 83-90, June 1998.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. 24.J. R. Horgan. Mining system tests to aid software maintenance. The Telcordia Software Visualization and Analysis Research Team, Telcordia Technologies.]]Google ScholarGoogle Scholar
  25. 25.D. Jackson and M. Rinard. Reasoning and analysis: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.]]Google ScholarGoogle Scholar
  26. 26.D. Kung, N. Suchak, J. Gao, P. Hsia, Y. Toyoshima, and C. Chen. On object state testing. In Proceedings of COMPSAC'94, 1994.]]Google ScholarGoogle ScholarCross RefCross Ref
  27. 27.J. W. Laski and B. Korel. A data flow oriented program testing strategy. IEEE Transactions on Software Engineering, 9(3):347-54, May 1983.]]Google ScholarGoogle ScholarDigital LibraryDigital Library
  28. 28.H. K. N. Leung and L. White. Insights Into Regression Testing. In Proceedings of the Conference on Software Maintenance, pages 60-9, October 1989.]]Google ScholarGoogle Scholar
  29. 29.T. Lewis. The next 10, 0002 years, part II. IEEE Computer, pages 78-86, May 1996.]]Google ScholarGoogle Scholar
  30. 30.B. Littlewood and L. Strigini. Software reliability and dependability: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. 31.R. Lutz. Software engineering for safety: A roadmap. In A. Finkelstein, editor, The Future of Software Engineering. ACM Press, New York, 2000.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. 32.G. McGraw and 3. Viega. Why COTS software increases security risks. In Proceedings of the First International Workshop on Testing Distribu ted Component- Based Systems, May 1999.]]Google ScholarGoogle Scholar
  33. 33.G. Murphy and D. Notldn. Lightweight source model extraction. In Proceedings of the Third A CM SIGSOFT Symposium on the Foundations of Software Engineering, pages 116-127, October 1995.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  34. 34.G. Murphy, P. Townsend, and P. Wong. Experiences with cluster and class testing. Communications of the ACM, 37(9):39-47, 1994.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  35. 35.K. Onoma, W-T. Tsai, M. Poonawala, and H. Suganuma. Regression testing in an industrial environment. Commummications of the ACM, 41(5):81-86, May 1988.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  36. 36.L. J. Osterweil ET AL. Strategic directions in software quality. ACM Computing Surveys, (4):738-750, December 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  37. 37.T. J. Ostrand and E. J. Weyuker. Using datattow analysis for regression testing. In Sixth Annual Pacific Northwest Software Quality Conference, pages 233-247, September 1988.]]Google ScholarGoogle Scholar
  38. 38.H. Pan, R. DeMillo, and E. H. Spafford. Failure and fault analysis for software debugging. In Proceedings of COMPSAC '97, August 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  39. 39.S. L. Pfieeger. Understanding and improving technology transfer in software engineering. Journal of Systems and Software, 47(2-3):111-124, July 1999.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  40. 40.S. Rapps and E. J. Weyuker. Selecting software test data using data flow information. IEEE Transactions on Software Engineering, SE-11(4):367-375, April 1985.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  41. 41.T. Reps, T. Ball, M. Das, and J. Larus. The use of program profiling for software maintenance with applications to the year 2000 problem, pages 432-439, September 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  42. 42.D. Richardson, J. Stafford, and A. Woff. A formal approach to architecture-based testing. Technical report, University of California, Irvine, 1998.]]Google ScholarGoogle Scholar
  43. 43.D. J. Richardson, P. Inverardi, and A. Bertolino, editors. Proceedings of the CNR-NSF International Workshop on the Role of Software Architecture in Testing and Analysis. July 1998.]]Google ScholarGoogle Scholar
  44. 44.D. Rosenblum and E. J. Weyuker. Using coverage information to predict the cost-effectiveness of regression testing strategies. IEEE Transactions on Software Engineering, 23(3):146-156, March 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  45. 45.D. S. Rosenblum. Adequate testing of component-based software. Technical Report Technical Report UCI-ICS- 97-34, August 1997.]]Google ScholarGoogle Scholar
  46. 46.G. Rothermel and M. J. Harrold. Analyzing regression test selection techniques. IEEE Transactions on Software Engineering, 22(8), August 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  47. 47.G. Rothermel, M. J. Harrold, J. Ostrin, and C. Hong. An empirical study of the effects of minimization on the fault-detection capabifities of test suites. In Proceedings of the International Conference on Software Maintenance, pages 34-43, November 1998.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  48. 48.G. Rothermel and M.J. Harrold. A safe, efficient regression test selection technique. ACM Transactions on Software Engineering and Methodology, 6(2):173-210, April 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  49. 49.G. Rothermel, L. Li, C. DuPnis, and M. Burnett. What you see is what you test: A methodology for testing form-based visual programs. In Proceedings of the 20th International Conference on Software Engineering, pages 198-207, April 1998.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  50. 50.M. Shaw and D. Garlan. Software Architecture Perspectives on an Emerging Discipline. Prentice Hall, New Jersey, 1996.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  51. 51.J. Stafford, D. J. Richardson, and A. L. Wolf. Chaining: A dependence analysis technique for software architecture. Technical Report CU-CS-845-97, University of Colorado, September 1.997.]]Google ScholarGoogle Scholar
  52. 52.E. J. Weyuker. Axiomatizing software test data adequacy. IEEE Transactions on Software Engineering, 12(12):1128-1138, December 1986.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  53. 53.W. E. Wong, J. R. Horgan, S. London, and H. Agrawal. A study of effective regression testing in practice. In Proceedings of the Eighth International Symposium on Software Reliability Engineering, pages 230-238, November 1997.]] Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Testing: a roadmap

                  Recommendations

                  Comments

                  Login options

                  Check if you have access through your login credentials or your institution to get full access on this article.

                  Sign in
                  • Published in

                    cover image ACM Conferences
                    ICSE '00: Proceedings of the Conference on The Future of Software Engineering
                    May 2000
                    381 pages
                    ISBN:1581132530
                    DOI:10.1145/336512

                    Copyright © 2000 ACM

                    Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

                    Publisher

                    Association for Computing Machinery

                    New York, NY, United States

                    Publication History

                    • Published: 1 May 2000

                    Permissions

                    Request permissions about this article.

                    Request Permissions

                    Check for updates

                    Qualifiers

                    • Article

                    Acceptance Rates

                    Overall Acceptance Rate276of1,856submissions,15%

                    Upcoming Conference

                    ICSE 2025

                  PDF Format

                  View or Download as a PDF file.

                  PDF

                  eReader

                  View online with eReader.

                  eReader