CloudQA is cloud-based test automation platform designed to significantly reduce time, cost and complexity of web testing process. This documentation will guide all the necessary information to learn about CloudQA methodology, best practices, use cases, as well as many tips that will allow you to get the most out of your CloudQA account.
For each account, testing in CloudQA is organized into Applications, Test Cases, Test Suite, Run History and Status.
An application is the main requisite defining a project in CloudQA. An "Application" basically defines what to test and where, along with a set of parameters that can be used to test multiple environments in different resolutions
A test case contains the settings and the list of steps to execute in order to test the application in a certain way. Test Cases can be created using the Recorder.
Test suite is a set of logically grouped test cases in a random or sequential order. Test suite allows to schedule set of test cases or invoke them through an API.
Run History is an illustration of test case execution. Run History has manual execution results, test suite, API Key and data driven results, which can be sorted in Executed by column in ruh history
When a test case is executed, it reveals the Status of the test case as pass/ fail. Status can be used to debug issues when a test case fails. A mouse hover on failed status displays error message and a click directs to the steps and screenshot so that error can be debugged.