How often should you parallel test? If that go like a trick question, mayhap it is. In this post, we & # x27; ll let you in on the & quot; trick & quot; part of the question, and so we & # x27; ll talk about what really subject when it get to when and how often you should twin test.

Parallel Testing - What is it?

First, the trick. It lies in what parallel testing is, and more to the point, what it isn & # x27; t.

What is parallel testing? The condition & quot; parallel testing & quot; is generic and rather unspecific, but it typically refers to automated scheme for simultaneously testing multiple applications or portion, with each application or subcomponent being test on a different computer. It is sometimes also used to depict automated testing of a single application or component on multiple platforms. The trial computers can be individual ironware units, or more typically, separate practical machine. In all cases, nonetheless, the combination of automation and multiple test scheme makes it possible to run many more tests than would be practical with serial testing, and it reduces the clip expect for testing to a fraction of that required for the equivalent serial tryout. The key points to hold in psyche about parallel testing are that:

• Parallel examination is a framework for testing.It lie basically of a scheme for command and running automated tests on multiple computers, the machine-controlled test book, the test systems, and reports of the test result. The framework can accommodate most, if not all, of the specific types of test that you are likely to run.

• Parallel examination is, more than anything, the logical outcome of applying current IT technology to testing.It is coming into widespread use mostly because it is now hard-nosed and comparatively easygoing to run parallel tests on multiple system. As is so often the instance when new technology wreak new capability, citizenry are quick to take advantage of these capabilities, once they understand what is possible.

• Parallel examination is in many ways a alternate for sequential testing, and manual examination in general.Sequential and manual examination have dominated software QA since the other day of computing, but not because they offer any real advantages. For a long time, they were the lonesome ways to test. With no feasible alternative, people made the best of the techniques that were useable. The advantages of parallel examination (in damage of clip, scope, and cost) are so great, yet, that it is easily on its way to becoming the new prove measure.

It is also significant to keep in mind what parallel testing isnot:

• Parallel testing is not a subset of the software testing regime, tie to specific functions or weather.Distributed testing (with which parallel examination is sometimes confused) does use multiple computers to quiz the interaction between components. As we mention above, parallel examination is a framework (which can include distributed testing, if appropriate), kinda than a type of test.

  For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

• Parallel testing is not a set of spot-checks.It makes no sense to add parallel testing to your test government as a variety of rethink, just to get anything that might turn up. As a testing framework, it should be able to contain almost all of your existing sequential tests, include both thorough testing and spot-checks.

• Parallel examination is not an add-on to your testing regime to meet new testing requirements or follow current trends.If you & # x27; re adding some parallel examination because higher-ups told you to, or because you need to keep up with the late trend, you & # x27; re likely to miss almost everything that parallel examination can do for you.

That, so, is the trick part of the question. Parallel testing is not just an add-on to your current system of sequential testing, any more than computers are an add-on to pencil-and-paper calculation, and for much the same ground - It is a new fabric, and a radical extension of what is possible.

What is Important?

So, what is important about how often you parallel test? In many ways, it really isn & # x27; t a matter of how often, but a matter of when - when the required tests can be done in parallel, when parallel testing will be more productive than serial testing, and when parallel examination will cost less than sequential testing. And the truth is that when parallel testing will do the job, it is well-nigh invariably much more productive and cost-effective than the equivalent set of tests in a sequential-testing environment.

It & # x27; s a New World

You can break it down like this:

1. Analyze your be examination regime, break it down into the smallest logical unit, and reorganize it for fully automated parallel testing.

2. Are there any tests leave over- tests that must be execute consecutive (or manually), outside of the parallel testing model? Be careful in determining this - some exam may simply ask to be reconceived or restructure before they will fit into the parallel framework.

3. Freestanding out the tests which genuinely can not or should not be done in parallel, and schedule those as demand. In impression, you will be treating those tests as add-ons to your standard (parallel) try regime.

So there it is. Welcome to the new world. Parallel testing is now the regulation, and not an optional, & quot; Should we toss in a few of these? & quot; add-on. And in this new world, the real question may be, how frequently should you go out of your way to perform clip and labor-consuming serial exam, if you involve to do them at all?

Image source:http: //www.shutterstock.com/pic-473592022/stock-vector-vector-seamless-parallel-diagonal-red-yellow-orange-brown.html

Michael Churchman started as a scriptwriter, editor, and producer during the anything-goes former eld of the game industry. He spent lots of the & # x27; 90s in the high-pressure bundled software industry, where the move from falls to faster release was well under way, and near-continuous release cycles and automated deployment be already de facto touchstone. During that time he developed a semi-automated scheme for contend localization in over fifteen languages. For the preceding ten years, he has been involved in the analysis of package ontogenesis processes and related engineering direction issues.