-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Issues with the Unit Test Suite #43
Comments
Well the thing I've noticed when adding 0c72e82 is that, with the current test setup I couldn't write actual assertions and that for some of the tests there are no assertions. The coverage of the tests is good, but they don't actually confirm that everything works as it is supposed to. This becomes apparent when running PHPUnit with the So basically we would need to check that the core features (i.e. getting data from the repositories) actually works. To keep the tests fast there are already offline Did I get everything right? |
@mihaeu any chance we can collaborate on this soon? Feel like tackling this issue :-), got some spare time at hands here and there. |
Hey there, sry I recently married and am in-between jobs so spare time I would still like to get it done, just can't make any promises about On 09/10/2014 12:45 PM, Michael Roterman wrote:
|
Congratulations first off all ;)! Been on your honeymoon as well? Alright I'll take a dive into it myself and see how far I'll get, I'll keep you updated. |
@mihaeu I've been working hard on improving on this in the I'd invite you to take a look at a bunch of these changes made in 870ed68, should be way improved. |
Since all risky tests are gone now, I'm closing this issue and continue onwards to imrpove the unit test suite quality in #51 |
Continuing from #42 on wards, @mihaeu maybe you can create a generic outline?
The text was updated successfully, but these errors were encountered: