-
Notifications
You must be signed in to change notification settings - Fork 15
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
Introduce setup and teardown hooks for tests #2
base: master
Are you sure you want to change the base?
Conversation
I am not in any way the official maintainer of CuTest, I've just created a github repository for my own needs that some people are forking, and that I (infrequently) update with the official releases. If you want your changes to become part of the "official" CuTest, you should probably contact the creator at http://cutest.sourceforge.net/ |
Thank you for clarifying. As the sourceforge-project appears to be abadoned (it didn't even migrate away from CVS, and last real activities seem to be a decade ago), I was under the impression, that you intended to pick that project up as I found your repository on github. I'll try to contact Asmin. |
There is a pretty good chance that it's been abandoned (sourceforge is merely a graveyard for old projects now), in which case I could be guilted into maintaining a fork, so let me know whether you hear back from the maintainer. |
I would like to bump this discussion. It would be cool to see some new life being brought into this library. |
Thanks for following up. As announced back in March last year, I tried to contacted Asim, the original author of the library. I didn't get a reply yet. So it's very likely @ennorehling is right: the project appears to be abandoned... |
In that case i think it might make sense to take this repo up and making it the unofficial continuation of the project? After all the original library was under an MIT license. |
In order to simplify creation of multiple tests (partially) sharing the same setup procedures, a possibility to hook into the test execution is introduced: Hooks for setting up the test (before the test executes) and tearing down the setup after the test executed.
I've TDDed the changes and thus extended the existing tests. However I didn't spend too much time yet for thinking about refactoring the test code. Still I wanted to float that change over to you as a request for comment, @ennorehling.