Why RocketQA?

Traditional testing frameworks require developers to write complex code, learn programming languages, and maintain intricate test suites. RocketQA changes this paradigm by allowing you to write tests in natural language that anyone can understand and maintain.

The Natural Language Approach

Instead of writing code like this:

await page.goto('https://example.com');
await page.fill('#username', 'testuser');
await page.click('#login-button');
await expect(page.locator('.welcome-message')).toBeVisible();

With RocketQA, you write this:

Feature: User Login
  Scenario: User can login successfully
    When navigate to "https://example.com"
    And type "testuser" into $loginPage.username
    And click $loginPage.loginButton
    Then $dashboard.welcomeMessage is visible

Living Documentation

Your tests become executable specifications:

• Features describe what your application does
• Scenarios document expected behavior
• Tests validate that documentation stays accurate

Shift-Left Testing

Enable everyone on your team to contribute to test automation:

• Product managers can write acceptance criteria as tests
• Designers can verify UI behavior
• QA engineers can focus on complex scenarios
• Developers can ensure features work end-to-end

Zero Configuration Philosophy

Start testing immediately without:

• Complex configuration files
• Framework-specific setup
• Programming language knowledge
• Build system integration

Page Object Pattern with YAML

Instead of maintaining page objects in code, define your locators in a simple YAML file:

loginPage:
  username: "#username"
  password: "#password"
  loginButton: "#login-btn"

dashboard:
  welcomeMessage: ".welcome"
  userProfile: "[data-testid='profile']"

Key Benefits

For QA Engineers

• No Coding Required: Write tests in plain English
• Fast Learning Curve: If you can write a user story, you can write a test
• Maintainable: Tests read like documentation

For Developers

• Zero Setup: Drop RocketQA into any project instantly
• Familiar Tools: Built on proven technologies (Cucumber + Playwright)
• VS Code Integration: Smart autocompletion, syntax validation, and navigation with the official extension
• Integration Ready: Works with existing CI/CD pipelines

For Teams

• Collaboration: Non-technical stakeholders can read and contribute to tests
• Documentation: Tests serve as living documentation
• Consistency: Standardized approach across all projects