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

Introduce Display Name Generator SPI #1588

Merged
merged 3 commits into from
Sep 26, 2018

Conversation

sormuras
Copy link
Member

@sormuras sormuras commented Sep 16, 2018

Overview

Addresses #162


Definition of Done

@ghost ghost assigned sormuras Sep 16, 2018
@ghost ghost added the status: in progress label Sep 16, 2018
@sormuras sormuras force-pushed the issues/162-display-name-generator branch 3 times, most recently from f5687c6 to 43fe669 Compare September 16, 2018 17:31
Copy link
Member

@sbrannen sbrannen left a comment

Choose a reason for hiding this comment

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

I requested that unrelated changes be pushed to master.

Copy link
Member

@sbrannen sbrannen left a comment

Choose a reason for hiding this comment

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

I've submitted a separate review for the meat of this PR.

@sormuras sormuras changed the title [WIP] Introduce Display Name Generator extension [WIP] Introduce Display Name Generator SPI Sep 17, 2018
@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 7542436 to 91231ac Compare September 19, 2018 05:00
@codecov
Copy link

codecov bot commented Sep 19, 2018

Codecov Report

Merging #1588 into master will increase coverage by 0.05%.
The diff coverage is 98.07%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #1588      +/-   ##
============================================
+ Coverage     92.03%   92.09%   +0.05%     
- Complexity     3548     3561      +13     
============================================
  Files           323      325       +2     
  Lines          8474     8510      +36     
  Branches        737      742       +5     
============================================
+ Hits           7799     7837      +38     
  Misses          502      502              
+ Partials        173      171       -2
Impacted Files Coverage Δ Complexity Δ
...va/org/junit/jupiter/api/DisplayNameGenerator.java 100% <100%> (ø) 1 <1> (?)
...r/engine/descriptor/NestedClassTestDescriptor.java 100% <100%> (ø) 4 <1> (ø) ⬇️
...piter/engine/descriptor/JupiterTestDescriptor.java 86.44% <100%> (-1.06%) 23 <1> (-2)
...r/engine/descriptor/MethodBasedTestDescriptor.java 100% <100%> (ø) 9 <1> (-1) ⬇️
...jupiter/engine/descriptor/ClassTestDescriptor.java 96.79% <100%> (-0.09%) 62 <2> (-1)
...it/jupiter/engine/descriptor/DisplayNameUtils.java 96.96% <96.96%> (ø) 15 <15> (?)
...jupiter/engine/execution/ExtensionValuesStore.java 91.42% <0%> (+4.28%) 22% <0%> (+1%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e83bfd...ee139f7. Read the comment docs.

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 91231ac to aa0d3bb Compare September 19, 2018 06:07
@sbrannen
Copy link
Member

sbrannen commented Sep 19, 2018

@sormuras, what was the resolution of the jacoco vs. synthetic discussion?

#1588 (comment)

Copy link
Member

@sbrannen sbrannen left a comment

Choose a reason for hiding this comment

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

I've requested minor changes and posed a few questions as well.

@sormuras
Copy link
Member Author

what was the resolution for the jacoco vs. synthetic discussion?

Mh, my comment is buried somewhere or was lost before being posted. Anyway, the underlying issue were the default methods introduced in the DisplayNameGenerator interface. They triggered JaCoCo to introduce the new real method. This new method was not a bridge, and not synthetic.

As I removed the default methods from the inteface, the JaCoCo method vanished as well.

@sbrannen
Copy link
Member

As I removed the default methods from the inteface, the JaCoCo method vanished as well.

Aha. Interesting!

But that makes sense now.

Thanks for the explanation.

@sbrannen
Copy link
Member

In any case, those JaCoCo methods will return due to the default interface methods in the upcoming TestWatcher API (#1393 (comment)). 😉

@sormuras
Copy link
Member Author

sormuras commented Sep 19, 2018

Create an issue in advance? Have a solution shelved here...

@sbrannen
Copy link
Member

Create an issue in advance? Have a solution shelved here...

Sure, feel free.

But please let @geo-m know so that he's informed. 😉

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from aa0d3bb to 7aa3d61 Compare September 19, 2018 11:45
@sbrannen
Copy link
Member

sbrannen commented Sep 19, 2018

Open Issues: (not covered in a review)

  • Should @DisplayNameGeneration be @Inherited (in inheritance hierarchies)?
  • Should @DisplayNameGeneration be inherited (in @Nested hierarchies)?
  • What package(s) do we want the new annotation, interface, and implementations to reside in?

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 7aa3d61 to 1572ccc Compare September 19, 2018 14:11
Copy link
Member

@sbrannen sbrannen left a comment

Choose a reason for hiding this comment

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

I added another mini review.

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 8f18466 to 2799c3e Compare September 22, 2018 04:28
@sormuras
Copy link
Member Author

All comments addressed, starting with the documentation.

@sormuras sormuras changed the title [WIP] Introduce Display Name Generator SPI Introduce Display Name Generator SPI Sep 22, 2018
@sormuras
Copy link
Member Author

Removed the WIP prefix from the issue title. @sbrannen shall I merge to master and you polish the documentation there?

Copy link
Member

@sbrannen sbrannen left a comment

Choose a reason for hiding this comment

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

Minor change requested

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from ac4a355 to 2dc2965 Compare September 23, 2018 16:00
@sormuras
Copy link
Member Author

@marcphilipp anything else? If not, I'll continue with documentation.

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 2dc2965 to be2d0e6 Compare September 25, 2018 10:55
@andreybleme
Copy link

Hi @sbrannen and @sormuras, what's avoiding this change to be merged at master? Just asking because it blocks #1595, which I'll start working.

@sormuras
Copy link
Member Author

A final review by @marcphilipp tonight or ... soon. ;-)

Copy link
Member

@marcphilipp marcphilipp left a comment

Choose a reason for hiding this comment

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

Looking good! 👍 One added some minor comments. Please add an entry to the release notes as well.

@sormuras sormuras force-pushed the issues/162-display-name-generator branch from be2d0e6 to c75ae2c Compare September 25, 2018 19:28
Move pre-defined generators to DisplayNameGenerator interface.
@sormuras sormuras force-pushed the issues/162-display-name-generator branch from c75ae2c to 3ad6cf2 Compare September 26, 2018 04:19
@sormuras sormuras force-pushed the issues/162-display-name-generator branch from 3ad6cf2 to ee139f7 Compare September 26, 2018 07:30
@sormuras sormuras merged commit 4db8e8e into master Sep 26, 2018
@ghost ghost removed the status: in progress label Sep 26, 2018
@sormuras sormuras deleted the issues/162-display-name-generator branch September 26, 2018 08:05
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.

4 participants