{"id":275,"date":"2023-01-05T15:40:50","date_gmt":"2023-01-05T13:40:50","guid":{"rendered":"https:\/\/newstaging.pecodesoftware.com\/blog\/?p=275"},"modified":"2024-08-20T21:02:54","modified_gmt":"2024-08-20T18:02:54","slug":"case-study-automation-qa-for-performance-monitoring-platform","status":"publish","type":"post","link":"https:\/\/pecodesoftware.com\/blog\/case-study-automation-qa-for-performance-monitoring-platform\/","title":{"rendered":"Case Study: Automation QA for performance monitoring platform"},"content":{"rendered":"\n

Empowering employees is a crucial part of their professional development. Sometimes it’s hard to track their progress properly, as different people must be rated according to their professional stack. This is where our partner Workstride<\/mark><\/a> steps in.<\/p>\n\n\n\n

However, when the solution becomes widespread and the product grows big, its requirements become big too. Especially, when it comes to Quality Assurance.<\/p>\n\n\n\n

In this case study, we will cover how Automated QA testing can save an enterprise-level project from poor quality and errors.<\/p>\n\n\n\n

Brief summary<\/h2>\n\n\n\n

1. 85% of the current functionality of the product covered<\/p>\n\n\n\n

2. <\/mark><\/strong>94% of test cases are fully automated<\/p>\n\n\n\n

3. 350+ automated tests created<\/p>\n\n\n\n

4. 51 defects found and reported<\/p>\n\n\n\n

5. Overall client’s savings are comparable to the total of 4 Manual QA yearly work hours cost.<\/strong> <\/p>\n\n\n\n

About the project<\/h2>\n\n\n\n

WorkStride is a leading provider of channel partner performance and incentive programs for the global enterprise – including full-scale solutions for SPIFFs, Rebates, Training, MDF\/COOP, and more.<\/p>\n\n\n\n

The company provides a full suite of reward technology, service, and support. WorkStride focuses on expert service and performance results helps their clients to gain more than a platform. They gain a team.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

.<\/mark><\/p>\n\n\n\n

What was the challenge<\/h2>\n\n\n\n

The main requirement was to increase the automated testing coverage across definite platforms because their current manual testing process took a long time and had not constantly updated test results. The project is huge and multifunctional, so the number of test cases is growing regularly.<\/p>\n\n\n\n

Workstride needed a way to speed up the manual testing process. Also, the company wanted to improve the documentation of specific configurations, processes, etc., and set up the method of reporting failure and error detection accuracy<\/p>\n\n\n\n

Problems we faced<\/h2>\n\n\n\n

\u2022 A lot of existing test cases were not automated. The manual coverage was relatively huge, while automation was used only for a few critical tests. As a result, this created a heavy load on manual testers.<\/p>\n\n\n\n

\u2022 Existing automation tests were outdated and uninformative.<\/p>\n\n\n\n

\u2022 The development team was not using the advantages of automation reporting.<\/p>\n\n\n\n

\u2022 Poor documentation<\/p>\n\n\n\n

Solution we provided<\/h2>\n\n\n\n

\u2022 The project team consisted of 3 Automation QA Testers and 1 Manual QA Tester<\/p>\n\n\n\n

\u2022 The QA Automation team analyzed the current technology stack and scalability. We decided to change the test framework and language. Currently, tests are being written using TypeScript. <\/p>\n\n\n\n

\u2022 Test automation coverage maximization.<\/p>\n\n\n\n

\u2022 Manual run of test cases reduced. Automated tests execution increased.<\/p>\n\n\n\n

\u2022 BDD approach.<\/p>\n\n\n\n

\u2022 Clear reporting was introduced.<\/p>\n\n\n\n

\u2022 The documentation was updated constantly with details on how to clone, set up, configure, and write new tests. The details about the structure, best practices, and used frameworks were added.<\/p>\n\n\n\n

\u2022 The tests are now running in parallel with an introduced nightly run on a Jenkins server.<\/p>\n\n\n\n

\u2022 Significant reduction in test time achieved, not only due to the test execution time but also due to the redistribution of testing levels.<\/p>\n\n\n\n

\u2022 Stable test environments due to more accurate test data built.<\/p>\n\n\n\n

\u2022 Manual QA switches focus on hard-to-automate testing: UI, Usability, Localization, Compatibility, and partly regression.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

.<\/mark><\/p>\n\n\n\n

Advantages of the tools we used<\/h2>\n\n\n\n

The technology stack used in this project includes, but is not limited to:<\/p>\n\n\n\n

JavaScript and TypeScript<\/strong><\/h3>\n\n\n\n

Main programming languages we used for test automation.<\/p>\n\n\n\n

Cypress 10<\/strong> <\/h3>\n\n\n\n

It\u2019s a good solution for UI end-to-end tests because of a huge variety of commands that imitate real users\u2019 behavior. Also, it provides API requests that significantly reduce the run time, and more useful features such as time traveling, automatic waiting, screenshots, videos, etc. Just what we needed.<\/p>\n\n\n\n

Cypress Dashboard (Cloud) <\/h3>\n\n\n\n

Increases test velocity while giving total visibility into tests running in CI pipelines, compatible with Jenkins. It\u2019s a good alternative to test reporting tools, because of its high usability and user-friendly interface. As a side bonus, the development team was always able to access and debug failed tests. <\/p>\n\n\n\n

Cucumber<\/strong><\/h3>\n\n\n\n

World\u2019s leading tool for Behavior Driven Development. Cucumber uses Gherkin syntax that makes feature files easy and human-readable. Using Cucumber, we automated 220 scenarios and almost 34 feature files on four separate project modules.<\/p>\n\n\n\n

Jenkins<\/strong><\/h3>\n\n\n\n

For CI pipelines we use Jenkins. It provides hundreds of plugins to support building, deploying and automating. Also, Jenkins has great compatibility with Cypress Dashboard, so it\u2019s simple to monitor the run results not only using logs. Since the company requested testing of a few projects we had to configure a schedule and parallel run for each one.<\/p>\n\n\n\n

Jira<\/strong><\/h3>\n\n\n\n

As a tracking system, we chose Jira. It allowed us to easily record and track bugs and assign them at the right time with the bug tracking template. \u200b\u200bFor the customer, Jira allowed monitoring of work progress and always being up to date with team tasks through a sprint cycle. It helped all team members to keep everyone aligned on each issue’s status and ensure that the highest priority work is being tackled first.<\/p>\n\n\n\n

Achievements<\/h2>\n\n\n\n

We have already covered 85% of the current functionality of the product. Now we are on the way to gaining maximum coverage of the platform.<\/p>\n\n\n\n

Approximately, 94% of test cases are fully automated<\/strong>. Our team reported more than 50  bug reports<\/strong>. Over 800 Jira tickets have been covered by manual testing and 350+ automated tests<\/strong> were created. It takes 4-5 hours per day to execute everything. <\/p>\n\n\n\n

Overall client’s savings are comparable to the total of 4 Manual QA yearly work hours cost.<\/strong> <\/p>\n\n\n\n

We provided actual test results of the product state and reported 51 defects. We are still working with Workstride to ensure proper work of the platform and assist with the new updates and feature releases.<\/p>\n\n\n\n

Like in the case with Workstrike, our Automation QA team continues to bring the quality of products to the higher level for dozens of enterprise companies and startups in 8+ industries. <\/p>\n\n\n\n

If you need fast, continuous, and visible quality verification of your software, you can schedule a call and get a free POC, just drop us a note to hello@pecodesoftware.com<\/mark><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Empowering employees is a crucial part of their professional development. Sometimes it’s hard to track their progress properly, as different people must be rated according to their professional stack. This is where our partner Workstride steps in. However, when the solution becomes widespread and the product grows big, its requirements become big too. Especially, when […]<\/p>\n","protected":false},"author":1,"featured_media":762,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[11],"tags":[15],"class_list":["post-275","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-case-studies","tag-aqa"],"acf":[],"_links":{"self":[{"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/posts\/275"}],"collection":[{"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/comments?post=275"}],"version-history":[{"count":3,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/posts\/275\/revisions"}],"predecessor-version":[{"id":1393,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/posts\/275\/revisions\/1393"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/media\/762"}],"wp:attachment":[{"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/media?parent=275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/categories?post=275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pecodesoftware.com\/blog\/wp-json\/wp\/v2\/tags?post=275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}