test(e2e): point SSHSettingsPage at the new SSH executor routes
Updates the page object to navigate to the SSH-specific routes that now host the connection + sessions cards: - gotoNew(): /settings/executors/new?type=ssh → /settings/executors/new/ssh - gotoExisting(): /settings/executors/[executorId] → /settings/executors/ssh/[executorId] The old URLs collided with the standard profile-create / profile-edit flow and were never going to render the SSH cards. The new paths give the SSH UI its own surface, leaving the generic profile pages untouched.
This commit is contained in:
@@ -14,13 +14,13 @@ export class SSHSettingsPage {
|
||||
|
||||
/** Navigate to the new-executor flow. */
|
||||
async gotoNew(): Promise<void> {
|
||||
await this.page.goto("/settings/executors/new?type=ssh");
|
||||
await this.page.goto("/settings/executors/new/ssh");
|
||||
await expect(this.connectionCard).toBeVisible();
|
||||
}
|
||||
|
||||
/** Navigate to the edit page for an existing SSH executor. */
|
||||
async gotoExisting(executorId: string): Promise<void> {
|
||||
await this.page.goto(`/settings/executors/${executorId}`);
|
||||
await this.page.goto(`/settings/executors/ssh/${executorId}`);
|
||||
await expect(this.connectionCard).toBeVisible();
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user