Bug: verbose flag doesn't do anything?

[drmorr0]

Description of the issue

Description:
cargo nextest run -v doesn't produce any different output than cargo nextest run (as far as I can tell):

drmorr@acrl1 ~/src/json_patch_ext > cargo nextest run -v
    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s
────────────
 Nextest run ID c6128057-81a5-4201-9b90-919837562827 with nextest profile: default
    Starting 23 tests across 1 binary
        PASS [   0.010s] json-patch-ext tests::test_matches_4::case_2
        PASS [   0.010s] json-patch-ext tests::test_matches_3
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_2
        PASS [   0.011s] json-patch-ext tests::test_matches_4::case_1
        PASS [   0.009s] json-patch-ext tests::test_patch_ext_add_vec2
        PASS [   0.010s] json-patch-ext tests::test_matches_root
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_4
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_add
        PASS [   0.011s] json-patch-ext tests::test_no_match::case_1
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_3
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_add_escaped
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_5
        PASS [   0.012s] json-patch-ext tests::test_matches_1
        PASS [   0.012s] json-patch-ext tests::test_matches_2
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_add_vec_err
        PASS [   0.014s] json-patch-ext tests::test_patch_ext_add_vec1
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_replace
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_remove_vec_err
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_remove_vec
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_replace_vec1
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_replace_err
        PASS [   0.012s] json-patch-ext tests::test_patch_ext_remove
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_replace_vec2
────────────
     Summary [   0.024s] 23 tests run: 23 passed, 0 skipped

versus

drmorr@acrl1 ~/src/json_patch_ext > cargo nextest run
    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s
────────────
 Nextest run ID 002d1598-af1c-41f6-8201-41f55c28db33 with nextest profile: default
    Starting 23 tests across 1 binary
        PASS [   0.007s] json-patch-ext tests::test_matches_4::case_1
        PASS [   0.008s] json-patch-ext tests::test_matches_1
        PASS [   0.008s] json-patch-ext tests::test_matches_root
        PASS [   0.009s] json-patch-ext tests::test_matches_3
        PASS [   0.009s] json-patch-ext tests::test_matches_4::case_2
        PASS [   0.009s] json-patch-ext tests::test_matches_2
        PASS [   0.009s] json-patch-ext tests::test_no_match::case_3
        PASS [   0.009s] json-patch-ext tests::test_no_match::case_5
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_2
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_4
        PASS [   0.010s] json-patch-ext tests::test_no_match::case_1
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_add
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_add_vec1
        PASS [   0.011s] json-patch-ext tests::test_patch_ext_add_escaped
        PASS [   0.009s] json-patch-ext tests::test_patch_ext_remove_vec
        PASS [   0.010s] json-patch-ext tests::test_patch_ext_remove
        PASS [   0.008s] json-patch-ext tests::test_patch_ext_replace_err
        PASS [   0.008s] json-patch-ext tests::test_patch_ext_replace_vec1
        PASS [   0.009s] json-patch-ext tests::test_patch_ext_remove_vec_err
        PASS [   0.009s] json-patch-ext tests::test_patch_ext_replace
        PASS [   0.009s] json-patch-ext tests::test_patch_ext_replace_vec2
        PASS [   0.019s] json-patch-ext tests::test_patch_ext_add_vec2
        PASS [   0.019s] json-patch-ext tests::test_patch_ext_add_vec_err
────────────
     Summary [   0.021s] 23 tests run: 23 passed, 0 skipped

Expected outcome

I expected the "verbose" flag to do something different than without the verbose flag.

Actual result

The results appear to be identical?

Nextest version

drmorr@acrl1 ~/src/json_patch_ext > cargo nextest --version
cargo-nextest 0.9.102 (c0f0b7051 2025-08-03)
release: 0.9.102
commit-hash: c0f0b7051e5e9af6f490659b186ca28af5494032
commit-date: 2025-08-03
host: x86_64-unknown-linux-gnu

Additional context

I was hoping to have nextest print out the name of the test binary so that I can run it under a debugger.

[sunshowers]

Yeah, printing out the command line makes sense under --verbose. Happy to accept a PR for this.