Following the screenshots's trail I had this result:
Given Callie decides to use the Super Calculator
Callie navigates to '/protractor-demo/'
When she adds 19 and 23
Callie enters a left operand of 19
Callie enters a right operand of 23
Callie confirms calculation
Callie enters 19 into the left operand input
Callie waits up to 5s until the left operand input does become visible
Callie clicks on the left operand input
Callie selects the + operator...
Resuming, after step 6 you have more details about step 3. So, the details of a scenario turns a bit confuse when 'read' only by the screenshots.
While in console the result is similar to:
Given Callie decides to use the Super Calculator
✓ Callie navigates to '/protractor-demo/'
When she adds 19 and 23
Callie enters a left operand of 19
✓ Callie enters 19 into the left operand input
✓ Callie waits up to 5s until the left operand input does become visible
✓ Callie clicks on the left operand input
✓ Callie selects the + operator
Callie enters a right operand of 23
✓ Callie enters 23 into the right operand input
Callie confirms calculation
✓ Callie clicks on the "Go" button
Then she should see that the result is 42
✓ Callie ensures that the text of the result does equal '42'
Are there a explanation about this or a way better to present screenshots (like only in Tasks calls or Step calls) ?
The text was updated successfully, but these errors were encountered:
jacquecosta commentedMay 28, 2020
Looking at the report generated on template's project for protractor and cucumber, I have noticed this behaviour:
Resuming, after step 6 you have more details about step 3. So, the details of a scenario turns a bit confuse when 'read' only by the screenshots.
Are there a explanation about this or a way better to present screenshots (like only in Tasks calls or Step calls) ?
The text was updated successfully, but these errors were encountered: