Automation of Regression Analysis: Methodology and Approach

Part of the Advances in Intelligent and Soft Computing book series (AINSC, volume 166)

Abstract

Test automation is widely used in different practices all over the world often to save time or to reduce manual effort. However, regression analysis consists of mundane tasks that are performed by software engineers on a daily basis. Automation of a regression analysis raises our hopes by promising a reduction in time and effort, yet at the same time it continues to create as many problems as it has solved. Thus the solution has to take into account the limitations of automation yet reap the maximum benefits. This paper will focus on: The paradigm to be followed while developing automation and the Advantages and Limitations that accompany the process of automating regressions.

Keywords

Regression Automation 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Brett, P.: Seven Steps to Automation Success (June 2001), http://www.io.com/~wazmo/papers/seven_steps.html
  2. 2.
    Bach, J.: Test Automation Snake Oil. Windows Technical Journal (October 1996), http://www.satisfice.com/articles/test_automation_snake_oil.pdf
  3. 3.
    Dustin, E.: Lessons in Test Automation. Software Testing and Quality Engineering (September 1999), http://www.stickyminds.com/sitewide.asp?ObjectId=1802&ObjectType=ART&Function=edetail; Fewster, M., Graham, D.: Software Test Automation. Addison-Wesley (1999)
  4. 4.
    Groder, C.: Building Maintainable GUI Tests. In: Fewster 1999 (1999)Google Scholar
  5. 5.
    Kit, E.: Integrated, Effective Test Design and Automation. Software Development (February 1999), http://www.sdmagazine.com/articles/1999/9902/9902b/9902b.htm
  6. 6.
    Hancock, J.: When to Automate Testing. Testers Network (June 1997), http://www.data-dimensions.com/Testers'Network/jimauto1.htm
  7. 7.
    Hendrickson, E.: Making the Right Choice: The Features you need in a GUI Test Automation Tool. Software Testing and Quality Engineering Magazine (May 1999), http://www.qualitytree.com/feature/mtrc.pdf
  8. 8.
    Hoffman, D.: Heuristic Test Oracles: The Balance between Exhaustive Comparison and No Comparison at All. Software Testing and Quality Engineering Magazine (March 1999)Google Scholar
  9. 9.
    Kaner, C.: Improving the Maintainability of Automated Test Suites. Presented at Quality Week (1997), http://www.kaner.com/lawst1.htm
  10. 10.
    Linz, T., Daigl, M.: How to Automate Testing of Graphical User Interfaces. European Systems and Software Initiative Project No. 24306 (June 1998), http://www.imbus.de/html/GUI/AQUIS-full_paper-1.3.html
  11. 11.
    Jeffries, R.E.: XPractices (1997), http://www.XProgramming.com/Practices/xpractices.htm
  12. 12.
    Marick, B.: When Should a Test Be Automated? Presented at Quality Week (1998), http://www.testing.com/writings/automate.pdf
  13. 13.
    Marick, B.: Classic Testing Mistakes. Presented at STAR (1997), http://www.testing.com/writings/classic/mistakes.html
  14. 14.
    Pettichord, B.: Success with Test Automation. Presented at Quality Week (May 1996), http://www.io.com/~wazmo/succpap.htm
  15. 15.
    Thomson, J.: A Test Automation Journey. In: Fewster 1999 (1999) Google Scholar
  16. 16.
    Weinberg, G.M.: Quality Software Management: Systems Thinking, vol. 1. Dorset House (1992)Google Scholar

Copyright information

© Springer-Verlag GmbH Berlin Heidelberg 2012

Authors and Affiliations

  1. 1.Department of computer Science and EngineeringNIT PatnaPatnaIndia
  2. 2.Department of Information TechnologyNIT PatnaPatnaIndia
  3. 3.Business Technology AnalystDeloitte IndiaNoidaIndia

Personalised recommendations