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

Align gradle plugin and runner features with Launcher API #312

Closed
6 tasks done
sbrannen opened this issue Jun 18, 2016 · 2 comments
Closed
6 tasks done

Align gradle plugin and runner features with Launcher API #312

sbrannen opened this issue Jun 18, 2016 · 2 comments

Comments

@sbrannen
Copy link
Member

sbrannen commented Jun 18, 2016

Status Quo

The JUnitPlatformPlugin (Gradle plugin), JUnitPlatform (JUnit 4 Runner), and ConsoleRunner currently have slightly different APIs and feature sets than what is supported by the Launcher APIs.3

Goals

For consistency and future proofing of these APIs we therefore need to align all public APIs for end users.

Specifically, actions related to DiscoverySelectors must be named "select" something. Similarly, filters must be named "include" or "exclude" something.

Related Issues

Deliverables

  • Rename @Packages to @SelectPackages
  • Rename @Classes to @SelectClasses
  • Rename byClassNamePattern() in ClassFilter to includeClassNamePattern()
  • Rename @FilterClassName to @IncludeClassNamePattern
  • Rename matchClassName in Gradle plugin to includeClassNamePattern
  • Rename --filter-classname option in ConsoleRunner to --include-classname
@sbrannen
Copy link
Member Author

in progress

sbrannen added a commit that referenced this issue Jun 18, 2016
sbrannen added a commit that referenced this issue Jun 18, 2016
sbrannen added a commit that referenced this issue Jun 18, 2016
- byClassNamePattern() in ClassFilter --> includeClassNamePattern()
- @FilterClassName --> @IncludeClassNamePattern
- matchClassName in Gradle plugin --> includeClassNamePattern
- --filter-classname option in ConsoleRunner --> --include-classname

Issue: #312
@sbrannen
Copy link
Member Author

sbrannen commented Jun 18, 2016

All deliverables have been pushed to master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant