discourse/test/javascripts/acceptance/new-message-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

42 lines
1012 B
JavaScript

import { acceptance } from "helpers/qunit-helpers";
acceptance("New Message");
QUnit.test("accessing new-message route when logged out", async assert => {
await visit(
"/new-message?username=charlie&title=message%20title&body=message%20body"
);
assert.ok(exists(".modal.login-modal"), "it shows the login modal");
});
acceptance("New Message", { loggedIn: true });
QUnit.test("accessing new-message route when logged in", async assert => {
await visit(
"/new-message?username=charlie&title=message%20title&body=message%20body"
);
assert.ok(exists(".composer-fields"), "it opens composer");
assert.equal(
find("#reply-title")
.val()
.trim(),
"message title",
"it pre-fills message title"
);
assert.equal(
find(".d-editor-input")
.val()
.trim(),
"message body",
"it pre-fills message body"
);
assert.equal(
find(".users-input .item:eq(0)")
.text()
.trim(),
"charlie",
"it selects correct username"
);
});