mirror of
https://github.com/discourse/discourse.git
synced 2025-05-29 11:48:08 +08:00
REFACTOR: Test Memory Usage Fixes (#7769)
* Calling `Discourse.reset()` creates a new container We should run our de-initializers only after acceptance tests, since initializers are not run outside of acceptance tests anyway, and the container at this point can be passed properly to the `teardown()` method. * Remove `Discourse.reset` from tests This would cause a new container to be created which leaks many objects. * `updateCurrentUser` is more accurate than `replaceCurrentUser`
This commit is contained in:

committed by
Joffrey JAFFEUX

parent
c3381b845b
commit
a8793d0d9a
@ -1,4 +1,4 @@
|
||||
import { acceptance, replaceCurrentUser } from "helpers/qunit-helpers";
|
||||
import { acceptance, updateCurrentUser } from "helpers/qunit-helpers";
|
||||
|
||||
acceptance("Composer topic featured links", {
|
||||
loggedIn: true,
|
||||
@ -156,7 +156,7 @@ acceptance("Composer topic featured links when uncategorized is not allowed", {
|
||||
});
|
||||
|
||||
QUnit.test("Pasting a link enables the text input area", async assert => {
|
||||
replaceCurrentUser({ admin: false, staff: false, trust_level: 1 });
|
||||
updateCurrentUser({ admin: false, staff: false, trust_level: 1 });
|
||||
|
||||
await visit("/");
|
||||
await click("#create-topic");
|
||||
|
Reference in New Issue
Block a user