How-To GuidesCreate Test Manually

How to Create a Test Manually

Build test cases step-by-step using BugBrain’s visual editor. Perfect for specific test scenarios and custom workflows.

What You’ll Learn

  • How to use the test case editor
  • How to add and configure test steps
  • How to organize tests with tags and priorities
  • How to run your manually created test

Prerequisites

Creating Your First Test

1
Navigate to Test Cases
From your project dashboard, click 'Test Cases' in the sidebar.
2
Click 'New Test Case'
Click the 'New Test Case' button in the top right corner.
3
Enter Test Details
Give your test a descriptive name (e.g., 'User can log in with valid credentials') and add a description explaining what this test verifies.
4
Add Test Steps
Click 'Add Step' to create your first test step. You'll configure the action, target, and expected result.
5
Configure Each Step
For each step, select the action type (Navigate, Click, Type, Assert, Wait), specify the target element or URL, enter any required values, and add a description.
6
Set Priority and Tags
Choose a priority level (Critical, High, Medium, Low) and add relevant tags for organization (e.g., 'login', 'authentication', 'smoke').
7
Save Your Test
Click 'Save Test Case' to save your test to the project.

Common Test Steps

Navigate Step

Action: Navigate
Target: https://example.com/login
Description: Go to the login page

Type Step

Action: Type
Target: Input field with placeholder "Email"
Value: user@example.com
Description: Enter email address

Click Step

Action: Click
Target: Button with text "Sign In"
Description: Click the sign in button

Assert Step

Action: Assert
Target: Element with text "Dashboard"
Value: (empty)
Description: Verify dashboard heading is visible

Wait Step

Action: Wait
Target: 2
Value: seconds
Description: Wait for page to load

Best Practices

Tip 1: Use descriptive test names that clearly state what’s being tested

Tip 2: Break complex workflows into multiple smaller tests for easier debugging

Tip 3: Add assertions after important actions to verify expected results

Tip 4: Use consistent naming conventions for tags across your team

Organizing Tests

Using Priority Levels

  • Critical - Core functionality that must work (login, checkout, data integrity)
  • High - Important features used frequently by users
  • Medium - Standard features and secondary workflows
  • Low - Nice-to-have features or rarely used functionality

Using Tags Effectively

Good tagging examples:

  • By Feature: login, search, checkout, profile
  • By Test Type: smoke, regression, integration, e2e
  • By Platform: web, mobile, desktop
  • By Environment: production, staging, dev

Reordering Steps

You can drag and drop steps to reorder them:

  1. Hover over a step
  2. Click and hold the drag handle (⋮⋮ icon)
  3. Drag to the new position
  4. Release to drop

Editing Tests

To edit an existing test:

  1. Go to Test Cases
  2. Click on the test you want to edit
  3. Click the ‘Edit’ button
  4. Make your changes
  5. Click ‘Save Changes’

Running Your Test

After creating your test:

  1. Click the ‘Run Test’ button
  2. Wait for execution to complete (usually 10-60 seconds)
  3. Review results, screenshots, and logs
  4. Fix any failures and re-run

Learn more about running tests →

Next Steps

Troubleshooting

Can’t find element selectors?

  • Use the browser’s developer tools (F12) to inspect elements
  • Look for unique identifiers like IDs, data attributes, or text content
  • Use descriptive text-based selectors (e.g., “Button with text ‘Submit’”)

Tests are flaky?

  • Add Wait steps before assertions to allow pages to load
  • Use more specific selectors to avoid selecting wrong elements
  • Increase timeout settings in project configuration
OverviewGenerate Tests with AI