We used many global functions to handle tests when they should be imported like other libraries in our application. This also gets us closer to the way Ember CLI prefers our tests to be laid out.
60 lines
1.5 KiB
JavaScript
60 lines
1.5 KiB
JavaScript
import { test } from "qunit";
|
|
import selectKit from "discourse/tests/helpers/select-kit-helper";
|
|
import { acceptance } from "discourse/tests/helpers/qunit-helpers";
|
|
|
|
acceptance("Topic Notifications button", {
|
|
loggedIn: true,
|
|
pretend(server, helper) {
|
|
server.post("/t/280/notifications", () => {
|
|
return helper.response({});
|
|
});
|
|
},
|
|
});
|
|
|
|
test("Updating topic notification level", async (assert) => {
|
|
const notificationOptions = selectKit(
|
|
"#topic-footer-buttons .topic-notifications-options"
|
|
);
|
|
|
|
await visit("/t/internationalization-localization/280");
|
|
|
|
assert.ok(
|
|
notificationOptions.exists(),
|
|
"it should display the notification options button in the topic's footer"
|
|
);
|
|
|
|
await notificationOptions.expand();
|
|
await notificationOptions.selectRowByValue("3");
|
|
|
|
assert.equal(
|
|
notificationOptions.header().label(),
|
|
"Watching",
|
|
"it should display the right notification level"
|
|
);
|
|
|
|
const timelineNotificationOptions = selectKit(
|
|
".topic-timeline .widget-component-connector .topic-notifications-options"
|
|
);
|
|
|
|
assert.equal(
|
|
timelineNotificationOptions.header().value(),
|
|
"3",
|
|
"it should display the right notification level"
|
|
);
|
|
|
|
await timelineNotificationOptions.expand();
|
|
await timelineNotificationOptions.selectRowByValue("0");
|
|
|
|
assert.equal(
|
|
timelineNotificationOptions.header().value(),
|
|
"0",
|
|
"it should display the right notification level"
|
|
);
|
|
|
|
assert.equal(
|
|
notificationOptions.header().label(),
|
|
"Muted",
|
|
"it should display the right notification level"
|
|
);
|
|
});
|