Best Practices to Use CloudQA

1. Do not Automate Every Test Case

• Automation tools are inevitable, but they might not offer solutions to every problem in testing. Thus, you should never rely entirely on automation tools.
• Many think that if they pick the right automation tool, they can automate anything. Nonetheless, not all tests can be automated. Automation Testing can reduce manual testing but not eliminate it.

2. Create Independent and Simpler Tests

• Dependencies will make tests hard to understand. Handling dependent tests become challenging when they are run in parallel as the parallel tests are initiated at the same time.
• Complex tests are difficult to maintain. An ideal automated test in CloudQA should limit to 50 - 60 steps, and beyond that, it becomes hard to debug on failures.

3. Create Tests That Are unaffected to UI Changes

• *In the initial phase, an application has frequent UI changes and releases. It takes a toll on existing automated tests and hampers the tests on every build.

4. Remove Flaky Tests

• To achieve consistency, companies shift to automation testing. If a test fails, the testing team has to debug the issue, fix, and recheck if it's working.
• It is better to avoid test with the inconsistency, which eats a lot of time for debugging than testing.

5. Use Assertions/Validations End of Every Test

• Assertions in CloudQA are added in every test case to validate if specified text or value is coming up during execution.
• Assertions at the end will remove false positives and improves accuracy during test execution.

6. Build a Technique using CloudQA’s Advanced Features

• Not just automating tests, creating with proper technique is essential. Leverage options like Store variables, Application variables, scripts, data-driven tests, etc.., which can help you build tests which can save a lot of execution time.

7. Run your Tests Frequently

• The main goal of choosing an automation Tool is to test constantly to find bugs early and get it fixed. Do not wait for the entire automation setup; run them as and when created.
• Test Suites in CloudQA accommodates to run multiple test cases/test suites on-demand, schedule, invoke via API, and integrate with CI/CD.

8. Name your tests judiciously

• The test case name has to be precise to explain the functional piece being tested. Why is it important? You should be able to understand what the test case does after a year too. Addition it would also help your new team members to understand the setup better.
• In hundred tests, if a few of the tests fail, it has to clear which is the broken functionality by looking at the test case name.
• Also, use tags, descriptions for a test case, and a test step, priority in CloudQA, to make testing sorted.

9. Assure That Test Automation Ownership is Collaborated

• Don't just one engineer own up managing an automation tool. Multiple people in the team should be able to access the application, so that team members are aware of the test case setup and give in their ideas on it. Use CloudQA's User Management feature to collaborate with your team and work collectively.