Skip to content
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

[CT-2922] Produce unit testing artifacts for metadata about unit testing #8295

Closed
Tracked by #8283
gshank opened this issue Aug 2, 2023 · 1 comment · Fixed by #8477
Closed
Tracked by #8283

[CT-2922] Produce unit testing artifacts for metadata about unit testing #8295

gshank opened this issue Aug 2, 2023 · 1 comment · Fixed by #8477
Assignees

Comments

@gshank
Copy link
Contributor

gshank commented Aug 2, 2023

Description

We should produce json artifacts which can be ingested and used as metadata about unit testing. There will be at least two types of artifacts, including a "result" artifact and a more manifest-like artifact.

The output in the run_result should organize test output by the unique_id of the model that they're running on, should include test result output, and a lightweight unit test structure.

Developing these artifacts will require settling on a "node-like" representation of unit tests, which will resemble the unparsed yaml objects, but have some additional data, but will not include everything in the UnitTestNode object.

Acceptance criteria

We should have a run result structure and an artifact structure that we can share with other teams for feedback.

@github-actions github-actions bot changed the title Produce unit testing artifacts for metadata about unit testing [CT-2922] Produce unit testing artifacts for metadata about unit testing Aug 2, 2023
@gshank
Copy link
Contributor Author

gshank commented Aug 31, 2023

Merged into unit testing feature branch with #8477

@gshank gshank closed this as completed Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant