citusdata / citusdata/the-process

Improve test report details

Open
#9 0 comments 0 reactions 0 assignees View on GitHub
Area :robot: Need :alembic: Need :mag: State :construction: Type :muscle:
Dominant language
Dockerfile
Stars
6
Forks
7
Avg merge
4d 22h
Merged PRs (30d)
1

Description

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](https://circleci.com/docs/2.0/collect-test-data/) 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 ~~forked~~ _assumed maintainership_ of `minitest`, so we can look at precisely [how they generate test metadata](https://github.com/circleci/minitest-ci/blob/8b72b0f32f154d91b53d63d1d0a8a8fb3b01d726/lib/minitest/ci_plugin.rb#L131-L161) after a run.

The RSpec JUnit formatter's [`xml_dump` method](https://github.com/sj26/rspec_junit_formatter/blob/8f981d20979a9efa235cc878790b92d8862ba560/lib/rspec_junit_formatter.rb#L14-L182) 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.