Add JUnit tests to releaseNote

[aliakhlaghi93]

Hello,
I am trying to add my JUnit test to the release note. Tests are published via Publish Test Result Task. releaseTest object is empty in that case. Do you know how it is possible that I include them in the object?
Or is there any way that I can define a new custom object?

Regards,
Ali

[rfennell]

As long as you have published your JUnit test results to the Azure DevOps pipeline they should appear.

The first check is to confirm your test results appear in the Azure DevOps pipeline run test results tabs. If they are not there, my task cannot report on them, as all I do is programmatically access the data that populates that tab.

Also, check the detailed pipeline log to make sure of what is actually being published

To my knowledge, there is no reason JUnit test should not be listed.

[rfennell]

I would expect the block in the Handlebars template for my Release Note Tasks to be similar to the following

# Global list of test ({{tests.length}})
{{#forEach tests}}
{{#if isFirst}}### Tests {{/if}}
* ** ID{{this.id}}** 
   -  Name: {{this.testCase.name}}
   -  Outcome: {{this.outcome}}
{{/forEach}}

You can of course dump all the available data using the following to get an idea of all the fields available

{{ json tests}}

[aliakhlaghi93]

Yeah, My tests object contains tests that are executed in build. However, releaseTest is empty while I can see the result in the test tab of the release stage. My main question is how do you get the releaseTest object in the backend? So I can investigate why it becomes empty at the end.

[rfennell]

The code to get the release tests (and remember these are only added in Classic Releases, not Muti-Stage YAML Pipelines where the test results are in the global tests) is in ReleaseNoteFunctions.ts

export async function getTestsForRelease(
    testAPI: TestApi,
    teamProject: string,
    release: Release
): Promise<TestCaseResult[]> {
    return new Promise<TestCaseResult[]>(async (resolve, reject) => {
        let testList: TestCaseResult[] = [];
        try {
            for (let envIndex = 0; envIndex < release.environments.length; envIndex++) {
                const env = release.environments[envIndex];
                    let envTestResults = await (testAPI.getTestResultDetailsForRelease(teamProject, release.id, env.id));
                    if (envTestResults.resultsForGroup.length > 0) {
                        for (let index = 0; index < envTestResults.resultsForGroup[0].results.length; index++) {
                            const test =  envTestResults.resultsForGroup[0].results[index];
                            if (testList.filter(e => e.testRun.id === `${test.testRun.id}`).length === 0) {
                                tl.debug(`Adding tests for test run ${test.testRun.id}`);
                                let run = await (testAPI.getTestResults(teamProject, parseInt(test.testRun.id)));
                                testList.push(...run);
                            } else {
                                tl.debug(`Skipping adding tests for test run ${test.testRun.id} as already added`);
                            }
                        }
                    } else {
                        tl.debug(`No tests associated with release ${release.id} environment ${env.name}`);
                    }
            }
            resolve(testList);
        } catch (err) {
            reject(err);
        }
    });
}

So the call is to getTestResults(<project>,<testtrun>)

[aliakhlaghi93]

Haha, I found my mistake. An "s" should be added to the documentation.

[rfennell]

Thanks for pointing that out. I have updated the WIKI with the correction and the next release of the extension will have an updated readme (and hence marketplace entry)