discourse/test/javascripts/acceptance/group-manage-profile-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

47 lines
1.1 KiB
JavaScript

import { acceptance, updateCurrentUser } from "helpers/qunit-helpers";
acceptance("Managing Group Profile");
QUnit.test("As an anonymous user", async assert => {
await visit("/g/discourse/manage/profile");
assert.ok(
count(".group-members tr") > 0,
"it should redirect to members page for an anonymous user"
);
});
acceptance("Managing Group Profile", { loggedIn: true });
QUnit.test("As an admin", async assert => {
await visit("/g/discourse/manage/profile");
assert.ok(
find(".group-flair-inputs").length === 1,
"it should display avatar flair inputs"
);
assert.ok(
find(".group-form-bio").length === 1,
"it should display group bio input"
);
assert.ok(
find(".group-form-name").length === 1,
"it should display group name input"
);
assert.ok(
find(".group-form-full-name").length === 1,
"it should display group full name input"
);
});
QUnit.test("As a group owner", async assert => {
updateCurrentUser({ staff: false, admin: false });
await visit("/g/discourse/manage/profile");
assert.equal(
find(".group-form-name").length,
0,
"it should not display group name input"
);
});