Testspace

Testspace suits software teams that want automated results, manual test cases, and exploratory findings connected to their development workflow. Its mix of testing approaches and reporting is a strong fit for teams within its session limits; high-volume teams and those needing encrypted database storage should look elsewhere.

Overview

Testspace combines test management with result publishing and analysis. It can bring automated runs, Markdown-based manual tests, and observations from exploratory sessions into one workspace. That breadth helps teams coordinate different testing activities, but the 30-day data retention and plan-specific session caps limit its appeal as a long-term test archive or for heavy usage.

Key features

Results and analysis

The dashboard organizes automated results, including results aggregated from parallel jobs. It accepts JUnit, NUnit, Visual Studio TRX, and xUnit.net output, with framework support spanning tools such as Google Test, Jest, pytest, and RSpec. Metrics, graphs, reports, analytics, insights, execution trends, failure analysis, and flaky-test detection help teams examine testing activity and recurring failures. Results are retained for 30 days, so teams needing a longer history will need another record-keeping approach.

Manual testing and integrations

Manual tests can be authored as Markdown in Testspace or kept in connected repositories, while exploratory sessions capture observations and usability issues. GitHub, GitLab, and Bitbucket integrations connect source control and issue workflows; CI/CD support includes GitHub Actions, GitLab CI, Jenkins, Circle CI, Azure Pipelines, and Buildkite, among other listed integrations. The command-line client runs on Windows, Linux, and macOS.

The REST API manages projects and spaces, but publishing test results requires the Testspace client. That distinction matters for teams planning custom publishing workflows: API access alone does not cover result submission. The privacy policy says data is encrypted in transit with SSL/TLS, while live database data is not encrypted. Technical support is provided only by email.

Pricing

The Free plan costs nothing and is aimed at open-source projects using a personal GitHub account. It allows unlimited public projects and 200 sessions, but its open-source and account requirements make it a poor fit for private commercial testing.

Basic costs $32 a month for 4 users, 2 private projects, unlimited public projects, and 200 sessions. It is the entry point for a small team that needs private projects, but the two-project and four-user limits can constrain growth. Premium costs $120 a month and raises the allowance to 20 users, unlimited projects, and 1000 sessions, with priority support. It suits larger teams needing more room and priority support, though the higher price makes the added capacity most relevant when Basic's caps are restrictive.

Enterprise uses custom pricing and includes multiple subdomains, SSO support, priority support, and unlimited sessions. Accounts generating more than 1 million test cases per month need an Enterprise account, making that threshold important for high-volume teams. A 14-day trial is available. Session limits remain a key distinction between the Free and Basic plans at 200 sessions and Premium at 1000.

Platforms

Testspace is available on web and through an API, with client platforms for Windows, Linux, and macOS. These options suit teams working across common desktop environments, while result publishing still depends on the client rather than the API alone.

Who it's for

Testspace is a sensible choice for development teams that want a shared place for automated results, repository-based manual tests, exploratory observations, and test analysis. It is less suitable for teams that exceed the 1-million-test-case monthly threshold, need more than 30 days of retained results, or require live database encryption.

Pros and cons

• Pros: Combines automated, manual, and exploratory testing workflows, reducing the need to separate those activities across tools.
• Pros: Aggregates parallel-job results and offers trend reporting, failure analysis, and flaky-test detection for investigating test activity.
• Pros: Connects to major source-control and CI/CD services and supports widely used test output formats and frameworks.
• Cons: Free and Basic both cap usage at 200 sessions, while Basic also limits teams to 4 users and 2 private projects.
• Cons: Result publishing requires the client, even though a REST API is available for project and space management.
• Cons: Data retention is 30 days, and live database data is not encrypted.

Alternatives

Test Analytics Software is a useful category page for comparing tools in this area.

• ReportPortal is worth considering if an open-source, self-hosted community edition with Docker, Kubernetes, or Google Cloud Marketplace deployment is a priority.
• TestBeats is an alternative with Pro plans priced at $18 a month for 200 credits and $39 a month for 500 credits.
• Qualflare offers a free Starter plan capped at 1 project, 1 active user, 200 test cases, and 100 test reports, which may suit a very small project.
• Allure Report is a free, open-source reporting tool under the Apache License 2.0.
• Buildkite may be preferable when the priority is a CI platform with a free plan for up to 5 users and 10 concurrent jobs.
• Tesults has a free plan with a lifetime term, which may suit teams seeking a permanently free option.
• BuildPulse is a paid alternative with a free trial and runner minutes, suited to teams looking for runner-focused pricing.
• UReport offers a free self-hosted Community plan with 5 seats, 3 product lanes, and 3 dashboards, making it an option for teams that want a self-hosted setup.

Verdict

Choose Testspace if your team wants automated, manual, and exploratory testing gathered with useful reporting and development integrations. Its main advantage is that range of testing workflows; its main drawbacks are limited retention, session caps, client-dependent result publishing, and unencrypted live database data. Teams with high test volume, longer history needs, or stricter database-security requirements should look elsewhere.