Please forgive my utter paranoia...
I have been burned recently by trivial composer.json bugs stopping clauses I thought were active from being employed.
I am almost certain - this could not cause problems - but it is better to fix it than worry about the consequences.
Beta phase evaluation
| Issue category | Bug: While the main thrust of this issue is to add integration test - techinically it also a bug fix with a regression test. |
|---|---|
| Issue priority | Not critical because ... they system works as it is. |
| Unfrozen changes | Unfrozen because it add an integration test see /core/tests/Drupal/Tests/ComposerIntegrationTest.php |
| Prioritized changes | The main goal of the issue is integration testing. |
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | drupal_2472269_8.patch | 2.8 KB | martin107 |
| #18 | justTest-2472269-18.patch | 2.17 KB | martin107 |
| #8 | drupal_2472269_8.patch | 2.8 KB | derhasi |
Comments
Comment #1
xanoI found another one.
Comment #2
xanoAnd now with tests.
Comment #3
xanoFixed a copy/paste error.
Comment #5
xanoIt didn't fail. I just cancelled it.
Comment #6
martin107 commented@Xano -Thank you :-) I will be smiling from ear to ear all day.
Yes Yes Yes fix the issue now and always before commit... I must adjust my perspective.
On a minor note I ran the new file through phpcs and found a couple of ultra trivial nits.
Comment #7
martin107 commentedfirst patch was adding a single comma, and could be justified as a minor quickfix
Adding beta evaluation
Comment #8
derhasi commentedAfter adding
@group Composerto the class, it appears in the PHPUnit section. (The group seems not to have a effect on the UI, is there an issue for that?)So I reapplied the patch with the given group annotation, so hopefully it will be recognized by the testbot too.
composer validatefor the changed composer.json works does not fail anymore too.Comment #9
derhasi commentedComment #10
xanoThe testbot picked up the test. Thanks!
Comment #11
derhasi commentedAs this was just an issue of the testbot, I think it is fine to RTBC, as the patch and test itself work nicely.
Comment #12
mile23Some similar work: #2337283: Add a composer.json file to every component
Comment #13
mile23+1 RTBC. The test makes us happy. :-)
Comment #14
mile23Comment #15
eclipsegc commentedJust ++ing the rtbc here.
Eclipse
Comment #16
mile23Comment #17
xjmSo it looks like the added test did indeed get run in https://qa.drupal.org/pifr/test/1025348, yay! However I'm unclear on what the earlier testbot issue was. There also is no test-only patch on this issue exposing the fails and that the test runs alright without the fix being there. (See https://www.drupal.org/core-gates#testing).
Can someone resubmit the patch as a test-only patch followed by a combined patch, to expose the test coverage? Thanks!
Comment #18
martin107 commentedThat is a good way to build confidence.
Comment #20
martin107 commentedComment #22
xjmThanks @martin107, that's a big help. So testbot does indeed properly report the failure in #18. And we can also confirm it's detecting the syntax error by applying the test-only patch locally and running it:
This issue is a normal bug fix, and doesn't include any disruptive changes, so it is allowed per https://www.drupal.org/core/beta-changes. Committed and pushed to 8.0.x. Thanks everyone! Also thanks for the beta evaluation.
Comment #24
davidwbarratt commentedThis change made unit tests fail for me, #2545344: Drupal\Tests\ComposerIntegrationTest assumes there is a composer.json in DRUPAL_ROOT