-
Notifications
You must be signed in to change notification settings - Fork 2
Gitlab 124: Implementing fixtures #69
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.
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
base: main
Are you sure you want to change the base?
Conversation
…dding product to cart. WIP: Rewriting tests to utilize fixtures
…te helper functions to accomodate fixtures
…lt address has been set
…d removeProduct() to first check if there actually is a product to remove
…ure. Renamed both tests to keep test names unique
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nagekeken!
@@ -105,21 +23,24 @@ test.describe.serial('Account address book actions', { annotation: {type: 'Accou | |||
* @then I should see a notification my address has been updated. | |||
* @and The new address should be selected as default and shipping address | |||
*/ | |||
productTest('Add_the_first_address', {tag: ['@address']}, async ({userPage}, testInfo) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you have a look at all these user tests? Looks like this should be called something like userTest
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gitlab ticket has been created to rename this!
This branch implements 3 fixtures for tests: