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

roadmap chart #251

Closed
wants to merge 1 commit into from
Closed

roadmap chart #251

wants to merge 1 commit into from

Conversation

Tibor17
Copy link
Contributor

@Tibor17 Tibor17 commented Nov 3, 2019

No description provided.

@Tibor17
Copy link
Contributor Author

Tibor17 commented Nov 4, 2019

@jon-bell
@Col-E
You are welcome to participate as well.

@eolivelli
Copy link
Contributor

@Tibor17
is it really necessary to publish such roadmap?
We can have JIRAs and assign them to a version.

So we need to share it explicitly on dev@ list?

That said for me it is okay, I am just asking

@Tibor17
Copy link
Contributor Author

Tibor17 commented Nov 4, 2019

@Tibor17
is it really necessary to publish such roadmap?

Maybe it is important for contributors/devs because some people at the U.S. Universities found Surefire as an interesting project and they started similar activities by themselves that we have in this plan too. And it was a perfect match because we left their activity with Shell scripting and started contributing to Surefire because our plan really targets their research problem at the University.

So now the contributors can see if they fit, and if not then we can include them.

Our goal with @krosenvold @agudian is to put the extensions in Test List Processor and break backwards compatibility with system properties of config parameters (means added prefix: surefire. and failsafe.).
If you know these three things, as the Surefire internals (code and req extentions) and user req (like -Dtest=org.asf.MyTest over -Dtest=org/asf/MyTest.java) and the path of JUnit5, then you must see that our internal code and documentation should change (more inside and less outside) and this is possible only in major version.
With this plan we do not break anything till the end and we satisfy our internal req and users too.
Therefore this is on GH because the dvelopers can immediately see what changed in the history of road map and what code changed for the road map.
I do not see ML as a benefit in this special case because our contrinutors notice usually the most recent email in ML and not the diff.

We can have JIRAs and assign them to a version.

I want to have this work done in Jira of course but we need to find the time slot to do it.
Maybe you would help if you like to.

@Rajno1
Copy link

Rajno1 commented Mar 8, 2020

HI I am trying to a maven project through terminal (MAC), by using command 'mvn verify'.
BUILD SUCCESS message is coming but T E S T S are not running. please check and advice
following is my pom.xml file


4.0.0

nopCommerseV001_cucumber
nopCommerseV001_cucumber
0.0.1-SNAPSHOT
jar

nopCommerseV001_cucumber
http://maven.apache.org

UTF-8 1.6 1.6 org.apache.maven.plugins maven-compiler-plugin 3.8.1 io.cucumber cucumber-junit 5.4.2 test junit junit 4.13 test io.cucumber cucumber-java 5.0.0-RC1 io.cucumber cucumber-core 5.0.0-RC1 io.cucumber cucumber-jvm 5.0.0-RC1 pom net.masterthought cucumber-reporting 4.11.0 io.cucumber cucumber-jvm-deps 1.0.6 provided org.seleniumhq.selenium selenium-java 3.141.59 io.cucumber cucumber-testng 5.0.0-RC1 log4j log4j 1.2.17 org.apache.maven.plugins maven-surefire-plugin 3.0.0-M4

************** following is my terminal output ***************

[INFO] Scanning for projects...
[INFO]
[INFO] ---------< nopCommerseV001_cucumber:nopCommerseV001_cucumber >----------
[INFO] Building nopCommerseV001_cucumber 0.0.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ nopCommerseV001_cucumber ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /Users/rajasekhar/eclipse-workspace/nopCommerseV001_cucumber/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ nopCommerseV001_cucumber ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ nopCommerseV001_cucumber ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /Users/rajasekhar/eclipse-workspace/nopCommerseV001_cucumber/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ nopCommerseV001_cucumber ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ nopCommerseV001_cucumber ---
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ nopCommerseV001_cucumber ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.295 s
[INFO] Finished at: 2020-03-08T18:40:31+05:30
[INFO] ------------------------------------------------------------------------

@KroArtem
Copy link

@Tibor17 , as far as I see, surefire-3.0.0-M4 was released without TCP/IP interprocess communication. Are there any plans to release a new milestone version? (since tcp/ip is merged to master)

@Tibor17
Copy link
Contributor Author

Tibor17 commented Apr 20, 2020

@KroArtem
In M4 we reworked only the protocol and the OOP model regarding the facilities which are sending and receiving data.
In M5 we extended the physical layer and made the code abstract with extensions which are able to substitute the default implementation with user's impl.

We definitively have to shift the tasks 1 - 5 to M6. This makes 10 issues shifted.

Currently, we are fixing 4 bugs with a help of our contributors, and some anoying bugs (NPE, JUnit5, toolchain) which are very fast to fix:
https://issues.apache.org/jira/browse/SUREFIRE-1234
https://issues.apache.org/jira/browse/SUREFIRE-1570
https://issues.apache.org/jira/browse/SUREFIRE-1750
https://issues.apache.org/jira/browse/SUREFIRE-1759
We don't want to postpone the release since the most difficult task - TCP was done.
These are in a good progress but we are open if you guys help on GitHub.

@Tibor17
Copy link
Contributor Author

Tibor17 commented Apr 20, 2020

@Rajno1
Sorry for late reply.
It's hard to answer because we don't see your project. Every time the user found and issue, we asked him to provide a project which can reproduce the issue. Feel free to create an account in JIRA and post the issue with ZIP archive of your project.

@KroArtem
Copy link

@Tibor17 , first of all, thanks a lot for your enormous work. I don't want to say hey guys, work harder, just was trying to clarify the roadmap. After releasing M5 we can check it on our project. If there are some built-in ways to compare performance I can spend some time and try to provide feedback.

Regarding contributions, I'm afraid Surefire is very low-level for me

@Tibor17
Copy link
Contributor Author

Tibor17 commented Apr 21, 2020

@KroArtem
The performance was improved in M5. We expect faster JVM startup and much faster teardown (10 millis). In the tests you can find bad performance with the old version 3.0.0-M3. I would be glad if you could use the same test project and compare 3.0.0-SNAPSHOT. Additionally, we have improved flushing the internal stream in JVMs and this should improve the performance for projects producing big logs (more than 64 MB) by the executed tests. Of course there are two more possibilities to improve more in the logs but we don't have time to delay the release too much.

@somayaj
Copy link

somayaj commented Nov 3, 2021

qq- for the naming convention being used - ex: 3.0.0-M3 what is M there, milestone? or major? Curious when the release candidate will be available outside of these milestones if indeed the M is a milestone?

@ascheman
Copy link

Coming here due to the hint on the beginning of https://maven.apache.org/surefire/maven-failsafe-plugin/.

To me it's a little bit confusing that the roadmap seems to list 3.0.0-M9 as the latest release though only M5 is available (at least on Maven Central). From my point of view as a simple user of failsafe a clear distinction of really released releases and planned releases would be helpful.

@Whitespirit0
Copy link

Hello @Tibor17,
I'm very interested in the fix https://issues.apache.org/jira/browse/SUREFIRE-1800 and would like to know if you have an estimated release date for 3.0.0-M6?

@ahoehma
Copy link

ahoehma commented Mar 7, 2022

Hi all ... any news regarding new versions ... I'm little bit blocked to update testng over 7.4.0 because of some incomp. changes.

With testng 7.5 and surefire 3.0.0-M5 ...

Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
org.testng.xml.XmlSuite.setParallel(Ljava/lang/String;)V
java.lang.NoSuchMethodError: org.testng.xml.XmlSuite.setParallel(Ljava/lang/String;)V
at org.apache.maven.surefire.testng.conf.TestNGMapConfigurator.configure(TestNGMapConfigurator.java:71)
at org.apache.maven.surefire.testng.conf.TestNG510Configurator.configure(TestNG510Configurator.java:40)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:111)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeLazy(TestNGDirectoryTestSuite.java:123)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:90)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:145)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)

2021 there was a hint about upcomming surefire fixes for this ... but nothing happend yet :)

https://groups.google.com/g/testng-users/c/0uuHRo-xJ04/m/mynTFvprBQAJ

Maybe someone can point my to an issue ... I can try to provide a MR?!

Strange fix for me ... If I remove classes from my surefire configuration then my build runs with testng 7.5. A kind of default ist then working okayisch.

PS: sorry if I spam here ... please tell me ... then I will move my comment here to the right pos. thanks

@Tibor17
Copy link
Contributor Author

Tibor17 commented Mar 7, 2022

@ahoehma
You are writing right on the time. I can see the only one pending PR #478 to complete. I do not have more significant requirements. Some Jira issues will be shifted but that's okay.

@Whitespirit0
Copy link

That's great news @Tibor17! Looking forward to this release 🤩

@asfgit asfgit closed this Mar 27, 2022
@asfgit asfgit deleted the milestones-roadmap branch March 27, 2022 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants