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

Switch to TestNG #25

Closed
gissuebot opened this issue Jul 7, 2014 · 6 comments
Closed

Switch to TestNG #25

gissuebot opened this issue Jul 7, 2014 · 6 comments

Comments

@gissuebot
Copy link

From crazyboblee on February 22, 2007 16:37:00

For unit testing.

Original issue: http://code.google.com/p/google-guice/issues/detail?id=25

@gissuebot
Copy link
Author

From kevinb9n on February 26, 2007 19:02:40

why bother?

@gissuebot
Copy link
Author

From kevinb9n on February 27, 2007 00:06:10

(No comment was entered for this change.)

Labels: -Type-Defect -Priority-Medium Type-Task Priority-Low

@gissuebot
Copy link
Author

From lwerner on March 17, 2007 17:59:48

FWIW, my opinion isn't just "why bother" but "please don't".  Even though TestNG has
some really nice features, JUnit still seems to have a huge percentage of the user
base, and integrating the Guice tests into existing test suites (e.g. here at Google)
will be much easier if its tests remain in JUnit, at least until TestNG takes off
more than it has already.

@gissuebot
Copy link
Author

From gk5885 on April 15, 2007 12:45:45

Since you can use TestNG to run JUnit tests, couldn't you just add the TestNG jar and
use it for new tests?  As long as you use TestNG to run the tests, you shouldn't have
any trouble integrating it with any existing test suite.

@gissuebot
Copy link
Author

From kevinb9n on May 31, 2007 13:37:59

I still see no point in this and move to close it.

@gissuebot
Copy link
Author

From crazyboblee on September 07, 2007 11:17:22

(No comment was entered for this change.)

Status: WontFix

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