Skip to main content
This page is under construction. More content coming soon!

​
Creating Test Cases

There are multiple ways to create test cases in OneTest.

​
Methods

​
Test Case Components

Title: Short, clear summary of what’s being tested
✅ Good: "Verify user can login with valid credentials"
❌ Bad: "Login test"
Description: Detailed explanation of the test purpose and scope
Each step should have:
  • Action: What the tester should do
  • Expected Result: What should happen
Example:
1. Navigate to login page → Login form is displayed
2. Enter valid username → Username field accepts input
3. Enter valid password → Password is masked
4. Click Login button → User is redirected to dashboard
What must be true before running this test:
  • User account exists
  • User is not logged in
  • Test data is available
Specific data needed for this test:
  • Username: test@example.com
  • Password: Test123!
  • Expected role: Admin
Tags: Categorize for easy filtering
  • smoke: Critical path tests
  • regression: Run before releases
  • feature-name: Group by feature
  • priority-high: Urgent tests
Folders: Hierarchical organization
  • Authentication/Login/Valid Credentials
  • Checkout/Payment/Credit Card

​
Best Practices

Be Specific

Clear, unambiguous steps that anyone can follow

Single Purpose

One test case should verify one thing

Use Tags

Tag appropriately for easy filtering and test suite creation

Link Requirements

Connect tests to user stories or requirements for traceability

​
What’s Next?

Running Tests

Execute your test cases

AI Best Practices

Get more from AI generation