Skip to content

Conversation

dzygmundfelt
Copy link

I need more robust testing.

If I have the time, I'm going to do some refactoring, possibly to let the method that captures JUnit Test annotated methods take a String as input that would let it decide whether it wants to capture a Test, Before, or After.

I haven't really thought through how I would make use of the Before and After annotated methods, but I think they or the results of the methods that call them would belong in the runTest method. I can also do some cleaning up to increase my methods' adherence to SRP.

Also, I should probably have runTests return an ArrayList and then have a resultsToString method to call on that ArrayList. As is, I'm not actually saving that ArrayList anywhere.

Dan Zygmund-Felt and others added 14 commits May 2, 2017 22:04
…istAllMembers+Test. There are some specs (alphabetize, spacing) that need to be ironed out.
…ods method, and need to implement runTests.
…n't probably been totally fulfilled, but it looks like the UnitCorn is working for the simple cases I've created. Next will be making a larger dummy test class to explore.
…efore and @after to figure out what they do and how the UnitCorn could accommodate them.
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.

1 participant