CloudQA FAQ
CloudQA FAQ: Frequently Asked Questions
Answers to the questions teams ask most about CloudQA: what it is used for, how codeless tests are created and run, browser support, setup, and our managed QA services.
Jump to a topic
General questions about CloudQA
What is CloudQA used for?
CloudQA automates functional, end-to-end UI testing of websites and web applications, so you can check that the features your users see keep working. It covers regression testing, API steps inside UI tests and synthetic monitoring. CloudQA also offers managed testing services and load testing as a service on request.
CloudQA is codeless. How are the automated tests created?
You create test cases by using your site the way your users would. A test case includes steps such as clicking buttons, typing into fields and checks (for example, that a piece of text is visible). CloudQA records these interactions into modules you can reuse, which keeps your UI test suite easy to maintain.
Does CloudQA use AI? What about self-healing?
AI assists while you author tests, but every run executes the same predefined, auditable steps, so results are repeatable from release to release. Self-healing only starts after a step fails, and any recovery is reported so you always know what changed.
How does CloudQA differ from Selenium?
CloudQA is built on top of Selenium. Test cases are modular, like parameterized programming modules, and each can be updated separately. CloudQA combines the power of programmable tests with the ease of record and playback, without requiring code.
Why use CloudQA instead of Cucumber or RSpec with Selenium?
Most teams do not have the skills for scripted test automation, and teams that do rarely have the time: when software is released daily, scripted tests lag behind development. Traditional record-and-playback tools carry a heavy maintenance burden. CloudQA brings the concepts of scripted testing to non-programmers.
Is CloudQA a replacement for tools like Watir?
Yes. CloudQA performs end-to-end tests like Watir and Selenium, but does not require programming skills.
Is the iframe element supported by the recorder?
Yes. CloudQA handles iframes transparently, so you do not have to worry about them while recording.
Which browsers and platforms do tests run on?
Tests run in the CloudQA cloud in Linux and Windows environments, on Chrome, Firefox and Edge. You can also run tests on your own machine for free.
Do I have to run tests on my production site?
No. You can record tests on any URL CloudQA can reach, such as a staging server, and change the starting URL at any time. For example, record on your live site and point the test at staging, or the other way round. Private runs are available for applications behind a firewall.
What counts as a pass or a fail?
If a test case executes all of its recorded steps without failing, the run passes. If any step fails, the whole test case run is marked as failed.
Which browsers can I record tests in?
Recording is currently supported in Chrome. Recorded tests can then run on Chrome, Firefox and Edge.
Is there a free plan?
Yes. CloudQA has a free-forever Kickstart plan, and paid plans for growing teams. See CloudQA pricing.
Getting started
How do I install the CloudQA Chrome extension?
1. Register at app.cloudqa.io. 2. Install the CloudQA extension from the Chrome Web Store to start recording tests in Chrome. 3. Watch the video tutorials to configure and run your first test. 4. For any questions, email us or use the feedback button inside the application.
Where can I learn more about how CloudQA works?
See how CloudQA works, the video tutorials and the CloudQA documentation.
How long does it take to set up CloudQA for an existing web project?
You can create your first test case within 5 to 10 minutes of registering.
Does CloudQA work with my CI/CD pipeline?
Yes. You can run tests on demand, on a schedule, or from your CI/CD pipeline through the CloudQA APIs.
Managed QA services
I am interested in your managed testing services. What do I have to do?
Share the URL of the application to test and, optionally, links to three to five key areas. We analyze your application, tell you what automated coverage we can provide and what would remain manual, and help set up the initial test cases. You receive a video of the test runs, an analysis of how much time and effort automation can save, and metrics from the initial tests. Learn more about managed testing.
What testing services do you provide?
Functional testing (manual and automated), regression testing, performance and benchmark testing, and load and stress testing as a service on request.
Regression testing automation
What is regression testing automation?
Regression testing automation uses software tools to re-test an application automatically after it has been changed or updated, to confirm that existing features still work.
What are the advantages of automating regression tests?
Automated regression tests catch bugs introduced by enhancements or defect fixes, and side effects of changes in the environment such as data, operating systems, browsers or screen resolutions. They can run on every release without adding manual effort.
Why is regression testing automation needed?
Modern teams release often. Re-testing every feature by hand before each release is slow and error-prone, so automated regression suites let teams test and re-test changes quickly before they reach production. See automated regression testing with CloudQA.
Still have a question?
Tell us about your application and testing environment, and the CloudQA team will get back to you.