jest test failed in fixture is marked as skipped

[tematef]

Description Failed in preconditions jest test is marked as skipped within allure report

To Reproduce Steps to reproduce the behavior:

1. clone project from https://github.com/tematef/fixture-bug
2. npm install
3. jest
4. allure generate
5. observe report

Expected behavior Test should be marked as broken (yellow color), since it has broken step within it's lifecycle. It is confusing that broken test is shown the same as tests disabled by technical reasons or disabled due to specific environment conditions

console log

` FAIL test/bug.test.ts ✕ new test (1 ms)

● new test

ERROR

  1 |
  2 | beforeAll(async () => {
> 3 |     throw new Error("ERROR");
    |           ^
  4 | });
  5 | test(`new test`, async () => {
  6 |

  at Object.<anonymous> (test/bug.test.ts:3:11)

Test Suites: 1 failed, 1 total Tests: 1 failed, 1 total Snapshots: 0 total Time: 0.268 s, estimated 1 s Ran all test suites. ` Screenshot

[ma-nk]

Looks like a bug in the reporter

[AlexsandroZapani]

The same happens to me when the test breaks, I'm using Cypress, I updated to 3.1.0, but the situation persists.

[clergyman]

Hello @tematef , thank you for the report! I confirm that this is a registered known issue, so will close as duplicate. Please feel free to follow and participate in the original issue.