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

JUnitReport generation #1827

Closed
jan-goral opened this issue Apr 22, 2021 · 0 comments · Fixed by #1908
Closed

JUnitReport generation #1827

jan-goral opened this issue Apr 22, 2021 · 0 comments · Fixed by #1908
Assignees

Comments

@jan-goral
Copy link
Contributor

jan-goral commented Apr 22, 2021

Description

Basing output structures which are representing parsed output from am instrument -r -w
Prepare function for generating JUnitReport.

Requirement

The implementation should allow generating one JUnitReport from many test results.

API

Input

List of logs from many executions

List<List<Instrument>>

reference - https://github.com/Flank/flank/blob/9775e46f920329640e58dfae821fbe2958643150/corellium/log/src/main/kotlin/flank/corellium/log/Parser.kt

Output

JUnitTest.Result

reference - Reuse structure described in #1757

@jan-goral jan-goral changed the title Generate JUnitReport (Corellium) JUnitReport generation Apr 22, 2021
@jan-goral jan-goral self-assigned this May 10, 2021
@jan-goral jan-goral mentioned this issue May 10, 2021
2 tasks
@mergify mergify bot closed this as completed in #1908 May 12, 2021
mergify bot pushed a commit that referenced this issue May 12, 2021
Fixes #1827 

* The JUnit structures are bases on those taken from the `test_runner` but applying some fixes like reducing the number of nullable fields.
* The `JUnit.xsd` is added just for convenience as a referential scheme.

## Test Plan
> How do we know the code works?

Unit tests pass

## Checklist

- [x] Documented
- [x] Unit tested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant