Rainforest QA — Simplify Test Scheduling

Overview

Rainforest QA is a low-code QA testing platform. This project started with findings from the data analysis. We found that customer stickiness noticeably improves after users try out the scheduling feature. As a result, we decided to focus on improving the test scheduling feature.
The goals of this project are to;

• Increase discoverability and ease of use of the test schedule feature
• Simplify the existing flow
• Validate the initial finding
• and ultimately increase customer stickiness

Design process

Auditing the existing user flow

1.Discoverability issue

It is hard to discover the call-to-action as it is buried in the settings pages;

• To find it in the run group page: go to the Test page, then select the Run group tab, choose a run group, and click the Edit button.
• To find it in the setting page: go to the Test page, click the Setting sidebar menu, and then click the Schedule Run Group sidebar menu.

2.Lack of call-to-action in the expected areas

• Visual editor page: where users view or edit tests
• Test page: list of all tests created in the account
• Run creation modal: where users set up their runs

3.Scheduling could be integrated into the onboarding process

It makes a lot of sense to introduce one of Rainforest QA’s core features during the onboarding.

4.Only one run time can be set per run group

Users have been requesting the ability to set multiple run times for each run group, so we have decided to include it in the scope.

Ideation & User flow

Why I start with a user flow?

• User flow can be created relatively quickly.
• It helps us identify areas for improvement quickly.
• It aids in visualizing the high-level design structure, which is very helpful.
  • Developers can start planning and estimating.
  • Project Managers can plan more easily.

Solution overview

Based on our findings and research, we decided to;

• Strategically add the scheduling call-to-action in areas that are useful for the users.
• Increase discoverability and ease of use
• Allow users to add more than 1 run time/day/run group

Solution details breakdown

“New Run Group” modal

• Added “Schedule” section in the modal
• Added a banner to inform that the user can schedule test with CLI

Enhanced scheduling flexibility

• Users can now schedule multiple run times.
• Default settings reduce decision fatigue, with a default schedule of daily runs at 10 AM.

Test writing page

• Added “Schedule using a Run Group” as a secondary CTA.
• Updated copy to clarify that scheduling is exclusively through Run Groups.

Test page actions

• Added “Schedule by creating a new Run Group” to the bulk action dropdown.

Onboarding flow

• Added “Schedule Your Test” as the final step in the onboarding process to introduce new users to Rainforest QA’s core workflow: “Create - Schedule/Run - Review Test Results.”

“Add Test to Run Group” modal

• Added a “New Run Group” button to streamline the process. Users no longer need to close the modal, create a new Run Group, and then add a test.