You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to supply a custom test reporter when running a suite of tests via run-tests? I'd like to be able to generate my own output for each test as certain build pipelines require specific output be wrote to stdout in order to enable various UI features.
Reading the source I found that run-tests! simply binds greenlight.test/report to a function that's called after each test, which sounded perfect but unfortunately it isn't possible to bind this from outside, it is possible when running a singular test with run-test! however.
So it seems my only option as it stands is to discover tests using find-tests and run each test individually, of course this means I unfortunately lose some information with regards to how many tests have passed/failed unless I keep track of that myself which I'd rather avoid.
Is there perhaps something I'm missing?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi all,
Is it possible to supply a custom test reporter when running a suite of tests via run-tests? I'd like to be able to generate my own output for each test as certain build pipelines require specific output be wrote to stdout in order to enable various UI features.
Reading the source I found that run-tests! simply binds greenlight.test/report to a function that's called after each test, which sounded perfect but unfortunately it isn't possible to bind this from outside, it is possible when running a singular test with run-test! however.
So it seems my only option as it stands is to discover tests using find-tests and run each test individually, of course this means I unfortunately lose some information with regards to how many tests have passed/failed unless I keep track of that myself which I'd rather avoid.
Is there perhaps something I'm missing?
Thanks.
The text was updated successfully, but these errors were encountered: