discourse/test/javascripts/acceptance/email-notice-test.js.es6
Robin Ward a8793d0d9a 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`
2019-06-14 14:54:20 +02:00

36 lines
956 B
JavaScript

import { acceptance, updateCurrentUser } from "helpers/qunit-helpers";
acceptance("Email Disabled Banner", {
loggedIn: true
});
QUnit.test("shows banner when required", async assert => {
Discourse.set("SiteSettings.disable_emails", "no");
await visit("/");
assert.notOk(
exists(".alert-emails-disabled"),
"alert is not displayed when email enabled"
);
Discourse.set("SiteSettings.disable_emails", "yes");
await visit("/latest");
assert.ok(
exists(".alert-emails-disabled"),
"alert is displayed when email disabled"
);
Discourse.set("SiteSettings.disable_emails", "non-staff");
await visit("/");
assert.ok(
exists(".alert-emails-disabled"),
"alert is displayed when email disabled for non-staff"
);
updateCurrentUser({ staff: true, moderator: true });
await visit("/");
assert.ok(
exists(".alert-emails-disabled"),
"alert is displayed to staff when email disabled for non-staff"
);
});