This page is under construction. More content coming soon!
Why Organization Matters
A well-organized test suite is:
- Easy to navigate: Find tests quickly
- Maintainable: Clear structure makes updates simple
- Scalable: Grows cleanly as product expands
- Collaborative: Team can work efficiently
Poor organization leads to duplicate tests, missed coverage, and wasted time.
Organization Methods
OneTest provides multiple ways to organize tests:
Folders
Hierarchical structure for logical grouping
Tags
Flexible labels for categorization
Custom Fields
Product-specific metadata
Folder Structure Strategies
By Feature
By User Journey
By Test Type
Hybrid
Organize by Product Features
Recommended for most teams.📁 Authentication
📁 Login
✅ Valid credentials
✅ Invalid password
✅ Locked account
📁 Registration
✅ New user signup
✅ Email verification
📁 Password Reset
✅ Request reset link
✅ Reset with valid token
📁 User Profile
📁 View Profile
📁 Edit Profile
📁 Upload Avatar
📁 Products
📁 Browse Products
📁 Search Products
📁 Product Details
📁 Reviews
📁 Shopping Cart
📁 Add to Cart
📁 Update Quantity
📁 Remove Items
📁 Checkout
📁 Shipping Information
📁 Payment
📁 Order Confirmation
- Mirrors product structure
- Easy for new team members
- Scales well
Cons:
- May need reorganization after refactoring
Organize by User Flows
Good for customer-centric products.📁 New User Journey
✅ Discover product
✅ Sign up
✅ Complete onboarding
✅ First action
📁 Purchase Journey
✅ Browse catalog
✅ Add to cart
✅ Checkout
✅ Payment
✅ Confirmation
📁 Return User Journey
✅ Login
✅ View history
✅ Repeat action
✅ Logout
📁 Admin Journey
✅ Login as admin
✅ Access dashboard
✅ Manage users
✅ Generate reports
- Reflects real user behavior
- Easy to identify gaps
- Clear end-to-end scenarios
Cons:
- Tests may span multiple features
- Can have overlapping tests
Organize by Testing Type
Common in mature testing organizations.📁 Functional Tests
📁 Smoke Tests
📁 Regression Tests
📁 Integration Tests
📁 Non-Functional Tests
📁 Performance Tests
📁 Security Tests
📁 Usability Tests
📁 Accessibility Tests
📁 Platform Tests
📁 Web Tests
📁 Mobile - iOS
📁 Mobile - Android
📁 API Tests
📁 Environment Tests
📁 Dev Tests
📁 Staging Tests
📁 Production Smoke Tests
- Clear separation of concerns
- Easy to run specific test types
Cons:
- May duplicate structure
- Less intuitive for new team members
Combine Multiple Strategies
Most flexible approach.📁 Smoke Tests (by type)
✅ Login
✅ Homepage loads
✅ Add to cart
✅ Checkout
📁 Features (by feature)
📁 Authentication
📁 Products
📁 Orders
📁 User Journeys (by flow)
📁 First-time Buyer
📁 Returning Customer
📁 Platforms (by platform)
📁 Web
📁 iOS App
📁 Android App
- Maximum flexibility
- Accommodates different needs
Cons:
- Can become confusing
- Requires discipline to maintain
Effective Tagging Strategy
Tags provide cross-cutting categorization:
Naming Conventions
Test Case Titles
Folder Names
Tags
Clear, Descriptive Titles
Format: Verify [action] [condition] [expected result]✅ Good Examples
Verify user can login with valid credentialsVerify error message displays for invalid email formatVerify shopping cart updates when quantity is changedVerify checkout completes successfully with credit card
❌ Bad Examples
Login test ← Too vagueTest #47 ← No contextCheck if it works ← What is “it”?User does something and sees a thing ← Too generic
- Start with action verb: “Verify”, “Validate”, “Confirm”
- Include condition being tested
- Be specific about expected outcome
- Keep under 80 characters if possible
Folder Naming
Rules:
- Use Title Case:
User Profile, not user profile
- Be concise but descriptive
- Avoid abbreviations unless universal (e.g., “API” is okay)
- Use plurals for collections:
Products, not Product
Examples:✅ Good:
📁 Authentication
📁 User Management
📁 Product Catalog
📁 Payment Processing
❌ Bad:
📁 auth (unclear abbreviation)
📁 User_Management (underscores)
📁 product catalog (not title case)
📁 paymentprocessing (no spaces)
Tag Naming
Rules:
- Use lowercase
- Use hyphens for multi-word tags:
smoke-test, not smokeTest
- Be consistent across team
- Avoid redundant tags
Examples:✅ Good:
smoke, regression, critical, login, checkout, ios, android
❌ Bad:
Smoke (capitalized)
smoke_test (underscore)
smokeTest (camelCase)
smoke-tests (plural when others are singular)
Maintenance Best Practices
Regular Audits
Review test suite quarterly:
- Remove obsolete tests
- Update outdated tests
- Consolidate duplicates
- Fix organizational issues
# Find old draft tests
status = draft AND created_at < -90d
# Find tests without folders
folder_id IS NULL
# Find untagged tests
tags IS NULL OR tags = []
Ownership
Assign test ownership:
- Feature teams own their feature tests
- QA owns smoke/regression suites
- Individuals own exploratory tests
Use custom fields to track ownership: owned_by: "payments-team"
Documentation
Document your structure:
- Create folder descriptions
- Define tag meanings
- Maintain test suite README
- Train new team members
Automation
Automate organization tasks:
- Auto-tag based on folder location
- Bulk move tests between folders
- Generate coverage reports
- Alert on orphaned tests
Common Anti-Patterns
Avoid these common mistakes:
Problem: Deeply nested folders (>5 levels)❌ Bad:
📁 Web
📁 Desktop
📁 Chrome
📁 Windows
📁 Authentication
📁 Login
📁 Valid Credentials
✅ Test
Inconsistent Organization
Problem: Some tests organized one way, others differentlySolution: Choose a strategy and stick to it. Migrate existing tests.
Problem: Too many tags (>10 per test)Solution: Use only meaningful tags. Remove redundant ones.
Problem: All tests in root folderSolution: Start organizing today! Create basic folders.
What’s Next?
