Open tonicauto opened 5 months ago
As Discussed please keep this following step "Then modal window will appear with options" in one test case rather than verifying for every test case.
Please add consistent steps for login functionality either Given the customer is on the "Online Order" web application When the customer click on top right corner sign in icon Then modal window will appear with options When the customer enters "Email" and "Password" And click "Log In" button Then will display message "Welcome back!" And successfully logged in
or
1 Step: Logging in as an Existing Customer Given the customer is on the "Online Order" web application When the customer clicks on the sign-in icon in the top right corner And the customer enters their "Email" and "Password" And clicks the "Log In" button Then the customer should be successfully logged in and see a message "Welcome back!"
1 Step: Logging in as an Existing Customer Given the customer is on the "Online Order" web application When the customer clicks on the sign-in icon in the top right corner And the customer enters their "Email" and "Password" And clicks the "Log In" button Then the customer should be successfully logged in and see a message "Welcome back!"
this scenario looks good for me as then should be at the end of the gherkin steps so we are verifying something at the end. If there is and at the end it sounds like we are ending steps in the middle.
Same here keep validation at the end saying that Then confirmation of successful update should be visible in "Profile" are we validating success message here then mention in the step like Then success message "Message" will be appear on the screen something like that.
Edit Account Demographics Information Given the customer is logged into their account
3 Step: Update Contact Details and Security Information Given the customer is logged into their account
for these two scenarios we have given statement as logged into account but instead can we validate like given we are on profile page or contact page whatever is applicable.
Then the system should confirm the update with a visible notification in the "Profile" section And the customer should be able to log in with the "NewEmail@example.com" and new "Password"
change it to
And the system should confirm the update with a visible notification in the "Profile" section Then the customer should be able to log in with the "NewEmail@example.com" and new "Password"
To validate below step we need previous order information. we can add it in example data like verify order number or which ever is important. Then the previous orders the customer made will display correctly
I don't understand what we are doing here. And when the customer cross-references the displayed order details with their own records Then the displayed items and total amount should accurately match the customer's records
1 Step: Login as existing customer Given the customer is on the "Online Order" web application When the customer clicks on the sign-in icon in the top right corner And the customer enters their "Email" and "Password" And clicks the "Log In" button Then the customer should be successfully logged in and see a message "Welcome back!"
2 Step: Edit Account Demographics Information Given the customer is on home page When they navigate to and open the "Profile" from the top right corner And they update the "Phone" number to "561-123-4567" And they change the "Address" to "1234 New Address Lane" And the customer updates the "Email" to "NewEmail@example.com" And the customer updates the "Name" to "NewName" And they confirm their password And the customer clicks the "Check" button to save changes Then the account information should be updated