fix: add better failover case for duration not being found

[BobGneu]

This past week I have been on a tirade of skipping test cases, and I found that there was a case where if a suite is skipped the duration could be undefined, given there is either no value or no result for it.

I have included the failover of reporting the file, which I am on the fence about, but more importantly, both paths through the method to retrieve the duration return a duration.

Happy to discuss or update further!

[AriPerkkio]

This seems correct. 👍
Duration is a mandatory field based on SonarQube documentation.

Inside a file element, insert a testCase for each test run by unit tests. It can have the following attributes/children:

• testCase (mandatory)

  • duration (mandatory): long value in milliseconds

[AriPerkkio]

Thanks @BobGneu!

[AriPerkkio]

This is now released in version 0.3.1.

[BobGneu]

I went to update the snapshots and wanted to note, running the tests requires yarn, which could be replaced with the following with no other impact on the suite, beyond the absolute paths being present.

    try {
        execSync('npx vitest --config test/vite.test-config.ts', {
            stdio: 'inherit',
        });
    } catch (_) {
        // Ignore exit codes
    }

Could lead to better engagement with the community as vitest continues to gain a foothold.
Either way, thank you for the plugin, and your contributions to the community =)

[AriPerkkio]

Good catch! I definitely want to improve the contribution experience and lower the requirements.

It seems that we can even reference vitest binary directly, since these tests are run by using package.json's scripts. The node_modules/.bin binaries are available in the session.
This will be resolved in #18.