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.

Sign up for GitHub

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

Jump to bottom

Create a compatibility junit runner #16

Closed
GoogleCodeExporter opened this issue Nov 18, 2015 · 2 comments
Closed

Create a compatibility junit runner #16

GoogleCodeExporter opened this issue Nov 18, 2015 · 2 comments
Labels
auto-migrated Milestone-Future Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

We should create a "compatibility" runner for JUnit 4 and perhaps JUnit 3.
This means a Junit runner without any chunking. The chunking is tightly
coupled to internal Junit4 functionality and for custom versions of JUnit
our chunking mechanism will fail (for example in the Eclipse JUnit
version). Using a compatibility runner it would be possible to launch
PowerMock (without chunking support) with custom JUnit versions.

Original issue reported on code.google.com by johan.ha...@gmail.com on 23 Sep 2008 at 11:05
@GoogleCodeExporter
Copy link
Author

Original comment by johan.ha...@gmail.com on 23 Sep 2008 at 11:05

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author 

Probably not needed, the eclipse version of unit works with the PowerMock 
legacy runner.

Original comment by johan.ha...@gmail.com on 3 Nov 2008 at 1:15

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-Future Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter