Allowing long form parsed output

[rareitems]

Hi
The adapters I worked with (jest and rust ones) show the whole output of the test in the output field which is the place to look for if you want to checkout any debug print statements or anything like that, the problem is, that output is extremely busy and quite unreadable.
Example of what Rust outputs in a simple test with a debug statement

    Building [                             ] 0/3: rust_code, rust_code(test)                                                                                                                                                               
    Building [==================>          ] 2/3: rust_code(test)                                                                                                                                                                          
    Building [==================>          ] 2/3: rust_code(test)                                                                                                                                                                          
    Finished test [unoptimized + debuginfo] target(s) in 0.29s
             [ 00:00:00] [                                                                                                                                                                                                                 
    Starting 1 tests across 1 binaries
             [ 00:00:00] [                                                                                                                                                                                                                 
             [ 00:00:00] [                                                                                                                                                                                                                 
     Running [ 00:00:00] [                                                                                                                                                                                                                 
     Running [ 00:00:00] [                                                                                                                                                                                                ] 0/1: 1 running,
     Running [ 00:00:00] [                                                                                                                                                                                                ] 0/1: 1 running,
        FAIL [   0.001s] rust_code tests::it_works

--- STDOUT:              rust_code tests::it_works ---

running 1 test
test tests::it_works ... FAILED

failures:

failures:
    tests::it_works

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s


--- STDERR:              rust_code tests::it_works ---
print debug statement
thread 'tests::it_works' panicked at 'assertion failed: `(left == right)`
  left: `4`,
 right: `0`', src/lib.rs:13:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

     Running [ 00:00:00] [                                                                                                                                                                                                ] 0/1: 1 running,
     Running [ 00:00:00] [                                                                                                                                                                                                ] 0/1: 1 running,
     Running [ 00:00:00] [                                                                                                                                                                                      ] 0/1: 0 running, 0 passed,
     Running [ 00:00:00] [                                                                                                                                                                                      ] 0/1: 0 running, 0 passed,
------------
     Summary [   0.001s] 1 tests run: 0 passed, 1 failed, 0 skipped
        FAIL [   0.001s] rust_code tests::it_works
     Running [ 00:00:00] [======================================================================================================================================================================================] 1/1: 0 running, 0 passed,
error: test run failed

What do you think about adding long, similar to short, field to the result table through which adapter could show the interesting things the tests outputs (stdout, stderr, what failed etc.) without other useless information that tester might add?
Cheers

[rcarriga]

I'm not opposed to the idea though I'd like to think on the best approach. Instinctively I don't like adding another field as it seems like maybe there could be more subsets of output to show with a result? On the other hand, just short and long would probably be the simplest approach for users to use. Of course open to ideas too!

[rareitems]

Maybe just outputs subtable for result, so adapters can attach what they want and specify users what to pass to show those results?
With short and long being a reserved and having some specification what to show so they work the more or less the same across all adapters.
Tho I guess swapping position of short would be a breaking change for adapters.

[rcarriga]

Yep I don't want to introduce a breaking change for this relatively niche feature. I also don't know if the adapters will be able to do what you're looking for right now. They're both relatively simple in how they collect output (i.e. they don't integrate tightly with the test runner), so I don't know if they could distinguish between output streams.

@haydenmeade @rouge8 Could I ask you both if neotest core allowed adding more output types, would your adapters be able to do the type of filtering as described above?

[haydenmeade]

It's most likely possible, happy to give it a shot as I am often annoyed by the same test output