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.
26 lines
946 B
JavaScript
26 lines
946 B
JavaScript
import { test } from "qunit";
|
|
import selectKit from "discourse/tests/helpers/select-kit-helper";
|
|
import { acceptance } from "discourse/tests/helpers/qunit-helpers";
|
|
|
|
acceptance("Badges", { loggedIn: true });
|
|
|
|
test("Visit Badge Pages", async (assert) => {
|
|
await visit("/badges");
|
|
|
|
assert.ok($("body.badges-page").length, "has body class");
|
|
assert.ok(exists(".badge-groups .badge-card"), "has a list of badges");
|
|
|
|
await visit("/badges/9/autobiographer");
|
|
|
|
assert.ok(exists(".badge-card"), "has the badge in the listing");
|
|
assert.ok(exists(".user-info"), "has the list of users with that badge");
|
|
assert.ok(!exists(".badge-card:eq(0) script"));
|
|
});
|
|
|
|
test("shows correct badge titles to choose from", async (assert) => {
|
|
const availableBadgeTitles = selectKit(".select-kit");
|
|
await visit("/badges/50/custombadge");
|
|
await availableBadgeTitles.expand();
|
|
assert.ok(availableBadgeTitles.rowByIndex(1).name() === "CustomBadge");
|
|
});
|