Making the Standard Output customizable!

[Dubai-Takodachi]

With Reqnroll 3.0.0 the new feature of generating report HTMLs is great! But sometimes I would just like to have a quick look at the standard output to know whats up.

A coloured output is already implemented. Which is great but my main problem is that its too much output.
Normally the output goes like this:
When The User Logs In
-> done: Classname.Method() (time)

This itself is okay. When the methods and Steps are short.
Once you describe a more complex step with multiple actors its gets very long. My current record is 108 characters.

Ideas:

Have a setting somewhere where you can define your customizations:

1. Show Method and Class names
2. Show Time
3. Show Scenario (which is not in the Standard output)

[gasparnagy]

These messages are provided by the ITestTracer (see here) implementations. You can make a custom one and register it using a runtime plugin.
The simplest runtime plugin registation could be like how the example shows for IBuildMetadataProvider here: https://docs.reqnroll.net/latest/extend/build-metadata-provider.html#step-3-create-the-runtime-plugin, except that in your case you should register it to the test thread container, so you need to use the CustomizeTestThreadDependencies event.
You can take a look at the default implementation, to get inspiration: https://github.com/reqnroll/Reqnroll/blob/main/Reqnroll/Tracing/TestTracer.cs#L28

Although this is possible and easy to do, you have to be aware that this interface is not directly dedicated for customizations. That means that we might change the interface even within major version numbers. But such changes are rare.

[Dubai-Takodachi]

Hi! This solves both the "Time" and the "Method and Class names" issue. But i still cant really display my Scenario., with the Interface implementation. My current Workaround is using the IReqnrollOutputHelper and using a beforeScenario hook. Otherwise this implementation is what I needed! Thanks for the Quick answer!

There might be other implementation aswell, e.g testing if the TraceStep Method has a new Scenario Definition. But thats more on the hacky side.