Skip to main content
The TestDino support team is available to help with setup, troubleshooting, and platform questions.

Support Channels

Reach the team by email or join Discord.

Support Hours

DetailInfo
Hours9:00 AM - 6:00 PM IST, Monday - Friday
Response timeWithin 24 hours for all channels
Priority supportAvailable for Team and Enterprise plans
The team is distributed across timezones and responds to messages as quickly as possible.

Reporting Issues

When submitting a technical issue, include as much of the following as possible to speed up resolution.
1

Describe the issue

Explain what happened, what you expected, and how often it occurs (every run, intermittent, or one-time).
2

Include identifiers

Provide the Test Run ID or Dashboard URL for the affected run. Include the project name if not obvious from the URL.
3

Share environment details

Include your testing framework, framework version, CLI version (tdpw or testdino), and CI provider.
4

Attach evidence

Add screenshots, error messages with full stack traces, or CI execution logs. Redact sensitive data (tokens, credentials) before sharing.

What to Include

CategoryDetails
Issue frequencyEvery run, intermittent, or one-time
FrameworkPlaywright version, Node.js/Python version
CLI versionnpx tdpw --version or testdino --version
Run IDTest Run ID or dashboard URL
Error outputFull error message and stack trace
CI logsPipeline logs with sensitive data redacted
Configurationplaywright.config.js or playwright.config.ts settings

CLI Debug Mode

If the support team requests debug logs, enable verbose output:
npx tdpw upload ./playwright-report --token="your-token" --verbose
Share the full output with the support team. Redact API tokens before sharing.

Feature Requests

Submit feature requests through: Include the problem you are trying to solve, not only the feature you want. Context helps the team prioritize and design the right solution.

Security Issues

Report security vulnerabilities directly to [email protected]. Do not report security issues through public channels.

Resources

FAQs, changelog, and getting started.