Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verbose logging for the runner #436

Open
wiredsister opened this issue Jul 30, 2022 · 1 comment
Open

Verbose logging for the runner #436

wiredsister opened this issue Jul 30, 2022 · 1 comment

Comments

@wiredsister
Copy link

Problem:
I wanted to see my tests run even though they are successful. I wanted to see them sequentially.
This was surprisingly hard for me because I'm new to expecto. Running them sequentially was easy enough. It's the printing that I couldn't quite figure out at a glance.

For example, reading the docs I could not find an easy example of making it verbose. I ended up on a goose chase around this part of the documentation:

image

The namespace Logary.Adapter.Facade no longer exists and Logary has no write up on how it should be configured with Expecto. The latest 5.0 package pulls in for the Adapter via Nuget... I just think the docs are out of date.

Funny enough all I needed to do in my code was: runTestsWithCLIArgs [] [|"--debug"|] all

The only --debug flag I found when I Ctrl+F'ed in the README was xbuild Sample.fsproj && mono --debug bin/Debug/Sample.exe which scared me off because I'm using dotnet and wasn't sure if this was how I needed to be passing it.

Couple of thoughts:

  • Is there a way I can PR a more friendly version of getting your test cases to print for the docs
  • Is this the way you want people to be doing this

Thanks for your time and effort ❤️ The library itself was quite lovely.

@baronfel
Copy link
Contributor

I'd love to see the docs point to the withCLIArgs version of the runner functions by default - those are the most user friendly in my opinion because they allow users to customize behavior at runtime easily. What do the maintainers think of that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants