At Sauce Labs, we define Continuous Testing as a “ best practice approaching to software quality that involves quiz earliest and more often throughout the development lifecycle. ” Teams that follow uninterrupted testing agnise a number of benefits, including few bugs found in production, faster liberation cycles, and overall improved customer experience. Another seldom discourse benefit is that as the routine of character checkpoints increase, so does the bulk of examination data and quality sign. This data, when present in a clear and reliable way, can go a long way in helping squad optimize and continually improve their examination practice. However, it can also be an engineering team ’ s worst nightmare.

Simply represent trial data in congeries can be confusing, and sometimes even counterproductive. Teams that want to get the most out of test datum analytics ask to lay some good practices basis in order to make their data work for them. If they can do this, they can use information analytics puppet to reach the pursual:

• Uncover quality gap - understand where in the pipeline or application you need to apply more testing coverage, or perhaps where testing is creating a bottleneck and needs to be optimized

• Understand resourcefulness allocation - are certain squad feeling stuck with long test execution times? Data insights can designate out where in the grapevine those blockers are occurring, and how you can redistribute resource to teams to ensure everyone has what they need.

• Celebrate success - Data isn ’ t precisely about risk mitigation, it ’ s besides about understanding where teams are succeeding, and why that ’ s the case. This allows for eminent performing groups to be celebrated, and gives a pattern for leadership in how they can replicate that success across the organization.

With all of these benefits in mind, here are some best practices that teams can use to harness the power of tryout datum and ensure they get the good insights into the efficacy of their quality efforts.

1. Set examination status to pass/fail

This may look like a no-brainer, but it is a crucial step for squad that need to truly understand their test datum in aggregate. Setting all of your test statuses to Pass/Fail can allow you to see where your application is working as a unit, and where there might be issues with testing. Additionally, Sauce Labs users that set their test status to pass/fail will be able to take advantage of our newest feature. To hear more, please citation.

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

2. Annotate/comment your tests

Providing an extra layer of context can make it much easier to trickle those test to regard more specific data. It can also help you find groups of examination lots more well, rather than receive to sift through mountains of data. Understand immediately what tryout you are looking at by adding additional info that is meaningful to your organization. You can notice in your tests using the. 

3. Give your tests meaningful and logical names

What ’ s in a name? For your trial, a meaningful and reproducible scheme creates circumstance. This permit you to do things like narrow down your failure conditions, understand your test coverage, remark how specific exam are execute over time, and more. It can also ply a reliable signal for you to understand when sure tests are creating quality risks. Some tips to take when naming your tryout:

• Give examination unequalled names. Think of them as individual snowbird: no two should be likewise!

• Be specific with your naming strategy. A test gens should be open in what it is trying to accomplish, and what success looks like.

• Avoid redact information in tests that don ’ t provide unique, human placeable identifiers. These are thing such as soma or pull postulation IDs and browser/OS edition.

To learn more, ascertain out this lightning talking from SauceCon 2019 onbest practices for naming your tests, presented by our real own own Dylan Lacey, Software Engineer in Support.

4. Associate trial with Builds

Tests ne'er exist in siloes. They operate in a bigger pipeline that include a number of other tools. Therefore, you don ’ t just want to realise how a particular test performs in isolation over time, you also want to grouping them together within the context of that larger pipeline. For Sauce users, this means. This assist you grouping tests meaningfully as it relate to your CI/CD grapevine, and analysis can show specific areas where testing might be creating issues or constriction. One of our nearly recentTech Tip videosshows you how to accomplish this, or you can cite the belowcode sample: 

Enabling your team to use the aggregate information from your tests gives your team the opportunity to optimize your prove practice and continually build digital confidence in your entire organization. Following these four best praxis of setting up pass/fail data, footnote your examination, naming your tests properly, as well as associating your tryout with builds sets your team up for further successes as you acquire new codification and testing processes. This is especially true for Sauce customers who need to take advantage of our new and improved platform, which include new features such as our machine-learning powerFailure Analysis. 

For those who require to learn how Sauce Labs helps you utilize datum to test better, we offer some Insights functionality as part of our2-week gratis trial. Sign up today, and see how you can build digital sureness with continuous advance.