All too often, QA is comprehend as the bottleneck in getting package out the threshold. This makes sense when you only see QA as just the “ bug finder ” in a world where you build, test, and liberation. But how can you leverage your QA squad to improve your pipeline to delivery? There are many ways that you can do this, but let ’ s look at using defect prevention and analysis to test wisely and improve your pipeline.PreventionThe scenario: a designer has post spec (and if you ’ re favorable, wireframes) for a new feature. Depending on your growing procedure, you would probably see the following happen:

1. A developer writes some codification

2. A tester goes off and publish some tests

3. Once the developer finishes codification, the tester executes the tests, notice bugs, and state the developer to fix the bugs that be ground.

The above scenario seems simple, however at the later stages often one discover that the examination cases do not 100 % align with code. To fix this, what if you changed this operation to appear more like this?

1. The decorator, technologist, and tester meet to discuss the characteristic.

2. QA commence guiding the team into the tests that are needed to ensure the feature work.

   SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

3. The engineer and designer see what is go to be tested, and also bestow - identifying country that were missed in the specification or wireframes.

4. The squad agrees to the tests.

5. The technologist builds the feature, pass each tryout until all are passing.

In the first approach, QA is bar to be only the bug discoverer. But in the latter, QA aid drive the team towards bug prevention. In write tests first, before anything is built, there are a few advantages:

• A shared understanding of the requirements early in the development process puts everyone on target for the same goal.Have you ever act on (or grapple) a project where the engineer and tester ’ s interpretation of a lineament was completely different? The end result is code that does not legislate the exam, and time drop trying to reconcile the matter delays future work. When tests are written first, the guessing game is conduct away; it highlight bugs earlier in the process as well as opening in lineament to final product issues.

• Issues found early save resources.Consider how expensive it is to notice a bug late in the cycle, after Development is ‘ cease ’ (a condition I use loosely hither). When QA facilitates tests before lineament, developer get glitch before QA even sees them. Then there are no bug to track, therefore no need to review the bug in triage or publish specific regression trial that make sure that one specific bug is fixed (those test were already written before the feature was coded). It also eliminates the need to perform those specific regression tests on every build since the bug perform not exist in the first place. Lastly, there ’ s no motive to have a meeting to justify the cost of define the bug versus the cost of leave it in, and no motivation to document its presence and or enforce its workaround. You do the math; this transform to hour -even days- of clip saved.

• Holes in design are found early and rework is minimized. In leveraging your QA squad to guide tryout maturation, usability (UX) should also be a consideration when designing tests. It is not possible to foreknow the success of all features when they see the user. Perhaps there is a technical aspect that has not been considered, and the team will want to rethink the design. This is much easier to do up front than after thing get started developing. Everyone in Development should be involved in a UX discourse early on in the process.

Of course there is much more we could dive into, but it is pretty clear that using your QA team to foreclose bug can exclusively help in your production ’ s delivery pipeline.Test WiselyDefects are inevitable. Try as we might to forestall them, they are merely going to happen. But what do you do with bugs that you do find? Your QA team can look at outcome and identify trend in the system. Perhaps the majority of the bugs are in a certain area. Your team can chop-chop adjust testing to areas that appear to be in more hassle, spending resources prudently as you get ready to deliver your product. If you need to get a product out the door – does it make more sense to spend imagination in areas that have had no (or few) bugs reported? Or preferably to add more to a feature that has had more problems than others? As you can see there are not just implementation questions, there are strategic ones as good.SummaryLet ’ s start getting rid of the percept that QA is the intellect things get delayed, and instead look at the point of view that QA gets your ware out the door quicker, and with better quality! Work with your QA teams to learn to drive defect prevention and to analyze those that do arrive in, and you should see a path to improving your pipeline. QA is then a facilitator of success, not a blocker.About The Author

Ashley Hunsberger is a Quality Architect at Blackboard, Inc. and co-founder of Quality Element. She ’ s passionate about making an wallop in education and loves coaching squad members in product and client-focused quality pattern. Most recently, she has focused on test strategy implementation and training, development process efficiency, and preaching Test Driven Development to anyone that will listen. In her downtime, she enjoy to travel, read, quilt, hike, and spend clip with her family.

T: @ aahunsberger L:https: //www.linkedin.com/in/ashleyhunsberger

Products

Global tool

Set up and integrate

Resources

Company