This week, mabl was a sponsor and speaker atAutomation Guild 2021, the conduct conference for hear about test automation strategy. As always, the conference was filled with a dizzying array of best practices for testing automation, tips and tricks for testing professionals, and wisdom from industry experts. & nbsp;

The conference ’ s unofficial-official tagline reads “ end flaky tests in 2021, ” and at mabl, we sure concord. Brittle, flaky exam continue to be a major obstacle for quality professionals in fast-paced companies, especially those operating in DevOps or CI/CD organizations. As a DevOps team ourselves, we understand the headaches that arrive when test mechanisation frameworks fail, ingest valuable time with high maintenance requirements. (That ’ s why we designed mabl with auto-heal capabilities, meaning mabl can automatically identify constituent impacted by product changes and update the necessary tests without human interposition, drastically reducing the amount of maintenance expect.)

To show what test automation appear like without gonzo tests, Product Manager Anton Hristov and Software Engineer Lauren Clayberg presented how mabl test with mabl at this year ’ s event. & nbsp;

Testing Strategies at mabl & nbsp;

Like any mature testing organization, the mabl team uses a range of tests to ascertain full essay coverage: & nbsp;

• Unit exam: Unit exam are heavily expend throughout all of our code bases with 66 % coverage for the web app. Target 95 % coverage for new projects.

• (react-testing-library, Jest, JUnit, Mockito, chai, mocha, sinon)

Sample unit test study

• End-to-end testing: We use mabl to examine the end-to-end user experience of the web app with 100 % page coverage.

Sample end-to-end report

• Integration tests: Integration tests are also heavily expend throughout our code bases and we use mabl for try the UI.
• (CodeceptJS for Trainer, Java for API, mabl for UI/API)

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

• Exploratory testing: We do team-based exploratory testing (known internally asElmer Fudds, except we ’ re hunting bug instead of rabbits) as an extra precaution for the web UI, Chrome extension, and the aboriginal background app.

If you ’ ve visited the mabl blog before, you ’ ve no uncertainty seen the infographic below. It instance what a full DevTestOps pipeline looks like with test integrated into every aspect of the SDLC. At mabl, this is also a model for our examination praxis throughout the platform. & nbsp;

Automated Testing Throughout Development

The mabl team has as many as 100 UI commits per week, a rate that would be near-impossible to sustain with brittle or freakish tryout. The process begins during the coding point, where we run unit exam and integration tests. For UI tests, a local runner is used to test the particular branch. & nbsp;

Next, in the pull request stage, a preview surroundings is established and code is run through deployment test and cross-browser examination. This check that the new codification meets basic functionality requirements and trim the amount of testing needed in the development level. Our team has adopted a shift-left approach which enables our quality squad to pass more time performing exploratory testing and engineer acquire a better sentience of calibre issues. & nbsp;

In the development phase, all regression testing as good as explorative testing is executed, which ensures that even the well-nigh ‘ originative ’ end user would be hard-pressed to break the app or website. In mabl ’ s DevOps workflow, the maturation form also include see examination coverage. & nbsp;

Once code is in production, our team expend mabl to monitor execution and test reportage, especially with our Segment integration that check testing is aligned with user needs. & nbsp;

[To say about the DevTestOps workflow in greater particular, insure out ourTesting for DevOps Pipelines serial!] & nbsp;

Overall, the Testing in DevOps framework ensures that the mabl team is capable to continuously test and deploy new code, while also continuously improving the mabl experience. & nbsp;

Turning test automation into product quality

In improver to its advanced test automation features, mabl also has blanket monitoring capabilities. The team uses these to unceasingly improve our quality strategy with data. & nbsp;

A major component of the mabl quality strategy start with integrations, which allow testing to be fully desegregate into the DevOps workflow, and secure that issues are surfaced and handle efficiently. For a pocket-sized squad, this reduces the feat need to keep everyone updated and frees up more clip to focus on high-value maturation employment. As we ’ ve grown, integrations with Slack, Jira, Segment, and GitHub keep to facilitate us simplify quality management. & nbsp;

The key to developing and maintaining an effective quality strategy is to be as data-driven and proactive as potential throughout the DevOps pipeline. At mabl, we recitation what we preach to foster a culture of caliber that not but provides the best intelligent test automation solution possible, but too addresses the challenge face quality master in a DevOps world. & nbsp;

Thanks to all who joined Anton and Lauren at Automation Guild 2021 and we hope to see you next year! & nbsp;

To see how mabl can help your team keep up with fast-paced evolution,sign up for a free trial today.