-
Notifications
You must be signed in to change notification settings - Fork 320
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
TestLogger/DataCollector can't be used to log Test Case Start #4950
Comments
Hello, are you using some specific testing framework? Or this is a for a "service" and needs to take all testing frameworks into account? |
This is a for a service and needs to take all testing frameworks into account. |
I would also be interested in this, the use case being the attribution of received messages to the test cases that sent them via @davidmatson, when you say
are you referring to the |
Yes. I was originally thinking of how test framework adapters call RecordEnd but RecordResult is probably more accurate. |
This is a new feature and won't be implemented, we are focusing on adding new features to Testing.Platform instead. https://aka.ms/testingplatform |
Description
I'm trying to use VSTest extensibility to integrate with another logging system that needs to report as soon as a test case starts. ITestLogger allows me to log on TestCaseEnd, but it doesn't provide any indication when a test case starts. This functionality is important especially for long-running test cases.
I tried using DataCollector and InProcessDataCollection, but neither of those help either - neither receive other messages as a test is running, unlike ITestLogger. Even using all in combination, I still can't get all the events as they happen - InProcessDataCollection doesn't have a way to log messages out; DataCollector can only log warnings or errors, but even these aren't sent to the ITestLogger right away - the platform appears to buffer any logged messages after the first one, so sending a "test case start" message from a DataCollector to an ITestLogger also does not work.
This scenario might be possible by replacing vstest.console.exe entirely with my own code, but that's far more code than I'd like to own just to be notified of and log TestStart events.
This is a feature request to add a TestStart event to TestLoggerEvents.
The text was updated successfully, but these errors were encountered: