Advertisement

When to Stop Testing

  • Ajay Jangra
  • Gurbaj Singh
  • Chander Kant
  • Priyanka
Part of the Communications in Computer and Information Science book series (CCIS, volume 169)

Abstract

Testing process is to detect variance between actual and expected results, to make good quality software. Testing is necessary but to test each and every part of software is not feasible. There should be threshold point to stop testing, in this paper we proposed an analytical scheme which provides threshold values to stop testing without compromising the quality of software. By using proposed scheme, developer can easily find out sufficient and enough level of testing.

Keywords

Software testing Quality Test cases testing metrics 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Nita, M., Notkin, D.: White-Box Approaches for Improved Testing and Analysis of Configurable Software Systems. IEEE, Los Alamitos (2009)CrossRefGoogle Scholar
  2. 2.
    Saha, G.K.: Understanding Software Testing Concepts. Published in ACM Ubiquity 9(6) (2008)Google Scholar
  3. 3.
    Do, H., Mirarab, S., Tahvildari, L.: An Empirical Study of the Effect of Time Constraints on the Cost-Benefits of Regression Testing. ACM, New York (2008)CrossRefGoogle Scholar
  4. 4.
    Kapfhammer, G.M.: Software Testing. ACM, New York (2008)Google Scholar
  5. 5.
    Nilsson, R., Offutt, J.: Automated Testing of Timeliness: A Case Study. IEEE, Los Alamitos (2007)Google Scholar
  6. 6.
    Seo, K.I., Choi, E.M.: Comparison of Five Black-box Testing Methods for Object-Oriented Software. IEEE, Los Alamitos (2006)Google Scholar
  7. 7.
    Bentlet, J.E., Bank, W., C.NC. : Software Testing Fundamentals-Concepts, Roles, and Terminology, pp. 1–12.Google Scholar
  8. 8.
    Cem Kaner, J.D.: Ph.D.The Ongoing Revolution in Software Testing, in Software Test & Performance Conference, December 8 (2004)Google Scholar
  9. 9.
    Kaner, C.: Inefficiency and Ineffectiveness of Software Testing: A Key Problem in Software Engineering (2004)Google Scholar
  10. 10.
    Kusinitz, A.: Software Testing—How Much Is Enough? (June 2003)Google Scholar
  11. 11.
    Tse, T.H., Chen, T.Y., Feng, X.: On the completeness of Test Cases for Atomic Arithmetic Expressions. IEEE, Los Alamitos (2000)CrossRefGoogle Scholar
  12. 12.
    Martin, E.: Testing and analysis of access control policies. In: International conference on software engineering (ICSE 2007 companion) (2007)Google Scholar
  13. 13.
    Chen, T., Sahinoglu, M., von Mayrhauser, A., Hajjar, A.: How Much Testing is Enough? Applying Stopping Rules to Behavioral Model Testing (2001)Google Scholar
  14. 14.
    Jangra, A., Singh, G., Singh, J., Verma, R.: Exploring Testing Strategies. International Journal of Information Technology & Knowledge Management IV-I (December 2010); ISSN 0973-4414Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Ajay Jangra
    • 1
  • Gurbaj Singh
    • 1
  • Chander Kant
    • 2
  • Priyanka
    • 3
  1. 1.CSE DepartmentU.I.E.T. Kurukshetra UniversityKurukshetraIndia
  2. 2.DCSA Kurukshetra UniversityKurukshetraIndia
  3. 3.ECE DepartmentU.I.E.T. Kurukshetra UniversityKurukshetraIndia

Personalised recommendations