At Pixability, our QA crew is made up of a director, two guide testers, and two automation engineers. Our Engineering division operates on a two week dash cycle the place the QA crew spends the primary three days on regression, adopted by an software launch. During the remainder of the dash, you’ll discover us testing dash options, grooming backlogs and supporting Pixability’s software program functions.

On Moving Toward Automation

In the start, QA regression testing was a wholly guide course of. However, I noticed an pressing have to automate repeatable assessments to avoid wasting helpful time, by way of devoted sources, a documented regression take a look at suite, and a course of for sustaining that suite. Here’s some background:

  • Dedicated automation sources: It’s laborious work to turn out to be an professional on, and keep on prime of, the functions that require testing. Creating and sustaining automated take a look at circumstances leaves little room for different duties.

  • Documenting the regression take a look at suite: It’s important to correctly describe the assessments which are wanted for a given launch to find out which guide take a look at processes must be automated. Documenting the assessments can be useful as a result of it highlights gaps in take a look at protection. Regression ought to all the time embrace important elements of the applying, and take threat into consideration. What’s left for guide testing ought to embrace advert hoc testing, usability testing, and different assessments that aren’t repeatable.

  • Maintaining the take a look at suite: While it’s time-consuming to doc each take a look at case, the take a look at suite might be nugatory if it doesn’t adapt to modifications within the software. The best methodology to maintain take a look at suites updated is to require guide testers to take care of it, as these engineers are testing modifications as they’re being developed.

Why Is Automation Important Now?

By automating assessments, QA groups can take a look at extra in regression, rising protection and decreasing threat. Automating assessments additionally shortens the regression cycle, as guide testers don’t should carry out as many take a look at circumstances.

However, it’s essential to notice that automation will not be a silver bullet for shortening regression. Bugs can push again a launch date regardless — however automation might help by liberating up guide testers to concentrate on testing tales as an alternative of regression.

Why Is Automation Important In The Future?

Continuous supply is the purpose, and automation is instrumental in reaching this purpose by way of fast responses to failed assessments. When assessments are automated and run as a part of the construct and deploy course of, builders can rapidly perceive what’s not working and make the suitable modifications.

Challenges: The Speed of the Development Cycle

The extra you automate, the extra you could keep. Pixability’s software modifications each two weeks, making it tough to each keep updated with the newest options, and keep the present regression suite. For instance, when a serious refactoring takes place within the UI, there are a number of new options that must be automated — however with an upcoming launch, we should decide the precedence by which we automate, and take a look at the remainder manually. While each scenario is exclusive, our crew strives to attain essentially the most take a look at protection with minimal guide testing. As our automation work catches up, some important capabilities would possibly must be manually examined, which underscores the significance of documenting these assessments.

Our Approach

When deciding what take a look at to automate subsequent, we first take into account whether or not it’s attainable to automate this course of, after which rank every course of to find out precedence utilizing the next components:

  • Level of effort: Describes whether or not a take a look at is well carried out as a part of an present framework, or would require investigation of an API or third celebration knowledge sources.

  • Level of enterprise impression: Highlights the impression on our resolution if the performance have been to fail.

  • Effort of guide testing: Determines the issue and sources required to manually take a look at the method.

Pixability’s QA crew is six months into this technique — be sure you verify again in 3-6 months for some classes we’ve discovered alongside the way in which.

The put up Our QA Strategy in an Agile Environment appeared first on .

This article sources info from Tech Blog