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
{{ message }}
This repository has been archived by the owner on Jan 18, 2025. It is now read-only.
Apologies if this has been asked, but I was wondering if there was a way to report the status of tests via a notification?
If I'm developing in a TDD style, I usually have some flavor of cargo watch -x test running in the background.
It would be great if there was a way to report red (tests failing) or green (test passing) through the desktop notifications.
It seems like the plumbing is there, since --notify pops up a notification every time there's a change, maybe just a way to react to the exit status? i.e. 0=green, >0=red?
The text was updated successfully, but these errors were encountered:
Stuff in -s is executed after the process ends and (IIUC) only when cargo exits with success. I assume that with a bit of scripting you should be able to wrap cargo-watch and write your own custom reporting notification that also handles the case where the command exited with an error code (f.e. one test failed)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apologies if this has been asked, but I was wondering if there was a way to report the status of tests via a notification?
If I'm developing in a TDD style, I usually have some flavor of
cargo watch -x test
running in the background.It would be great if there was a way to report red (tests failing) or green (test passing) through the desktop notifications.
It seems like the plumbing is there, since
--notify
pops up a notification every time there's a change, maybe just a way to react to the exit status? i.e. 0=green, >0=red?The text was updated successfully, but these errors were encountered: