I have a strange issue with QUnit. This test is extremely simple and should be straightforward … but … A plugin setting is changing from those I have set up. test/javascripts/acceptance/composer-default-location-test.js b87a63b54 boundingbox: ["51.28676…

I took this for a spin locally. Looks like there a few factors at play: The siteSettings object you’re referencing is being obtained by the initializer, and then used in a modifyClass call: assets/javascripts/discourse/initializers/location-edits.js.es6 59525d1d82 …

David, thanks so much! That’s quite a gotcha!

David, FYI There’s another issue here which I suspect is for the same reason: currentUser is also defined in the initialiser. If the wrong test runs second this is evaluated and this is no longer defined so the tests when run together can fail “half” of the time. I think the Composer model has u…

Comportement QUnit étrange ?: le test échoue car la définition de la valeur ne survit pas

Dev

merefield (Robert) Août 7, 2023, 10:55 3

David, merci beaucoup ! C’est une sacrée surprise !

Sujet		Réponses	Vues
Is it possible to override the Site object with own fixture during Front End tests of a Plugin? Development	2	420	Décembre 28, 2022
Qunit tests not deterministic in Plugin? Development	1	395	Juillet 20, 2022
Loading our SiteSetting properties before plugin loads Development	14	3715	Juillet 8, 2016
Site Settings keep changing Self-hosting unsupported-install	2	712	Mars 15, 2020
"No setting named __ exists" when trying to run specs on poll plugin Product Support	9	1053	Septembre 27, 2022

Comportement QUnit étrange ?: le test échoue car la définition de la valeur ne survit pas

Sujets connexes