Skip to content

Conversation

nmammadli
Copy link
Contributor

No description provided.

Copy link
Contributor

@vlad-dargel vlad-dargel left a comment

Choose a reason for hiding this comment

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

Great job!

just please check the names of the tests and make them the same as in the checklist
ideally, test names should be like in the 'Scenario' column, and checklist checks can be as comments inside the tests

verify onboarding step visible based on title
*/
async verifyStepVisible(stepName: string): Promise<void> {
await t.expect(Selector('[data-testid=step-title]').withText(stepName).exists).ok(`${stepName} step is not visible`);
Copy link
Contributor

Choose a reason for hiding this comment

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

please move these selectors below to pageObject

/**
complete onboarding process
*/
async verifyOnbardingCompleted(): Promise<void> {
Copy link
Contributor

Choose a reason for hiding this comment

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

typo here Onbarding

.afterEach(async() => {
await deleteDatabase(ossStandaloneConfig.databaseName);
});
test.skip('verify onboard new user steps', async t => {
Copy link
Contributor

Choose a reason for hiding this comment

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

no need to skip these tests, as env: env.desktop, they will run only on desktop pipelines

create page file
@nmammadli nmammadli merged commit 1dcba56 into fe/feature/RI-4067_onboard-new-users Feb 10, 2023
@nmammadli nmammadli deleted the e2e/feature/RI-4067_onboard-new-users branch February 10, 2023 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants