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

Needs TestNG support #441

Closed
SebTardif opened this issue Dec 14, 2012 · 13 comments
Closed

Needs TestNG support #441

SebTardif opened this issue Dec 14, 2012 · 13 comments

Comments

@SebTardif
Copy link

TestNG was mainly created to fix the flaw of JUnit. TestNG generates compatible JUnit report, is fully Maven compatible, and has an Eclipse plug-ins.

We need native integration with TestNG to be able to leverage our existing tests framework via Cucumber.

@aslakhellesoy
Copy link
Contributor

The JUnit Cucumber runner is a way to kick off Cucumber from JUnit. When you use this you only use the assertion parts of JUnit.

TestNG may bring improvements over JUnit, but these are primarily in how tests are organised, not how assertions are written.

Since none of these are relevant when using Cucumber I'm not sure I understand what benefits a TestNG runner would provide.

Can you elaborate?

@SebTardif
Copy link
Author

Our existing automated tests, that are not using Cucumber, are using TestNG due to the design fix it has. Was impossible to do the same with JUnit.

So now we want to add more automated tests to the same suites but using Cucumber, so we will end-up to have a mix of automated tests approach. The same run should end-up with a single JUnit report, and single coverage report.

Also, in the IDE, users want to run all of them using the same plug-in, in this case the TestNG plugin.

Our automated tests are testing UI using Selenium and also do coverage analysis, it has complex life-cycle to put all the pieces together, we have this life-cycle handled with TestNG.

@aslakhellesoy
Copy link
Contributor

I see, makes sense. I'm not planning on using TestNG any time soon, so I won't be the one implementing it.

were you planning to contribute a cucumber-testng module?

@maximenajim
Copy link

+1 for TestNG support

I've used the TestNG test factory solution outlined here: https://github.com/talios/cucumber-testng-factory
It works well ... possibly this can be integrated into Cucumber-JVM somehow.

@gimlet2
Copy link

gimlet2 commented Feb 28, 2013

We made TestNG wrapper for Cucmber: https://github.com/lionhearth/cucumber-testng. But it'll be great to have TestNG support out from the box.

@aslakhellesoy
Copy link
Contributor

@gimlet2 what are you waiting for? Send us a pull request :-)

@aslakhellesoy
Copy link
Contributor

@gimlet2 are you interested in making this a part of cucumber-jvm just like cucumber-junit?

@pranasblk
Copy link

+1 for TestNG support
I am new in GitHub, but may consider pooling and adjusting https://github.com/talios/cucumber-testng-factory

@aslakhellesoy
Copy link
Contributor

@gimlet2 you said you'd be able to have TestNG support out of the box. That will only happen if you send us a pull request. Are you still interested in that or not?

@yohannesalazar
Copy link

Hi aslakhellesoy,

now that cucumber-jvm supports testNg, what is needed for a project that is implemented with junit tests to be covered to TestNg , a little instruction will be of great help. We need to do this as we wanted to support multi browser testing using selenium grid which can not be achieved with junit.
Thank you in advance

@aslakhellesoy
Copy link
Contributor

@yohannesalazar please post your question to the cukes google group instead.

@paoloambrosio
Copy link
Member

@yohannesalazar this is an issue tracker and NOT a discussion group. Please repost your question in the Cukes Google Group. Also if you address the community and not Aslak directly, you might get more answers.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants