The Period Charges section of the billing page has been expanded to include:
All embedded tests have been automatically migrated to become Reusable Snippets.
Reusable Snippets are similar to embedded tests — they're building blocks that make it easy to quickly create and maintain tests that contain common user flows. When you edit a Snippet, changes propagate to any tests (or other Reusable Snippets) that contain that Snippet.
You can create Reusable Snippets from scratch or by extracting steps from existing tests.
In the new Reusable Snippets tab in the Tests page, you can manage your Snippets and see where each of them is being used in your test suite.
Other recent improvements:
Starting today, everyone signing up for Rainforest QA will have access to branching.
Branching is a version control system for Rainforest tests. You can edit and preview tests while the rest of your test suite remains stable, and the rest of your team can continue to run tests, uninterrupted by your experiments.
With branching, you can continuously maintain and update your Rainforest tests as easily as you maintain and update your code. Your code and your tests now move at the same speed.
We'll continue to add features and improvements to branching, including better support for CI/CD pipelines.
Other recent improvements:
You can now schedule tests in bulk and directly from the Visual Editor via the Run Test drop-down.
Other recent improvements:
You can now schedule Run Groups to run automatically up to multiple times per day, an option that was previously only available via the API.
Other recent improvements:
When it comes to test automation, it’s inevitable that tests sometimes fail. It happens for many reasons: bugs, UI changes, environment issues, random errors. Successful teams use a clear process to keep their test suites maintained and healthy, investigating and addressing all failures quickly to prevent them from recurring.
We’re excited to announce new features that makes it easy for you to stay on top of test failures and collaborate on test results with your team.
Failure status
In the Results page, see which of your test failures still need to be resolved in the new “Failure Status” field, and mark what’s been addressed as Resolved.
Assigning test failures
When failures happen, it’s important someone is responsible for investigating and resolving them. Assign (or re-assign) team members to resolve each failure.
New Tasks page
Keep track of all test failures that need attention on the new Tasks page, a built-in todo list.
Broken test reminders
We always recommend disabling broken tests so they don’t cause noisy results. However, if you allow broken tests to keep running, we now remind you that the test has open failure tasks from previous runs. No more guesswork; you’ll immediately know the cause of the test failure.
Summaries of resolved run failures
See at a glance in the Results page which runs have been cleared by your team, and those that still have failures that need attention.
Other recent improvements:
When a test fails due to webhook (mis)configuration, Rainforest now shows a notification describing the issue and providing next steps to resolve the issue.
Formerly, when choosing an action like Click, you'd then have to click the Element icon to enable screenshot capture.
Now when you choose any action that requires a screenshot, screenshot capture will be enabled immediately upon choosing the action. No more having to click the Element icon.
Other recent improvements:
You can now use the rainforest-run-info NPM package (also available on Github) to get the run ID and test ID in your client-side code for every test you execute.
This can connect events in Sentry and other logging tools to your Rainforest test runs. When investigating errors, your developers will be able to go directly to the appropriate reproduction videos in Rainforest.
We also now add HTTP headers (X-RAINFORESTQA-TEST-ID, X-RAINFORESTQA-RUN-ID, and X-RAINFORESTQA-RUN-TEST-URL) to all outgoing requests during testing so you can access this information in more places.
It’s difficult to grab screenshots of elements when they’re moving, temporary, or require a hovering cursor (like a drop-down menu).
We’ve made it easier with the introduction of VM freeze-frames. Press the Esc key or click the new Freeze Screen button to create a frozen image of the VM in which you can capture screenshots. To unfreeze the image, simply press Esc again or click the Unfreeze Screen button.
This feature freezes the image on screen, but not the VM itself. The VM will keep running in the background, so when you unfreeze, you’ll see the latest state of the machine.
