You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skipped tests are shown in the report with allureClearSkippedTests=true.
I also use custom defineHistoryId() function.
I see root cause in writer/results.js#writeTests function. allureMapping I see is an object where values are arrays, not a simple object.
Therefore mochaID will always be undefined: const mochaID = Object.keys(allureMapping).find( (id) => allureMapping[id].allureId === test.uuid );
Not sure why there is an array, but such case can be covered as well: const mochaID = Object.keys(allureMapping).find( (id) => { if (Array.isArray(allureMapping[id])) { return allureMapping[id].find(e => e.allureId === test.uuid); } return allureMapping[id].allureId === test.uuid; } );
The text was updated successfully, but these errors were encountered:
It was changed when retries handling was added, so this is basically an array of attempts. And you are correct that if mochaID is undefined, we do not remove it from mapping when allureClearSkippedTests is specified, so skipped tests are not ignored.
Skipped tests are shown in the report with allureClearSkippedTests=true.
I also use custom defineHistoryId() function.
I see root cause in writer/results.js#writeTests function. allureMapping I see is an object where values are arrays, not a simple object.
Therefore mochaID will always be undefined:
const mochaID = Object.keys(allureMapping).find( (id) => allureMapping[id].allureId === test.uuid );
Not sure why there is an array, but such case can be covered as well:
const mochaID = Object.keys(allureMapping).find(
(id) => {
if (Array.isArray(allureMapping[id])) {
return allureMapping[id].find(e => e.allureId === test.uuid);
}
return allureMapping[id].allureId === test.uuid;
}
);
The text was updated successfully, but these errors were encountered: