Problem solve Get help with specific problems with your technologies, process and projects.

Automate regression testing

Rami Jaamour discusses the components and aspects that you would need to consider in automate regression testing.

Given the amount of different technologies our company is trying to make work together is there any way to automate regression testing? It would be nice to know if different modules will work together at the outset of a project.

Yes, there are ways to automate regression testing and it should be automated. Web services lend themselves to automation because of the absence of a user interface – a component which has traditionally made automated regression testing difficult. There are vendors who offer regression test automation technologies that can be found with Web search. The components and aspects that you would need to consider are:

1) Automated build process. The services would need to compile and deploy automatically. This is typically done on a daily basis by the build system (at night) after code changes were made during the day.

2) Tools that allow you to easily create test cases that are as close to the use case scenarios as possible, and at the messaging layer.

3) An infrastructure for running the tests automatically after the build is made.

4) An infrastructure for making the test cases available and sharable between different teams (development, QA, etc.) so they can collaborate efficiently.

5) Consolidated reports with the results so there is no repetitive time spent checking on test execution results.

6) Ability to link tests to requirements in the requirements management system or bug IDs in the bug tracking system becomes very useful in tracking progress and identifying what is tested/not tested, what is working and what is not working in a project.

This way you can build an efficient agile process. Every day developers and QA engineers can come in the morning, check the test execution results, resolve any regressions, then go on coding and creating tests for new features with confidence that existing functionality is still working correctly. Efforts are spent on creating the tests for new features, not testing old things or running tests manually, and this is a huge productivity gain. The regression test set grows as a valuable asset that can be executed at anytime to verify the application and it allows you to progress with the project with predictability and status awareness, rather than receiving bad surprises towards the end. This is all very doable and I've observed many organizations apply this process successfully.

Dig Deeper on Topics Archive

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.