Security and data
TestDetta runs in your CI and on your machines. Your source code and test results never leave them; coverage maps leave them only for your CI's cache storage. This page lists everything it stores. TestDetta itself makes no network calls.
What stays in your CI
- The analysis of your diff and source code.
- Coverage maps: which test class ran which method, and how long each class took. They name your types, methods and test classes, so treat them like build artifacts.
- Test runs and their results.
td recordinstruments assemblies in the test project's build output while it runs: your repository's, and third-party ones there that read files. It backs up the originals in a temporarytestdetta-record-*folder first and puts them back at the end, also when the recording fails. It also copies its runtime into the build output and lists it in the test project'sdeps.json, both undone at the end, and the test process sets a startup hook (DOTNET_STARTUP_HOOKS) for the .NET processes the tests start, so that each reports which test started it.td auditrewrites assemblies only in its own copy of the working tree; your sources and build output are only read, and the copy is deleted at the end.
Where it keeps files
| Path | Contents |
|---|---|
.testdetta/coverage/ | Coverage maps of the current commit, one per test project |
.testdetta/cache/ | A cache of the evaluated project graph |
--maps-dir folder | Maps of earlier commits, one folder per commit, kept where you choose |
.testdetta/testdetta-audit.json | td audit's report (or --report); .testdetta/testdetta-shadow.json is shadow mode's |
testdetta-record-* in the temporary folder | While td record runs: the original assemblies of the test project's build output, put back and deleted at the end |
td-audit-* under --work-dir (/tmp) | While td audit runs: a copy of the working tree, readable only by your user, where code is broken on purpose and tested. Deleted at the end, or by the next audit after a crash |
testdetta-shadow-* in the temporary folder | While td test --shadow runs: copies of the test reports, the reruns' results and a checkout of the base commit (a git worktree). Deleted at the end, also after Ctrl+C or a cancelled job. Your results directory and your own reports are left as they are; the TRX reports shadow mode asks for itself are deleted once read |
On GitHub Actions, maps are stored in your repository's Actions cache. .testdetta/coverage/ and .testdetta/cache/ are generated; keep them out of version control.
No network calls
TestDetta itself makes no network calls: no license check, no renewal, no usage data. What uses the network in a job is not TestDetta's own: the GitHub Action downloads the TestDetta package from nuget.org, checked against the SHA-512 it pins, and lists and restores the coverage maps in your Actions cache; your builds restore packages as usual, shadow mode's rerun on the base commit restores that commit's packages like any build, and the audit's builds and test runs in its copy restore packages the same way.
The source code
TestDetta is open source under the Apache License 2.0, so you can read what it does before you run it, and build it yourself. The source is on GitHub; see License.
What we keep
Nothing about your use of TestDetta. There is no license, account or trial, so we hold no record of who uses it or where. What this website and email support process is in the privacy policy.
Reporting a vulnerability
Email support@testdetta.com rather than opening a public issue. Please give us time to fix it before you publish.