Comments (3)
Do you mean that we would use an option in order to specify one format or the other, in order to be retro-compatible?
Yes.
I would say that we break the API (and old projects using the old versions of
test-runner
) and release a new major version oftest-runner
. I don't really see the point of having such an option (unless for retro-compatibility). This option will be drag forever without real meaning, isn't it?My point of view is that have the
testClassName#testMethodName
is richer than only the simple test method names and thus it would be better for all the users. One day, we must take the step and I think it is better to do it ASAP.WDYT?
If you think it is worth it, then I follow you. I definitely agree that it is a richer output.
I'll prepare a PR for this issue and the new major release.
from test-runner.
The main issue I see is that the output will be different to what is expected because of the changes in the names of test methods. Maybe if we introduce an option, where the default would be simple name?
from test-runner.
Do you mean that we would use an option in order to specify one format or the other, in order to be retro-compatible?
I would say that we break the API (and old projects using the old versions of test-runner
) and release a new major version of test-runner
. I don't really see the point of having such an option (unless for retro-compatibility). This option will be drag forever without real meaning, isn't it?
My point of view is that have the testClassName#testMethodName
is richer than only the simple test method names and thus it would be better for all the users. One day, we must take the step and I think it is better to do it ASAP.
WDYT?
from test-runner.
Related Issues (20)
- Support multiple classes directories HOT 3
- Bump jacoco to 0.8.7 HOT 1
- Specify test classes and methods to run via a file HOT 1
- Optimize memory usage HOT 3
- Optimize coverage analysis HOT 3
- [BUG]: Cannot run concurrency test
- [CI] sonatype lift HOT 1
- [BUG] cannot use test-runner with JUnit < 4.12
- add support for testng
- Lower log level of EntryPoint
- Maven Surefire not properly loaded HOT 10
- Improve isolated process error handling
- set up continuous delivery in Github Actions HOT 11
- Refactor: redirection of IO in EntryPoint
- Refactor: something is wrong with the following condition
- Bump JaCoCo to 0.8.8
- Use optimized analyzer in detailed compressed coverage
- [FEAT] can pass arguments to the internal JVM with a file
- Option for including class constructors in the coverage results
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from test-runner.