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
It sure would be nice to have things like error logs, differences in test output, etc., right in our UI. I think CircleCI should be able to do this. Their documentation on Collecting Test Metadata gives a high-level overview, but their reliance on the JUnit format (which is documented only in a few ancient XSD files floating around the web) means we'll need to use other implementations as inspiration.
Fortunately, CircleCI themselves forkedassumed maintainership of minitest, so we can look at precisely how they generate test metadata after a run.
The RSpec JUnit formatter's xml_dump method could be another good place to look.
Basically, look at what they do and do something similar for the properties we care about in our tests.
The text was updated successfully, but these errors were encountered:
It sure would be nice to have things like error logs, differences in test output, etc., right in our UI. I think CircleCI should be able to do this. Their documentation on Collecting Test Metadata gives a high-level overview, but their reliance on the JUnit format (which is documented only in a few ancient XSD files floating around the web) means we'll need to use other implementations as inspiration.
Fortunately, CircleCI themselves
forkedassumed maintainership ofminitest
, so we can look at precisely how they generate test metadata after a run.The RSpec JUnit formatter's
xml_dump
method could be another good place to look.Basically, look at what they do and do something similar for the properties we care about in our tests.
The text was updated successfully, but these errors were encountered: