dotnet/maui · error · Exception

All tests are marked inconclusive, no tests ran. There is pr

Error message

All tests are marked inconclusive, no tests ran. There is probably something wrong with running the tests.

What it means

Thrown by FailRunOnOnlyInconclusiveTests when the total test count equals the inconclusive test count. This detects the dangerous case where the test runner reports success (no failures) but in reality every test was skipped/inconclusive — i.e. nothing actually ran, hiding a broken test setup.

Source

Thrown at eng/devices/devices-shared.cake:152

{
    Information($"Looking for .apk files in {directory}");
    return GetFiles($"{directory}/*-Signed.apk").Select(file => file.FullPath);
}


void FailRunOnOnlyInconclusiveTests(string testResultsFile)
{
    // When all tests are inconclusive the run does not fail, check if this is the case and fail the pipeline so we get notified
    var totalTestCount = XmlPeek(testResultsFile, "/assemblies/assembly/@total");
    var inconclusiveTestCount = XmlPeek(testResultsFile, "/assemblies/assembly/@inconclusive");

    if (totalTestCount == null)
    {
        throw new Exception("Could not find total or inconclusive test count in test results.");
    }
    if (totalTestCount.Equals(inconclusiveTestCount))
    {
        throw new Exception("All tests are marked inconclusive, no tests ran. There is probably something wrong with running the tests.");
    }
}

void CleanResults(string resultsDir)
{
    Information($"Cleaning test results: {resultsDir}");

    if (!IsCIBuild())
    {
        CleanDirectories(resultsDir);
    }
    else
    {
        // Because we retry on CI we don't want to delete the previous failures
        // We want to publish those files for reference
        DeleteFiles(Directory(resultsDir).Path.Combine("*.*").FullPath);
    }
}

View on GitHub (pinned to f377ff1c5e)

Solutions

1. Open the results file and read the skip reasons / messages for the inconclusive tests to find the root cause.
2. Check that the test platform/category filters and the target device/app allow tests to actually execute.
3. Verify the app-under-test launched successfully (for UI tests) — a crashed app often makes all tests inconclusive.
4. Confirm the test adapter version matches the test framework; adapter mismatches can mark all tests inconclusive.

var total = XmlPeek(testResultsFile, "/assemblies/assembly/@total");
var inconclusive = XmlPeek(testResultsFile, "/assemblies/assembly/@inconclusive");
if (total != null && inconclusive != null && total.Equals(inconclusive) && int.Parse(total) > 0)
    Warning($"All {total} tests inconclusive — investigate test discovery/execution before trusting this run.");

When it happens

Trigger: totalTestCount != null AND totalTestCount.Equals(inconclusiveTestCount) — every reported test is inconclusive, so the run effectively validated nothing.

Common situations: All tests are filtered out or skipped due to a missing platform/category mismatch; the test adapter failed to discover/load tests but marked them inconclusive; a [Fact(Skip=...)] or platform-guard caused every test to skip; the app under test crashed before any test could run.

Related errors

• Could not find total or inconclusive test count in test resu
• No test result files found. All test processes may have cras
• At least {failed} test(s) failed in {System.IO.Path.GetFileN
• Unexpected platform (expected: android) in device: {deviceDe
• Unexpected device type (expected: device|emulator) in device

AI-assisted analysis of dotnet/maui@f377ff1c5e (2026-08-13). Data as JSON: /api/errors/469e8b110c23adba. Report an issue: GitHub.