Last active
April 5, 2018 21:27
-
-
Save nicopaez/52fcb6d18179d09abf17178450909422 to your computer and use it in GitHub Desktop.
ejercicio_escenarios
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Consigna: | |
Trabajando en grupos identificar las partes "buenas" y "malas" de los siguientes escenarios | |
tomando en cuenta las siguientes consideraciones: | |
* ¿Es claro lo que el escenario está describiendo? | |
* ¿Hay mucho/pocos detalles? | |
* ¿Utiliza un lenguaje que todos pueden entender? | |
* ¿Cuán probable es que este escenario cambie cuando cambie la aplicación? | |
A) | |
Scenario: Username should be unique | |
Given a user "Marvin" is in the database | |
And I navigate to http://myapp.com | |
And I click on "Register" | |
And I fill in "Usename" with "Marvin" | |
And I fill in "Password" with "1234" | |
When I click on "Submit registration" | |
The "ValidateSummary" should be visible | |
B) | |
Scenario: Delivery Address change | |
Given I have placed an order | |
When I change the delivery address | |
Then I should receive a confirmation | |
And the estimated arrival time should be updated | |
And the delivery person should notified about the new address | |
C) | |
Scenario: Client receives order notification | |
Given I visit Geek Pizza shop site | |
And I browse for "Margarita" pizza | |
And I add the pizza to the basket | |
And I proceed to checkout | |
And I enter delivery address | |
And I enter payment details | |
When I confirm the order | |
The I should receive and order notification |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment