Accelerating Quality for Digital Enterprises

Cut Your Regression Cycle by 75 Percent

The biggest challenge for QA groups is how to complete the regression cycle which often takes far more time and resources than the QA team has.  The problem is often worse for Agile teams- in fact some QA teams struggle to get time to complete any regression testing.  QMetry helps to organize your test cases and improve efficiency, but to truly keep up with regression as your team grows you need to build up a good automated regression suite, and Continuous Integration (CI).  Fortunately QMetry integrates well CI. Recently the services arm of InfoStretch has helped some of our customers cut down regression cycles by 75% or more using the below best practices.

Introduce Continuous Integration Tools

Regression Testing

Regression runs can be done overnight or over the weekend. Compare this to manually entering and monitoring scripts during working hours and there’s no contest on regression speed and efficiency. But you will need Continuous Integration (CI) tools like Jenkins – CI to be able to able to manage automated regression runs. There are a lot of other very strong reasons for introducing CI tools. As a starting point, there’s early defect detection, reduced overheads, better project visibility and reduced assumptions.

Automate More

There is always a little controversy in deciding the right amount of testing to automate. But common sense should prevail. If it is more time-efficient to create automation scripts once and re-use them, then that is what should be done. But don’t stop when you have created test automation scripts. There can be many other elements outside of the core testing that can be automated. For example, think about automating the loading of the software to be tested, configuring servers and posting results. For instance each QMetry build is automated to be created, installed, and then tested using a simple script which any user can kick off.  The tests are run through QMetry Automation Studio (QAS) which provides some basic pass / fail reports. QAS also sends the individual test results to QMetry where they can be further analyzed.  If the build is accepted the manual testers will just continue adding their test results tagging each new manual test with the same build. This process not only does this allow us to move quickly, but allows us to compare our manual and automated test results based on builds.

Connect All The Pieces

Any setup where the individual components do not talk to each other means your efficiency will be leaking away. Having one integrated view of all testing provides a single comprehensive view of the test data.  QMetry’s advanced reporting engine allows management to see the 1000 ft. view of the testing or drill in to get a granular view of the testing. So, even if it’s tougher at the beginning, integrate the core tools in your testing portfolio. If your testing infrastructure is relatively mature, you will ideally have a mobile test management tool at the center. That will need to talk to and share information with every other core system you use, which will increase visibility of your whole quality process and create multiple efficiencies.

Get in touch with us to see how we can help increase your regression testing efficiency and the efficiency of your whole QA and quality operation.

VN:F [1.9.10_1130]
Rating: 0.0/10 (0 votes cast)

SharePost

0Likes

0 Comments

Leave a comment

Your email address will not be published. Required fields are marked *