Test Automation Strategy

Test automation is key for success in today's software development;

especially in agile/teams with small delivery cycles it is very crucial to meet ever changing business requirements. In software industry automation is a buzz word and it is fruitful only when software delivery teams understand When/What/How/How Much to automate. Tool/technologies/Test framework selection is also play vital role in success/failure of test automation efforts.

Here can be our short and long term strategies;     

Short term strategy: After quickly learning the domain we should focus on automating smoke tests covering the breadth of the application and these high level tests will be running on each new build. This will give confidence that our recently code check in did not break any thing in whole application. This will be our 1st check in place to make sure that new code/build looks good.

In next stage of our short term strategy, we should write automated tests to cover the core functionality of the application under test. We should cover all the crucial functionality that is heart of the system and without this functionality we cannot ship product. This will be our 2nd line of quality check and having these tests in place will give us much more confidence that application is fine and breadth and core functionality of application is not broken in new code/build.

Also we should work closely with development team during this time to go for bug prevention mode instead of bug detection mode. We should  write automated tests and refactor the existing automated tests for all the new under development functionalities so that our regression suit is more robust and gives us more confidence. Other than functional attributes  we should  also performance test application on each new build and share the results with team. Also work closely with development team on performance issues as these are hard to identify and fix.

Long Term strategy: Working with above specified strategy we should  try to cover whole application from both breadth and depth prospective. Also we should work on process side to decrease the bug detection and fix cycle. All new functionality has automation tests and all regression tests should be running green on our nightly build. We should also automate every bug and will make it part of the regression suite. Later as team we can have multiple builds and different tests can run on each build continuously for example one build just for Smoke tests and regression build to run whole automated regression suite. Other than automation we should have many ideas to implement regarding Development/QA process to decrease the number of bugs in application at first place and to deliver bug free application on time. 

Weekly deployment and some urgent changes during the weekday

I have more than three year experience in Agile environment which is base on weekly deployment and we call it sprint cycle. About urgent changes, we can manage it well working closely with development team. Development team will share new control’s unique properties with us and we should write or refactor the existing automation tests for this new change and when development team will finish their work then our automation tests will be ready to run as well.

Passing these tests mean application is fine functionality wise for new functionality and running regression suite on this build will make sure no existing functionality is broken.

Testing Setup

We can set up testing infrastructure using latest tools and technology which will represent your true business values and satisfaction

Our QA Test automation consultants, TestOps, Manual tester and BA's can deliver best test solution which will make sure that quality is achieved and customer is happy.