- 🇳🇿New Zealand quietone
I checked the issue and git, #2827014: Throw an exception when testing status code or response headers in functional JavaScript tests → was committed to branch 8.4.x and 8.5.x, and was in the 8.4.0 release.
- Merge request !7942Finish deprecating status code and header assertions in JS tests #3318988 → (Closed) created by andypost
- 🇫🇷France andypost
still needs work to split removal of status-code checks, so probably 12.x material
- Status changed to Needs work
10 months ago 4:13pm 22 June 2024 - 🇫🇷France andypost
proper status to deprecate in 11.x and remove in 12
- Status changed to Needs review
10 months ago 5:11pm 23 June 2024 - 🇬🇧United Kingdom longwave UK
Fixed the deprecation message, tagged for removal in 12.0.0.
- 🇬🇧United Kingdom longwave UK
@andypost re #2 all those usages are in BTB functional tests, not JavaScript tests.
- Status changed to RTBC
10 months ago 12:05am 25 June 2024 - 🇺🇸United States smustgrave
Oh wow 8.4 stuff
Applied MR and verified all deprecations in file are updated.
- Status changed to Fixed
10 months ago 5:06pm 3 July 2024 - 🇬🇧United Kingdom catch
It's almost impossible to add this back - selenium doesn't provide the information back to PHP at all, there is not really a nice API even executing javascript against the browser to get it either. I had to do similar things for performance testing, and they were pretty evil, we can live without it until there's a nice way to get it, if that happens.
Committed/pushed to 11.x and cherry-picked back to 10.3.x given this is just a text change in the deprecation message.
Automatically closed - issue fixed for 2 weeks with no activity.
