Check that every step is complete and connected to the Start node. Conditions also need valid paths for the outcomes used by the test.
Creating tests
Build tests by describing browser actions and checks in plain English, then connecting them into a visual flow.
Create a test
Tests save automatically while you work.
Open Tests in your project.
Create a test and give it a clear name.
Select the Start node to configure the test.
Select Add step to add the first instruction.
Connect the steps in the order the agent should run them.
Use folders to organise related tests and reusable components. Running a folder runs its tests, but not its reusable components on their own.
Configure the test
The Start node controls the browser and account used for the whole test.
Description explains the purpose of the test.
Files gives the agent files to inspect or upload during the run.
Viewport chooses a desktop, tablet or mobile browser size.
Live user is used when the test runs against Live.
Test user is used for Test and custom branches.
Timeout sets the maximum time allowed for the complete run.
Add test steps
A Test step tells the agent what to do or what to check.
Give each step a short name, then add the exact details the agent needs. Include expected text, values and outcomes when they matter.
Choose what should happen if the step fails:
Stop on failure ends the run and cancels the remaining steps.
Continue on failure records the problem and continues to the next available step.
Keep each step focused on one action or check. This makes failed results easier to understand.
Add conditions
A Condition sends the agent down different paths based on what it finds.
Add a step and select Condition.
Name the action the agent should perform.
Describe what must be true for the condition to be met.
Connect the green output to the steps for a met condition.
Connect the red output to the steps for a condition that is not met.
Only the matching path runs. Steps on the other path are skipped.
Reuse common flows
A reusable component holds steps you use in several tests, such as logging in or opening the same page.
Create the shared flow in the same builder and enable Reusable component on its Start node. Add it to another test with Add component or by changing a step to Component.
During a run, Buildprint expands the component into its steps and groups their results together.
Create test users
Test users give the browser a reusable account for Live or development data.
Open Users, or select Create test user from the Start node.
Enter a name and choose the database.
Enter the Bubble user's email address.
Choose Log in with password or Log in automatically.
Add the test user.
Log in with password stores credentials for login steps. Log in automatically starts the run as that Bubble user.
Fix builder errors
The test will not run
The wrong account is used
Check the database selected on the test user, then assign it to the matching Live or Test field on the Start node.
A component is not available
Open the shared flow and confirm that Reusable component is enabled on its Start node.