General questions about CloudQA
CloudQA is used to automate functional end-to-end UI testing on web sites/apps, i.e. to check that the features which are visible to end users work as expected. CloudQA includes regression testing and performance monitoring.
Test cases are created by interacting with your site as your users would. A test case includes steps like clicks on buttons, typing in fields and checks (elements which are visible on the page, e.g. text). CloudQA records these interactions into modules that can be reused, thus building a highly maintainable automation test suite for your application’s user interface.
CloudQA is built on top of Selenium. CloudQA test cases are modular similar to programming parameterized modules, and test cases can be updated separately. CloudQA combines the benefits of programmable tests with the ease of record & playback.
Most teams don’t have the required skills for scripted test automation. The teams that do have these skills struggle to have the time for testing: when software is released daily, scripted tests constantly lag behind development. A simplified testing tool which allows easy test creation and maintenance without programming is needed. However, traditional record & playback tools are inadequate for agile teams due to their maintenance burden. CloudQA brings concepts from scripted testing and make it available to non-programmers.
Yes. CloudQA performs end-to-end tests like Watir and Selenium; however, CloudQA does not require programming skills.
CloudQA transparently handles iframes and you don’t have to worry about them when recording traces.
Tests are run in a Linux & Windows environment. Our default browser is Firefox however, we also offer the ability to run your tests with Chrome and IE.
No, you can record your tests from any URLs you choose. You could use, for example, a staging server — as long as that URL is accessible to CloudQA. The starting URL of a test can also be edited at any time. You could record a test on your live site, and then point it to a staging server, or vice versa.
If a test case executes all the steps recorded in it without failing, it is considered a success. If any one step fails, the entire test case run is considered a failure.
Currently, the only supported browser for the initial recording is Chrome. In future, we might add other browsers to the recording list.
Installation related Questions
You should be able to create your first test case in 5 to 10 minutes after registration.
Testing as a Service
Yes, we provide managed testing services. We would analyze your web application and tell you what coverage of automated testing can we provide and what would be the manual testing component.
We will assist you in setting up the initial test cases. For this, we will require the following
1. The URL of the application to test
2. Optionally, provide links to 3-5 areas of the application to be tested. Else we will randomly pick the test cases.
We will provide you with the following:
1. A video link of tests executions performed with CloudQA
2. An analysis of how effective automated testing is for your web application and how much time & effort you can save.
3. Metrics from the initial tests.
- Functional Testing (Manual & Automated)
- Load / Stress Testing
- Performance & Benchmark Testing
- Regression Testing