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

730 - Refactor jUnit HTML report #731

Merged
merged 10 commits into from
Apr 30, 2020
Merged

Conversation

Writhe
Copy link
Contributor

@Writhe Writhe commented Apr 22, 2020

This PR is a refactor of /junit_html_report. It replaces CRA with plain TS and simplifies the shape of data expected from Kotlin app (hence the WIP status).

TO DO: DONE:

  • change the output from Kotlin app that gets injected into the resulting HTML, to the following shape:
IResult {
  label: string
  url: string
}

IResultGroup {
  label: string
  items: IResult[]
}
  • make it so it gets JSONified and injected into HTML, replacing "INJECT-DATA-HERE", preferably with quotes escaped.

},
function(err, result) {
if (err) { console.log(err); }
var kotlinResource = '../test_runner/src/main/resources/inline.html';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't find replacement for this line. @Writhe are you sure that new implementation will update inline.html in resources automatically? I guess we don't want to do copy paste manually after update.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good catch - it won't.
I don't think we need this file anywhere other than resources, so I can just tell Webpack to target that directory when building the thing. Would that be ok?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can just tell Webpack to target that directory when building the thing. Would that be ok?

Yes, that will work. We don't use inline.html anywhere else.

@jan-goral jan-goral added this to the May 2020 milestone Apr 22, 2020
@jan-goral jan-goral linked an issue Apr 22, 2020 that may be closed by this pull request
@jan-goral jan-goral marked this pull request as draft April 22, 2020 21:53
@jan-goral jan-goral force-pushed the 730-refactor-junit-html-report branch 2 times, most recently from f5c3ba5 to 721e9c2 Compare April 30, 2020 01:56
@jan-goral jan-goral marked this pull request as ready for review April 30, 2020 01:58
@jan-goral jan-goral requested a review from pawelpasterz April 30, 2020 01:58
@jan-goral jan-goral changed the title 730 - Refactor jUnit HTML report (WIP) 730 - Refactor jUnit HTML report Apr 30, 2020
pawelpasterz
pawelpasterz previously approved these changes Apr 30, 2020
@codecov-io
Copy link

Codecov Report

Merging #731 into master will increase coverage by 0.00%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #731   +/-   ##
=========================================
  Coverage     78.21%   78.22%           
+ Complexity      675      665   -10     
=========================================
  Files           125      125           
  Lines          2796     2774   -22     
  Branches        405      399    -6     
=========================================
- Hits           2187     2170   -17     
  Misses          350      350           
+ Partials        259      254    -5     

@jan-goral jan-goral merged commit 6188af2 into master Apr 30, 2020
@jan-goral jan-goral deleted the 730-refactor-junit-html-report branch April 30, 2020 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refactor junit_html_report
5 participants