Skip to main content

Fast Feedback from Automated Tests Executed with the Product Build

  • Conference paper
  • First Online:
Software Quality. The Future of Systems- and Software Development (SWQD 2016)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 238))

Included in the following conference series:

Abstract

Nowadays Continuous Integration (CI) is a very common practice with many advantages and it is used in many software projects. For large software projects checking out the source code, building the product and testing the product build via automated tests during CI can take a long time (e.g. many hours). So the software developers do not get fast feedback about their changes. Often the test report contains the results of many changes from several software developers or the feedback is not accurate enough according to the developer’s source code changes. This paper describes a novel approach to reduce the feedback time and to provide test results for only these changes the developer has committed.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    When the option “Build Automatically” is activated in the Eclipse IDE.

  2. 2.

    Depending on the hardware of the developer’s computer.

  3. 3.

    For example the test plugin could be named as the product plugin plus the postfix “.test”.

References

  1. Lindstrom, L., Jeffries, R.: Extreme programming and agile software development methodologies. Inf. Syst. Manag. 21(3), 41–52 (2004)

    Article  Google Scholar 

  2. Mogyorodi, G.: Requirements-based testing: an overview. In: International Conference on Technology of Object-Oriented Languages. IEEE Computer Society (2001)

    Google Scholar 

  3. Building a better bug-trap. Economist Magazine, June 2003

    Google Scholar 

  4. Fowler, M., Foemmel, M.: Continuous integration. (Thought-Works) (2006). https://www.thoughtworks.com/continuous-integration

  5. Duvall, P.M., Matyas, S., Glover, A.: Continuous Integration: Improving Software Quality and Reducing Risk. Pearson Education, United States (2007)

    Google Scholar 

  6. Beck, K.: Embracing change with extreme programming. Computer 32(10), 70–77 (1999)

    Article  Google Scholar 

  7. McConnell, S.: Daily build and smoke test. IEEE Softw. 13(4), 144 (1996)

    Google Scholar 

  8. Elbaum, S., Malishevsky, A.G., Rothermel, G.: Prioritizing test cases for regression testing, vol. 25(5). ACM (2000)

    Google Scholar 

  9. van der Storm, T.: Backtracking incremental continuous integration. In: 12th European Conference on Software Maintenance and Reengineering, 2008, CSMR 2008. IEEE (2008)

    Google Scholar 

  10. Maven. https://maven.apache.org/index.html

  11. Eclipse Foundation. http://eclipse.org

  12. Collins-Sussman, B., Fitzpatrick, B., Pilato, M.: Version Control with Subversion. O’Reilly Media, Inc., Sebastopol (2004)

    Google Scholar 

  13. Subclipse. http://subclipse.tigris.org/

  14. Asklund, U., Bendix, L., Ekman, T.: Software configuration management practices for eXtreme programming teams (2004)

    Google Scholar 

  15. Srikanth, H., Williams, L., Osborne, J.: System test case prioritization of new and regression test cases. In: 2005 International Symposium on Empirical Software Engineering. IEEE (2005)

    Google Scholar 

  16. PREEvision. https://vector.com/vi_preevision_en.html

  17. Beena, R., Sarala, S.: Code Coverage Based Test Case Selection and Prioritization (2013). arXiv preprint arXiv:1312.2083

  18. JaCoCo. http://www.eclemma.org/jacoco/

  19. Saff, D., Ernst, M.D.: Continuous testing in Eclipse. In: Proceedings of the 27th International Conference on Software Engineering. ACM (2005)

    Google Scholar 

  20. NCrunch. http://www.ncrunch.net/

  21. Thiele, E.: CompilerCache. http://www.erikyyy.de/compilercache/

  22. Yoon, M., et al.: A test case prioritization through correlation of requirement and risk. J. Softw. Eng. Appl. 5(10), 823–835 (2012)

    Article  Google Scholar 

  23. Rothermel, G., et al.: Test case prioritization: an empirical study. In: Proceedings of the IEEE International Conference on Software Maintenance, 1999 (ICSM 1999). EEE (1999)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Martin Eyl .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing Switzerland

About this paper

Cite this paper

Eyl, M., Reichmann, C., Müller-Glaser, K. (2016). Fast Feedback from Automated Tests Executed with the Product Build. In: Winkler, D., Biffl, S., Bergsmann, J. (eds) Software Quality. The Future of Systems- and Software Development. SWQD 2016. Lecture Notes in Business Information Processing, vol 238. Springer, Cham. https://doi.org/10.1007/978-3-319-27033-3_14

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-27033-3_14

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-27032-6

  • Online ISBN: 978-3-319-27033-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics