Skip to content

fix: move the debug for me button to the connection error toast COMPASS-9746 #7247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 29, 2025
Merged

fix: move the debug for me button to the connection error toast COMPASS-9746 #7247

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1479cc2
move the debug for me button to the connection error toast
lerouxb Aug 28, 2025
2661039
no assistant in web for now
lerouxb Aug 28, 2025
3b6d4f8
add ticket
lerouxb Aug 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 17 additions & 15 deletions packages/compass-e2e-tests/tests/connection.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,22 +334,24 @@ describe('Connection string', function () {
.$(Selectors.ConnectionModal)
.waitForDisplayed({ reverse: true });

await browser.clickVisible(Selectors.ConnectionToastErrorDebugButton);
// TODO(COMPASS-9759) we might have to opt-in via the modal once that's a thing
const messagesElement = browser.$(Selectors.AssistantChatMessages);
await messagesElement.waitForDisplayed();
// TODO(COMPASS-9748) check the response from the chatbot too

await browser.waitUntil(async () => {
return (await messagesElement.getText()).includes(
'Given the error message below,'
);
});
if (!TEST_COMPASS_WEB) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is surprising, I'm enabling the ff locally and it seems to work just fine:

image

Why are we skipping those here? Do we have a ticket for re-enabling those?

Copy link
Contributor Author

@lerouxb lerouxb Aug 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://parsley.mongodb.com/evergreen/10gen_compass_main_test_web_sandbox_test_web_sandbox_firefox_2_patch_1d36e9c0586021832d811666b49b79248fb23020_68b0680339847f0007138d62_25_08_28_14_30_29/0/task?bookmarks=0,26810

and also https://spruce.mongodb.com/task/10gen_compass_main_test_web_sandbox_test_web_sandbox_chrome_2_patch_1d36e9c0586021832d811666b49b79248fb23020_68b0680339847f0007138d62_25_08_28_14_30_29/logs?execution=0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://jira.mongodb.org/browse/COMPASS-9768

await browser.clickVisible(Selectors.ConnectionToastErrorDebugButton);
// TODO(COMPASS-9759) we might have to opt-in via the modal once that's a thing
const messagesElement = browser.$(Selectors.AssistantChatMessages);
await messagesElement.waitForDisplayed();
// TODO(COMPASS-9748) check the response from the chatbot too

await browser.waitUntil(async () => {
return (await messagesElement.getText()).includes(
'Given the error message below,'
);
});

// clear the chat so that a broken message doesn't break every future message
await browser.clickVisible(Selectors.AssistantClearChatButton);
await browser.clickVisible(Selectors.ConfirmClearChatModalConfirmButton);
await browser.clickVisible(Selectors.SideDrawerCloseButton);
// clear the chat so that a broken message doesn't break every future message
await browser.clickVisible(Selectors.AssistantClearChatButton);
await browser.clickVisible(Selectors.ConfirmClearChatModalConfirmButton);
await browser.clickVisible(Selectors.SideDrawerCloseButton);
}
});

it('can connect to an Atlas replicaset without srv', async function () {
Expand Down
Loading