Thursday, February 3, 2011

Test Automate for legacy Applications...

Automate testing is always a tedious Task, if you don’t have addicted to it. I’m also not that much into Test Automation, but with latest experience we had with our projects (Most importantly they are Products), were forced us to think of having Testing Automated. It was developers always doing Unit testing to make sure all the things are ok after a change, before giving a Release to the QA.

Found a good article (Or it’s about a discussion) on this specially it’s about Test Automate in legacy Applications already developed, but don have test automated.

There are Key Points highlighted in the content on this subject..

Hubert Matthews

“You can never test everything so you have to choose where you want to spend your Time and Money. Testing for me is primarily about information and risk and not about blanket coverage and completeness”.

Question mentioned, which might help to find areas to focus on..

1. Where is the Client Currently experiencing poorest quality?

2. What are the key areas of functioning (e.g what makes them money)?

3. Would the Client prefer more features better quality?

4. What are the risks of their systems?

5. If Client could improve what it would be?

6. Would exploratory manual testing find more important bugs?

And According to the Rajesh Patel..

1. Only automate through the GUI the most important paths through your app. A lot of apps have some common path that is used in 80% of cases. If this stops working, your business is in trouble!!

2. If you can bypass the GUI and go straight to the backend to test business functionality, do that. That means GUI-specific integration tests are about making sure the data from the front-end get to the back end.

Some more points..

  • Ask the customers to prioritize the critical areas of the app
  • Write manual regression test scripts for each area
  • Budget time in each sprint to write GUI smoke tests for those areas
  • Execute the test suite at least once a day with the CI framework
  • All new development should have adequate tests

Here is the Original Article link..

Best Regards

Lakmal