An agile Java group project completed as our final project at Sparta. The deliverable of the project was to produce a testing framework suitable for testing the Sparta 1-1 tracker website created by a previous Java Development group and to Implement BDD, using JUnit5 and Cucumber. The aim was to verify the integrity of the code before it was actually implemented at Sparta.
- Jakub Matyjewicz - SCRUM Master and SDET
- Alasdair Malcolm - SCRUM Master and SDET
- Jack Ingham - SDET
- Alex Sikorski - SDET
- Golam Choudhury - SDET
- Abdul Makba - SDET
- Patrick Walsh - SDET
-
Do not touch the master branch.
-
The feature branches include software features that then merge in to the dev branch.
-
Follow SOLID principles.
-
Strictly adhere to OOP for scalability, maintainability, testability, and general robustness.
-Naming Convention: f(ticket number)-(small description) e.g. f76-prevWeekAccess
-Pushing code from a feature branch to the dev branch requires approval and review by 2 members of the team.
-Pushing code from the dev branch to the master branch requires approval and review by 1 member of the team and the scrum master.
-Minimum documentation per feature
-Code review
-Framework Unit tests passed
-Acceptance criteria met
-Product owner review / approval
The project uses a page-object model (POM). Each page has an associated interface with methods that abstract common areas to test behind easy to use, human readable functions. The pages also inherit from larger interfaces for behaviour and abstract classed when state is required.
Sprint 0 -> Planning and Interface Creation
Sprint 1 -> Implementation of Framework
Sprint 2 -> Unit Test Implementation and Refactor of Project
Sprint 3 -> Implementation of BDD layer and completion of left-over tasks from previous sprints.