Navigates to a mock standard single-step login page where both username and password fields are visible and editable on initial page load. The extension should identify both fields, fill the provided credentials, click the Login button, and continue to the next page without requiring any additional intermediate step.
Navigates to a mock two-step login page where only the username field is available on initial page load. The extension should detect the first-step username form, fill the username, click Continue, wait for the password step to render, identify the password field, fill it, and then click the Login button on the second step.
Navigates to a mock localhost login page used to test localhost environment matching and login automation together. The extension should recognize that the page is part of the localhost flow, identify the username and password fields, fill both values, click Login, and proceed into the mocked localhost AdviserGo route.
Navigates to a mock localhost protected interstitial page that simulates a browser security warning before reaching the application. The extension should identify this page type, click the Advanced button, wait for the additional details section to appear, and then click the proceed link to continue to the localhost destination.
Login actions should not depend on route identification alone, because any of the supported login flows could appear at any time behind the same route. Use the randomized buttons below to test that the extension detects the actual page state and chooses the correct login method from the rendered DOM.
If absolutely necessary, the extension may detect the /login route first, but it should still
decide the login approach from the page content after load rather than assuming a specific login flow.
Navigates to a mock client import flow. On page load, the extension should identify the import page, click the .VYT File import option, trigger the Choose File action, detect when a file has been selected, and then click Upload File once the upload button becomes enabled.
Navigates to a mock client export flow. On page load, the extension should identify the export page, recognize the export modal or popup, locate the .VYT Export action within the export options section, and click that button to trigger a browser download of the mock export file.
Instruction: extract the Jira code from the URL when each site is navigated too.
Some links contain the issue reference in the path and some contain it in the
selectedIssue query parameter.
Instruction: extract the region from each link hostname and save the normalized AGO link. These examples include UK, CA, and AU environments across integrations, staging, test, and localhost-style domains.
Instruction: these links should not match Regex site identifiers.
https://jira.ethanjohnsrud.com/jira/software/c/projects/MAS/boards/99/backlog
https://jira.ethanjohnsrud.com/issues/?jql=project%20%3D%20MAS
https://jira.ethanjohnsrud.com/browse/UK
https://jira.ethanjohnsrud.com/browse/UK-1
https://jira.ethanjohnsrud.com/browse/uk-22
https://jira.ethanjohnsrud.com/jira/software/c/projects/MAS/boards/99/backlog?selectedIssue=uk-22
https://notjira.ethanjohnsrud.com/browse/AGO-3065
https://uk-integrations.ethanjohnsrud.com/voyant/main/user/view
https://uk-integrations.ethanjohnsrud.com/advisergo/#/not-a-client-id/not-a-plan-id
https://example.com/not-jira/AGO-3065
Below are snippets of HTML from the rendered page, please use context to extract the relevant text from the DOM.
From snippet below, extract text: Base Plan
From snippet below, extract text: Campbell, John & Julia and save as clientFullName
From snippet below, extract text: Campbell and save as clientLastName
Campbell, John & JuliaFrom snippet below, extract text: Ready for Merge to Staging then reduce to acronym RFMTS and save as status
From snippet below, extract text: March 27th, 2026 then reduce to Mar-27 and save as sprint
From snippet below, extract text: Important & Immediate Action Needed: Fix Production Bug and save as title