Skip to content

"Previous failure in test files that were not rerun" persists even though the failing test file was rerunΒ #2069

Closed
@IgnusG

Description

@IgnusG

Issuehunt badges

Description

The output of the watch mode is very confusing and more often than not unhelpful. I usually have to rerun the whole command since I'm never sure if the tests passed or not.

I was getting 2 failed tests. So I went ahead and fixed one but the other error was showing only a previously failed so I quit the command and rerun it since I didn't want to scroll to when it first failed (I think this could also be improved).

I got the error and fixed it, after which the output was a weird number of passed tests and 1 previous failure that was not rerun (even though there wasn't else failing to my knowledge).
DeepinScreenshot_select-area_20190315120700

I rerun the whole command again and finally got the correct number of passing tests with no failures.
DeepinScreenshot_select-area_20190315121039

I'm not sure if this is intended or if I'm just thinking about the numbers incorrectly.

Config

Copy the relevant section from package.json:

{
  "ava": {
     "require": [
         "esm",
         "./setup-test-env.js"
     ]
  }
}

setup-test-env.js

import browserEnv from 'browser-env';
browserEnv(['window', 'document']);

Environment

Node.js v10.5.0
linux 4.20.13-arch1-1-ARCH
ava 1.3.1


IssueHunt Summary

Sponsors (Total: $40.00)

Become a sponsor now!

Or submit a pull request to get the deposits!

Tips

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions