Frequently Asked Questions
FAQ, answered.
Everything you need to know about how TestCoverNet works, what it touches, and what it costs.
What does TestCoverNet do?
TestCoverNet connects to your repository, either for a one-time onboarding of your main branch or via pull-request webhooks. It builds a deterministic test plan, generates high-accuracy unit, integration and smoke tests for untested invariants and regressions, and verifies that every generated test compiles, passes and exercises the intended code before it is proposed. It runs on every pull request, so your coverage keeps climbing and regressions are caught before they merge.
Which languages and frameworks are supported?
Support launches with C#, followed by Rust and Dioxus. If you'd like your stack supported, email the team and we'll give you a straight answer rather than a guess.
Do you need write access to my code?
No. TestCoverNet operates with read-only access to your codebase. Generated tests are proposed as pull requests that your team reviews and merges — nothing lands without your approval.
Will the generated tests actually be readable and maintainable?
That's the point. TestCoverNet writes focused tests that pin real behaviour, not brittle snapshots that break on every refactor. Every test is verified to compile and pass before it's proposed, and your team reviews every test before it lands.
How does it fit into CI?
TestCoverNet integrates with GitHub, GitLab, Gitea and Bitbucket and runs automatically on every pull request, flagging regressions and reporting coverage over time. Always on, with no manual triggering and no changes to your existing pipeline.
Is TestCoverNet private and secure for our code?
Yes. Access is strictly read-only, your code is analysed in isolated, network-restricted environments, and no repository snapshots are retained after a run completes. The service is deployed on major US cloud providers following security best practice.
Is my code used to train AI models?
No. Your code is never used to train AI models. TestCoverNet is built for teams that take code privacy seriously, with read-only access and strict privacy controls, and all generated tests belong to you.
How much does optional main branch onboarding cost?
Main-branch onboarding is optional and billed per source file we cover. For C# repositories it's USD $80 per covered file, where a file counts as covered once its generated unit, integration, and end-to-end tests pass and are accepted by your team. A typical 150-file C# service works out to USD $12,000, and you only pay for files we successfully cover.
How much does pull-request coverage cost?
Pull-request coverage is billed per source file we cover — for C#, USD $30 per covered file, not for every file the PR touches. A file counts as covered once its generated tests pass and your team accepts the pull request — you only pay for coverage you keep. Monthly volume pricing is available for high-change repositories. See the pricing section on the home page, or email us for a quote.
When will high-accuracy test coverage be available?
C# support will be available in late 2026, with Rust and Dioxus following in 2027.
What happens if we already have some test coverage?
TestCoverNet detects your existing tests and generates only the coverage that's missing — it never duplicates work your team has already done.
Still have a question?
Email us and we'll answer straight — even if the answer is "not yet".
admin@testcovernet.com