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

Replace TestNG with JUnit + Rules #298

Merged
merged 1 commit into from Mar 3, 2015

Conversation

codefromthecrypt
Copy link
Contributor

JUnit Rules, such as MockWebServerRule, reduce boilerplate setup present
in our tests. By migrating off TestNG, and onto rules, our tests become
more maintainable as JUnit is well understood.

JUnit Rules, such as MockWebServerRule, reduce boilerplate setup present
in our tests. By migrating off TestNG, and onto rules, our tests become
more maintainable as JUnit is well understood.
@cloudbees-pull-request-builder

denominator-pull-requests #408 SUCCESS
This pull request looks good

@cloudbees-pull-request-builder

NetflixOSS » denominator » denominator-pull-requests #33 SUCCESS
This pull request looks good

codefromthecrypt pushed a commit that referenced this pull request Mar 3, 2015
@codefromthecrypt codefromthecrypt merged commit 2ca855c into master Mar 3, 2015
@codefromthecrypt codefromthecrypt deleted the adrian.testng-to-junit_core branch March 3, 2015 06:36
@codefromthecrypt
Copy link
Contributor Author

ps now no tests use guava either. the only thing left that uses guava is the CLI, but those days are numbered, too.

UltraDNSLiveTest.GeoReadOnlyLiveTest.class,
UltraDNSLiveTest.GeoWriteCommandsLiveTest.class
})
public class UltraDNSLiveTest {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonbodner @jdamick Hopefully, centralizing this into one file keeps things more sane. There's mild refactoring opportunity, but I decided to stop as otherwise I'll get no more work done for the next month :) Anyway, feel free to start on the new rest provider in master, as the base test framework is at or near where I feel it should be in order to facilitate easier work in the future.

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.

None yet

2 participants