TestOwl LogoTestOwlDocs

How to Send Feedback to the TestOwl Team

We build TestOwl directly in response to how quality engineering teams work. Whether you have an idea for improving the Step Editor, a request for a new CI/CD runner integration, or thoughts on how we can make test failure diagnosis faster, sharing your feedback helps shape our product roadmap.

Learn more about TestOwl's product vision and roadmap on our main platform resources.

When to send feedback vs reporting an issue

Before submitting, determine whether your message is a product suggestion or a technical problem:

  • Send Feedback: Use feedback for workflow improvements, feature suggestions, UI polish requests, or suggestions for additional pre-built assertions. Feedback goes directly to our product and design team for roadmap evaluation.
  • Report an Issue: If a test step failed unexpectedly, a video recording is missing, or the platform produces an error, submit a bug report instead. See How to Report an Issue.
  • Urgent Production Support: If you are experiencing an outage affecting critical automated deployment gates, contact our technical team directly. See Contact the TestOwl Support Team.

What makes feedback actionable

The most impactful feedback explains the underlying objective rather than just a requested button or toggle. High-value feedback answers three questions:

  1. 1
    What workflow are you trying to accomplish? (e.g., "Our QA team runs smoke tests across 12 localized regional staging URLs every morning.")
  2. 2
    Where does the current experience create friction? (e.g., "Manually selecting each environment across 5 different suites takes 10 minutes.")
  3. 3
    What is the business impact? (e.g., "Batch triggering across environment matrices would save our release engineers 30 minutes per deployment cycle.")

Step-by-step: Submitting feedback from the app

You can submit feedback without leaving your current workspace:

  1. 1
    Click the Help & Feedback icon (question mark) in the bottom-left corner of the sidebar navigation.
  2. 2
    Select Send Feedback from the slide-out menu.
  3. 3
    Choose a category: Feature Request, User Experience Improvement, or General Thoughts.
  4. 4
    Type your feedback in the description field. Be as specific as possible regarding the project context.
  5. 5
    (Optional) Check Include current page URL so our product designers know which screen prompted your thoughts.
  6. 6
    Click Send Feedback.

Worked example: High-impact feature suggestion

Here is an example of an actionable, well-structured feedback submission:

Category: Feature Request
Topic: Bulk tag management across Test Suites
Current Friction: Currently, to add the #release-2.4 tag to 20 test cases, I have to open each test case individually and add the tag manually in the settings panel.
Suggested Solution: Allow multi-select checkboxes on the Test Cases list view with a "Bulk Apply Tag" action bar.
Team Impact: We tag tests weekly during sprint planning; bulk editing would eliminate repetitive manual work across our 6 QA engineers.

What happens after you send feedback

Every feedback submission is automatically routed to our internal product management queue:

  • Triage: Our product team reviews submissions weekly and tags them against active roadmap initiatives.
  • Clarification: If we need additional context on your specific enterprise workflow, a product manager may reach out via the email address linked to your TestOwl account.
  • Roadmap Updates: When your suggested capability is scheduled for development or enters private beta, we notify you directly with early testing access.

Common problems and misconceptions

  • "I submitted feedback but haven't received a technical troubleshooting reply." Feedback submissions are reviewed for product planning and feature enhancements. If you need technical assistance or suspect a software defect, submit an issue via How to Report an Issue or reach out to Support.
  • "Can external contributors vote on features?" In addition to in-app feedback, we periodically conduct roadmap review sessions with enterprise customer councils. Contact your account manager to participate.

Last updated:

Maintained by the TestOwl product team.