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

Does Nunit ITestEventListener support async handler for OnTestEvent #1397

Open
puagarwa opened this issue Mar 31, 2024 · 1 comment
Open
Labels

Comments

@puagarwa
Copy link

I am writing a custom reporter by writing a Nunit extension via ITestEventListener as mentioned in the Nunit document here.

I have some requirement where i would like to implement OnTestEvent as async handler. I didnt find any document around it, hence checking if Nunit support async handler for it.

Another minor question is around console out, i observe console out lines from extension are not showing up in console, for now i am getting around this by writing into a file but i like to see if there is way to flow logs at console form extension.

@OsirisTerje
Copy link
Member

OsirisTerje commented Apr 5, 2024

  1. There is no async support there. Could be something for the future, but it would be a long shot, as we're currently out of resources.
  2. Console: Never tried that, but the engine in itself doesn't have any console to write to (as NUnit traps the output) If you look at the resultwriter, there is code showing the console reportwriter. That might give you some ideas. But it will depend on how you're running the engine, NUnit.console or adapter, and how they capture the stdout. Also, have a look at this doc: https://docs.nunit.org/articles/nunit/technical-notes/nunit-internals/specs/Internal-Trace-Spec.html

Btw. moving this to the console/engine repo, since this is a question related to the engine.

@OsirisTerje OsirisTerje transferred this issue from nunit/nunit Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants