[allure-jest] Test start time is incorrect, which leads to incorrect test duration

[maks-rafalko]

Describe the bug

We are using v2.15.1 and this version incorrectly calculates tests' start time, which leads to incorrectly calculated Duration time on allure report UI.

The instance of AllureTest is created here on Jest's add_test event:

allure-js/packages/allure-jest/src/AllureJest.ts

Lines 95 to 98 in d426d79

	this.handleTestAdd({
	testName: event.testName,
	concurrent: event.concurrent,
	state,

Then, we set time to test.testResult.start:

allure-js/packages/allure-js-commons/src/current/AllureTest.ts

Line 21 in d426d79

this.testResult.start = start;

The root of the bug is that we should save start time on test_start event, not on add_test. Here:

allure-js/packages/allure-jest/src/AllureJest.ts

Lines 101 to 103 in d426d79

	case "test_start":
	this.handleTestStart(event.test);
	break;

add_test event occures for all the tests cases of the fille at the same time, so this is simply not a correct event to save start time of the test..

To Reproduce

1. Create a test file with N tests, let's say N=5
2. in each test() case, add for example sleep for 3 seconds
3. Result - duration of the test N1 will be 3 seconds, duration of the test N2 will be 6 seconds, of the test N3 9 seconds and so on

Expected behavior

1. Create a test file with N tests, let's say N=5
2. in each test() case, add for example sleep for 3 seconds
3. Result - duration of the test N1 will be 3 seconds, duration of the test N2 will be 3 seconds, of the test N3 3 seconds and so on

Screenshots

Before:

After adding a fix:

---

The fix is pretty simple, we just need to save test.testResult.start time somewere here on test_start event:

allure-js/packages/allure-jest/src/AllureJest.ts

Line 179 in d426d79

currentTest.stage = Stage.RUNNING;

If you agree, I can try to provide a PR.

[baev]

Could you please re-check the issue using the latest 3.0.0-beta.3 release? All the integrations were revisited (& reworked) recently, we're about to release 3.0.0. If the issue still occurs, we'll be happy to fix it