Closed (fixed)
Project:
Drupal Coverage Core
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
5 Oct 2016 at 05:36 UTC
Updated:
21 Oct 2016 at 08:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
legovaerComment #3
legovaerComment #4
legovaerThis patch introduces a PHPUnit test for the BuildData class. It also contains 2 fixes of code which was apparently broken (and caused me a headache while developing these unit tests).
Comment #5
jonathan1055 commentedI suggest you might as well commit this immediately. Then you can enable automated testing on d.o. and we can all see how the first test performs! Having a failing test but with automated testing running is better than no tests, and things can only get better from that point.
Comment #6
jonathan1055 commentedIn testSetModuleType($actual, $expected)
The assertEquals will always pass, as you are sending the same values in to the function. I think you probably meant
Comment #8
legovaerThanks for reviewing. I've committed this patch to 8.x-1.x so that we can enable the automated testing.
All tests are passing.. seems like we have our first unit tests in place ;)
Comment #9
jonathan1055 commentedThat's a great start. Well done!
I notice that the default core version for testing is 8.3. It might be useful to run a one-off custom test on D8.1 and D8.2 as I have found there to be differing results sometimes. It would be useful to have this information.
Comment #10
legovaerAll of the tests have passed except one. But this seems to be a bug in Drupal CI so I created an issue for that. RTBC?
Comment #11
jonathan1055 commentedThat's useful to see those extra test configurations passing. I have commented on #2813495: Test fail because supervisorctl: command not found as I've seen exactly that problem with Scheduler.
RTBC for sure, but you have already committed the code, so I will let you have the pleasure of setting it to 'fixed' ;-)
Comment #14
jonathan1055 commentedThat's interesting. It must be due to continual assessment testing - I set the status to RTBC but I did not manually ask for re-testing of the patches, that must have been automatic. Now the status has been reverted to 'needs work' because the patches no longer apply, as the work has already been committed. I won't set it to RTBC again, as I expect that may trigger another set of tests.
Comment #15
legovaerRight! I was mixing up several issues. Let's just close this one :)
Comment #16
legovaer