mirror of
https://github.com/zulip/zulip.git
synced 2025-10-31 03:53:50 +00:00
f6998d6fee
The only downside of this is that it makes it harder to control the order of these tests; which isn't that important. And the structure of naming each with its test order fundamentally requires renaming files when adding/deleting tests, so if we want to control the default test order, we'd be better off doing that by just hardcoding a list in the test runner code.
74 lines
3.1 KiB
TypeScript
74 lines
3.1 KiB
TypeScript
import {strict as assert} from "assert";
|
||
|
||
import type {Page} from "puppeteer";
|
||
|
||
import common from "../puppeteer_lib/common";
|
||
|
||
const email = "alice@test.example.com";
|
||
const subdomain = "testsubdomain";
|
||
const organization_name = "Awesome Organization";
|
||
const host = "zulipdev.com:9981";
|
||
|
||
async function realm_creation_tests(page: Page): Promise<void> {
|
||
await page.goto("http://" + host + "/new/");
|
||
|
||
// submit the email for realm creation.
|
||
await page.waitForSelector("#email");
|
||
await page.type("#email", email);
|
||
await Promise.all([
|
||
page.waitForNavigation(),
|
||
page.$eval("#send_confirm", (form) => (form as HTMLFormElement).submit()),
|
||
]);
|
||
|
||
// Make sure onfirmation email is sent.
|
||
assert(page.url().includes("/accounts/new/send_confirm/" + email));
|
||
|
||
// Special endpoint enabled only during tests for extracting confirmation key
|
||
await page.goto("http://" + host + "/confirmation_key/");
|
||
|
||
// Open the confirmation URL
|
||
const page_content = await page.evaluate(() => document.querySelector("body")!.textContent);
|
||
const confirmation_key = await JSON.parse(page_content!).confirmation_key;
|
||
const confirmation_url = "http://" + host + "/accounts/do_confirm/" + confirmation_key;
|
||
await page.goto(confirmation_url);
|
||
|
||
// We wait until the DOMContentLoaded event because we want the code
|
||
// that focuses the first input field to run before we run our tests to avoid
|
||
// flakes. Without waiting for DOMContentLoaded event, in rare cases, the
|
||
// first input is focused when we are typing something for other fields causing
|
||
// validation errors. The code for focusing the input is wrapped in jQuery
|
||
// $() calls which runs when DOMContentLoaded is fired.
|
||
await page.waitForNavigation({waitUntil: "domcontentloaded"});
|
||
|
||
// Make sure the realm creation page is loaded correctly by
|
||
// checking the text in <p> tag under pitch class is as expected.
|
||
await page.waitForSelector(".pitch");
|
||
const text_in_pitch = await page.evaluate(
|
||
() => document.querySelector(".pitch p")!.textContent,
|
||
);
|
||
assert(text_in_pitch === "You’re almost there! We just need you to do one last thing.");
|
||
|
||
// fill the form.
|
||
const params = {
|
||
realm_name: organization_name,
|
||
realm_subdomain: subdomain,
|
||
full_name: "Alice",
|
||
password: "passwordwhichisnotreallycomplex",
|
||
terms: true,
|
||
};
|
||
// For some reason, page.click() does not work this for particular checkbox
|
||
// so use page.$eval here to call the .click method in the browser.
|
||
await page.$eval("#realm_in_root_domain", (el) => (el as HTMLInputElement).click());
|
||
await common.fill_form(page, "#registration", params);
|
||
await page.$eval("#registration", (form) => (form as HTMLFormElement).submit());
|
||
|
||
// Check if realm is created and user is logged in by checking if
|
||
// element of id `lightbox_overlay` exists.
|
||
await page.waitForSelector("#lightbox_overlay"); // if element doesn't exist,timeout error raises
|
||
|
||
// Updating common.realm_url because we are redirecting to it when logging out.
|
||
common.realm_url = page.url();
|
||
}
|
||
|
||
common.run_test(realm_creation_tests);
|