Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should provide test env in verbose test report

See original GitHub issue

Update: Repurposed bug to feature

🚀 Feature Proposal

Display testEnvironment value in test output report on a per test file basis.

Motivation

To clearly see what env is used for each test file.

Example

 PASS  foo.test.js (6.252s) (jest-environment-jsdom)
  ✓ should be true
 PASS  bar.test.js (3.122s) (jest-environment-node)
  ✓ should be true

Pitch

It can sometimes be important to see test env used to run your tests. For example, if you have tests for code which run on both node & browser. Having at least the report of what env was used for which test - is valuable from a maintenance perspective.

Notes

Should this be on by default, or only when verbose: true?

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:19 (11 by maintainers)

Top GitHub Comments

1reaction

rickhanloniicommented, Dec 24, 2018

Yes @SimenB that’s what I meant, the reporter would strip jest-environment

I feel strongly that we should only print the env in the default reporter if there are multiple detected

If that’s too difficult to achieve then I’d recommend providing the info to reporters and using a custom reporter to display it always

0reactions

github-actions[bot]commented, Apr 30, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.