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

Make Report permanent snapshot #525

Open
sebastian-echeverria opened this issue Nov 15, 2024 · 0 comments
Open

Make Report permanent snapshot #525

sebastian-echeverria opened this issue Nov 15, 2024 · 0 comments
Labels
test-library Issues related to the main functionality of MLTE as a test library

Comments

@sebastian-echeverria
Copy link
Collaborator

We want the Report to be a snapshot of a test run in time. It should not change if other artifact changes. Currently it depends on ValidatedSpec/TestResults, which in turn depends on Spec/TestSpec. If those change, the current Report data will change accordingly, which would violate having it being a snapshot.

Modify Report so that:

  • It contains a standalone or permanent version of the content of NegotiationCard, TestSpec and TestResults. One way of doing this is by having the Report contain a copy of all the data in each of those artifacts. However, since Add versioning support to NegotiationCards and TestSpec #520 will be adding versioning support to NegotiationCards and TestSpecs, that means that each iteration of a NegotiationCard and TestSpec will never be lost/changed, as each change will create a new version. If this is so, it may be enough for the Report to link to the specific version of the NegotiationCard and TestSpec that was the current one when it was created/results where run. However, for TestResults, they will not be versioned since they are just intermediate results, so they will have to somehow be copied/maintained for the Report.
  • A sort of versioning will be needed for Reports, by timestamp. Each time a new Report is created, it will have to be stored and clearly identified by its timestamp. However, it may be possible to modify specific fields in it (TBD).
@sebastian-echeverria sebastian-echeverria added the test-library Issues related to the main functionality of MLTE as a test library label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test-library Issues related to the main functionality of MLTE as a test library
Projects
None yet
Development

No branches or pull requests

1 participant