Part 2: Mock Two Week Sprint Day 1and Day 2
Mock two week sprint using Behavior Driven Development with Page Objects
Day 1 of the Sprint
Sprint Planning Meeting:
1. The first part of the Sprint Planning Meeting is attended by the full team, this includes the Product Owner – the Product Owner presents the highest priority backlog items to the team – the team holds a Q&A with the Product Owner to ensure that requirements are understood. The team and Product Owner then agree on the sprint Objectives.
2. The second part of the session is usually only attended by the team. During this session the team discusses the requirements, make their sprint commitments and agree a delivery strategy.
User Story Example – As a registered user, I want to be able to login, so I can access my account.
Acceptance Criteria Example
1. On a successful login the user will be referred to their home page.
2. When the “Remember me” is checked on a successful login – a cookie will be stored/automatic login next time
3. When the “Remember me” is not checked on a successful login – no cookie will be stored/force login next time
4. On a login failure due to unrecognized user name – message displayed “Unrecognized user name, please try again”
5. On a login failure due to incorrect password – message displayed “Incorrect password, please try again”
6. On a login failure due to service being unavailable – message displayed “Service unavailable, please try again”
7. On a login failure due to Account being expired – message displayed “Account has expired – refer to Help”
Day 2 of the Sprint
The daily stand-up meeting lasts for no more than 15 minutes and is attended by the sprint team. All relevant stakeholders and the Product Manager are invited to these meetings, but they’re not allowed to say anything.
Each team member answers the three Daily Scrum Questions:
1. What have I done since the last Scrum,
2. What am I going to do today (does this impact anyone else?)
3. Is there anything blocking you (or likely to block you) from delivering to plan?
The Scrum should be held in front of the team Task Board and an up-to-date Burn down Chart should be on the board for all to see. Any conversations deviating from the above questions should be held after the Scrum.
Design Session: During the design session the team will create the Behavior Driven Development mockups of the new feature and any needed work flows. During the design session the team will also agree on naming conventions to be used for any new services to be created thus allowing the automation to be stubbed out.
Example Mock Ups of Login and Welcome Pages
Test Case Design Session: During the Test Case Design Session the automation engineer(s), manual testers and any other team members that participate in testing such as developers and business analysts would meet to determine the testing strategy and write out any test cases.
Automation Tasks Day 2 – The team members responsible for creating the Page Objects and test cases for automation would start building the required Page Objects from the BDD mockup. Once the number of required Page Objects are determined and the classes are created, the automation team members would start stubbing out the services (methods) available on the Page Objects. For each new feature or legacy change, a new code branch would be created. The automation team members would checkout the new branch. As new code is created, it should be checked into the CMS.