- π³π±Netherlands spokje
Closed π claroAutocompleteTest passes, but log shows a 404 Active as a duplicate and going to repurpose this issue to preserve the original credits.
- Assigned to spokje
- Merge request !6053Resolve #2651798 "Claroautocompletetest passes but" β (Closed) created by spokje
- π³π±Netherlands spokje
So they should be working - in fact maybe the test should be changed to a FunctionalJavascriptTest so we can test the auto complete calling beyond just the existence of the links and autocomplete.js being loaded.
I think we should do that here instead so the trivial fix is actually tested.
@alexpott in #7 π form_test routes improperly defined, why doesn't this fail? Needs work
I disagree.
I would _love_ to convert every Nightwatch test to a FunctionalJavascriptTest, and drop Nightwatch altogether, but that's not very feasible.
Basically, we're a bit spoiled by FunctionalJavascriptTests, which not only test the (JS)-Frontend, but also look at backend errors.
Nightwatch doesn't. If the webserver spews errors in the range from 500 to 911, is on fire and with its last dying breath serves a page that meets the assertations, it's perfectly happy.That's why
claroAutocompleteTest
doesn't care about the invalid routes, it only asserts certain specific layout features of a autocomplete which is in progress. The result of the autocomplete is irrelevant and as proven, not even necessary.
The test is not about the inner workings of autocomplete, nor dependent on it even working.Like it or not, somebody somewhere decided to use a Nightwatch test for this, and I think we should stick with that.
Having said that: We should fix the routing, make the autocomplete work and test this in the Nightwatch test itself.
The latter part didn't exist in the test until now and is added.I hope this explanation makes any kind of sense?
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 3:32pm 7 January 2024 - Status changed to RTBC
about 1 year ago 6:05pm 7 January 2024 - πΊπΈUnited States smustgrave
Confirmed the issue by going by going to the last ticket merged
https://git.drupalcode.org/issue/drupal-3409587/-/jobs/505831/artifacts/...(Coordinated-Universal-Time)_console.json
Checked this MR https://git.drupalcode.org/issue/drupal-2651798/-/jobs/587545/artifacts/...(Coordinated-Universal-Time)_console.json
And no issue.
- π¬π§United Kingdom alexpott πͺπΊπ
Committed and pushed a4d53f09f6 to 11.x and e265a01324 to 10.2.x. Thanks!
Backported to 10.2.x since this only involved tests.
-
alexpott β
committed e265a013 on 10.2.x
Issue #2651798 by Spokje, cilefen, TR, smustgrave: claroAutocompleteTest...
-
alexpott β
committed e265a013 on 10.2.x
- Status changed to Fixed
about 1 year ago 9:34am 8 January 2024 -
alexpott β
committed a4d53f09 on 11.x
Issue #2651798 by Spokje, cilefen, TR, smustgrave: claroAutocompleteTest...
-
alexpott β
committed a4d53f09 on 11.x
Automatically closed - issue fixed for 2 weeks with no activity.