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
In the provided script, I encountered an issue where the Allure report does not display the description or other Allure features correctly when using test.concurrent. However, the description works fine when using test() without concurrent.
describe('Sleep Duration Test',()=>{test.concurrent.for([2,3,4])('1-1 Should sleep for %i second(s).',async(n,ctx)=>{awaitallure.description(`This is allure description - ${ctx.task.name}`)awaitsleep(n)expect(n).toBeLessThan(10)logWithTimestamp(`This is ${ctx.task.name}-${n}`)logWithTimestamp(`Slept for ${n} second(s)`)})test.for([2,3,4])('1-2 Should sleep for %i second(s).',async(n,ctx)=>{awaitallure.description(`This is allure description - ${ctx.task.name}`)awaitsleep(n)expect(n).toBeLessThan(10)logWithTimestamp(`This is ${ctx.task.name}-${n}`)logWithTimestamp(`Slept for ${n} second(s)`)})})
Could this be related to how Allure integrates with concurrent tests, or is there something specific that needs to be configured for it to work with test.concurrent?
Describe the bug
In the provided script, I encountered an issue where the Allure report does not display the description or other Allure features correctly when using test.concurrent. However, the description works fine when using test() without concurrent.
Could this be related to how Allure integrates with concurrent tests, or is there something specific that needs to be configured for it to work with test.concurrent?
To Reproduce
Steps to reproduce the behavior:
e2e
folder.Expected behavior
Description sections should display in every tests.
Screenshots
The results of tests wrapped in test.concurrent()
The results of tests wrapped in test()
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: