Skip to main content

Testomat

Overview​

Testomat is our test management system that enables us to efficiently store, organize, and execute our test cases. It provides a centralized repository for test documentation, particularly for manual tests, ensuring that our testing processes are consistent and repeatable.

Purpose​

The primary purpose of Testomat in our quality workflow is to:

  • Store and organize test scenarios in a structured manner
  • Track both manual and automated tests in a single location
  • Facilitate test execution and recording of results
  • Maintain documentation for how to test our application
  • Provide a clear overview of our test coverage

Key Features​

Test Organization​

Testomat allows us to organize our tests with different classifications:

  • End-to-End Tests: Detailed test cases with well-described steps to reproduce that validate specific user flows (happy paths and negative paths)
  • Checklists: Simpler tests with concise summaries that are sufficient for verification
  • Status Tracking: Tests are categorized as either "automated" (implemented in code and run automatically) or "manual" (performed by a team member)

Test Runs​

Test runs in Testomat represent execution sessions for groups of tests:

  • Create test runs for specific testing sessions
  • Execute tests and mark them as passed, failed, or skipped
  • Add notes and comments to document test results
  • Track execution history

Labels and Organization​

Tests can be organized with labels for better categorization:

  • Playwright E2E tests
  • Storybook interaction tests
  • Other custom labels as needed

Demo Video​

The following video provides a walkthrough of Testomat and how we use it:

How We Use Testomat​

Our quality engineer is responsible for populating Testomat with various test scenarios, which serves as an important documentation resource for the team. Team members can:

  1. Review existing test cases to understand how features should be tested
  2. Execute manual tests following the documented steps
  3. Edit test cases when requirements change
  4. Export test suites for reference or reporting

Getting Started​

Accessing Testomat

To access Testomat, please contact Vova or Spencer for credentials, which will be shared securely.

Once you have access to Testomat...

  1. Navigate to the main test page to view all existing tests
  2. Review the different types of tests (end-to-end tests, checklists)
  3. Examine the test runs page to see execution history
  4. Familiarize yourself with the markdown-based test step format

Best Practices​

  • Review test cases before implementing new features to understand expected behavior
  • Update test cases when requirements change
  • When executing manual tests, document any unexpected behavior
  • Use the labeling system to organize tests by feature area or test type