question-mark
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.

--verbose option not taken into account for test commands

See original GitHub issue

Current Behavior

using the nx console or by manually using the cli, passing --verbose flag to a test command like nx run lib:test --verbose or nx run lib:test -- --verbose.

running jest --verbose in the lib/app I want to test does correctly apply the flag’s functionality.

Expected Behavior

I expect the expected behavior of this flag to be active: “Display individual test results with the test suite hierarchy.”

Steps to Reproduce

run a test command using the verbose flag using the nx console or the nx cli

Failure Logs

Environment

nx report                                                            

>  NX  Report complete - copy this into the issue template

  nx : Not Found
  @nrwl/angular : Not Found
  @nrwl/cli : 10.2.1
  @nrwl/cypress : 10.2.1
  @nrwl/eslint-plugin-nx : 10.2.1
  @nrwl/express : Not Found
  @nrwl/jest : 10.2.1
  @nrwl/linter : 10.2.1
  @nrwl/nest : Not Found
  @nrwl/next : Not Found
  @nrwl/node : Not Found
  @nrwl/react : 10.2.1
  @nrwl/schematics : Not Found
  @nrwl/tao : 10.2.1
  @nrwl/web : 10.2.1
  @nrwl/workspace : 10.2.1
  typescript : 3.9.7

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:7
  • Comments:13

github_iconTop GitHub Comments

3reactions
bopmcommented, May 19, 2021

And yet, it’s not working even now. I have a project upgraded to ng 12, which is no longer build after that being stuck in Generating browser application bundles (phase: building) and verbose doing nothing for the build.

cc @vsavkin

2reactions
alexhadcommented, Sep 20, 2022

running the test with nx run my-app:test --verbose works!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Command testing verbose output, can not pass option -v
Instead: $commandTester->execute([ 'command' => $command->getName(), '--verbose' => true ]);. It is necessary to use:
Read more >
Setting verbose option for at(1) and batch(1) commands
zshenv is indeed correctly executed and that when launching [[ -o SHIN_STDIN ]] && !test -t 0 && echo OK with batch I...
Read more >
Use PowerShell to Write Verbose Output - Scripting Blog
Easier way to verbose output​​ The point of the earlier command is to show you how the preference variables effect the way Write-Verbose...
Read more >
Troubleshooting Guide for Java SE 6 with HotSpot VM - Oracle
This section describes some command line options that can be useful in diagnosing problems. B.1 HotSpot VM Command-Line Options. Command-line options that are ......
Read more >
Options Summary (GNU make) - GNU.org
The -d option is equivalent to ' --debug=a ' (see below). ... it is older than its prerequisites, and do not remake anything...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found