Dry Runs are often misunderstood. While they can be of huge benefit to a project, time and again they do not get factored into the testing schedule, and so, they can become a ‘nice to have’ rather than a mandatory part of the testing cycle.
The most common approach to doing a Dry Run is when the software tester has all the test scripts written and in place and the software is deemed ready for testing by the software developer. The Dry Run can then be executed by informally running through the test scripts and logging any issues.
An alternative to this could be for a tester to take the system requirements, and again run through the full system, but without following a test script.
Although documented test evidence is not required for a Dry Run, it is a good idea to keep track of any issues and resolutions.
The benefits of doing a Dry Run include saving money and time, although this may not seem the case to the project manager when timelines and budgets are looming. To use a Dry Run before the formal testing begins is an unrecognised advantage going into the OQ (Operational Qualification).
There are a number of hidden benefits to doing a Dry Run:
Benefits to the Developer:
- Confidence in the code or product being handed over to the software tester for formal qualification.
Benefits to the Software Tester:
- Saves time in the long run as there are less discrepancies with code when formal testing is being executed.
- Less formal documentation is needed with regard to software bug fixes
- More testing time
- If there are any test script errors found these can be fixed before formal testing (if the test scripts have not been signed), again this saves time on having to raise these as issues in formal testing.
- It allows the tester feel more confident when going into OQ
Benefits to the Customer:
- A fully tested system which may save time and money in the long run with regard to bugs being found at the PQ stage and in the ‘Live’ environment.
Taking the above benefits and time savings into consideration it is difficult to class a Dry Run as a waste of time.
At Dataworks we believe that the benefits of a Dry Run can only truly be considered and assessed on a project by project basis – taking all of the advantages to each stakeholder into account.
Our team of validation engineers will work in partnership with you to achieve and deliver the results you need. We will determine if a Dry Run will incur cost savings, or if it is an unnecessary addition to your validation process.You can be assured that your software and equipment will be validated to the highest industry standards by our skilled engineers.
If you have current or upcoming Validation projects and would like to discuss how we can deliver real benefits to your project please contact us today on 051 878555 or email firstname.lastname@example.org
Image courtesy of jesadaphorn at FreeDigitalPhotos.net
- Back to Blogs