| ... | @@ -3,21 +3,34 @@ |
... | @@ -3,21 +3,34 @@ |
|
|
|
|
|
|
|
# Acceptance Test Results
|
|
# Acceptance Test Results
|
|
|
### Chad Johnson
|
|
### Chad Johnson
|
|
|
1. "As a competitive person wanting to keep improving in all the sports I play, I want to see my performance, match data, historical statistics, and standings for all teams/leagues so I can become the best in my sports."
|
|
EPIC: "As a competitive person wanting to keep improving in all the sports I play, I want to see my performance, match data, historical statistics, and standings for all teams/leagues so I can become the best in my sports."
|
|
|
* User Story: "As a person wanting to keep track of stats and standings, I want to be able to input appropriate data after a game so that I can review it later when needed." (All acceptance criteria [and more] is met)
|
|
* User Story: "As a person wanting to keep track of stats and standings, I want to be able to input appropriate data after a game so that I can review it later when needed."
|
|
|
* User can input scores after a game is completed
|
|
* **Original Acceptance Criteria:**
|
|
|
* User can see their personal Wins, Ties, and Losses (in numerical and graphical format) on the home page
|
|
* App prompts the user to input game data after a game is finished.
|
|
|
* User can see each team Wins, Ties, and Losses (in numerical and graphical format) on the team page
|
|
* User can input individual match/game data and see it nicely laid out.
|
|
|
* User can see the Win:Loss ratio over time (as a line chart) on the Games page for each team
|
|
* **Final specific features implemented:**
|
|
|
* User can see their team ranked amongst other teams within a league (i.e. standings)
|
|
* Time, date, and location of a game is input when creating a game (and teams to play the game are also selected)
|
|
|
* User Story: "As a competitive person, I want to see game/match statistics after the game, so I can see how well my team played." (All acceptance criteria is met)
|
|
* User can input scores after a game is completed
|
|
|
* [Similar to above user story]
|
|
* [See below for "user can see data nicely laid out"]
|
|
|
* User can see each team Wins, Ties, and Losses (in numerical and graphical format) on the team page
|
|
* User Story: "As a competitive person, I want to see game/match statistics after the game, so I can see how well my team played."
|
|
|
* User can see the Win:Loss ratio over time (as a line chart) on the Games page for each team
|
|
* **Original Acceptance Criteria:**
|
|
|
* User Story: "As a person wanting to find trends and areas to improve, I want to see the historical game/match data for all games I have played against other teams." (All acceptance criteria is met)
|
|
* For every team in a league, there is a designated page that displays stats for the team.
|
|
|
* User can see each team Wins, Ties, and Losses (in numerical and graphical format) on the team page
|
|
* User can see the previous match data that was input.
|
|
|
* User can see the Win:Loss ratio over time (as a line chart) on the Games page for each team
|
|
* **Final specific features implemented:**
|
|
|
* User can see their team ranked amongst other teams within a league (i.e. standings)
|
|
* Stats for a team are displayed at the top of the team page (win:tie: loss bar chart) and the top of the games page (win: loss ratio over timeline graph)
|
|
|
|
* User can see each team Wins, Ties, and Losses (in numerical and graphical format) on the team page
|
|
|
|
* User can see the Win: Loss ratio over time (as a line chart) on the Games page for each team
|
|
|
|
* User can see their team ranked amongst other teams within a league (i.e. standings)
|
|
|
|
* User Story: "As a person wanting to find trends and areas to improve, I want to see the historical game/match data for all games I have played against other teams."
|
|
|
|
* **Original Acceptance Criteria:**
|
|
|
|
* User can see all match data for all previous games played against an individual team
|
|
|
|
* User can see all match data for all previous games played against all teams in a league
|
|
|
|
* **Final specific features implemented:**
|
|
|
|
* User can see all the previous games played for their team (info includes the opposing team and the final score)
|
|
|
|
* User can see each team Wins, Ties, and Losses (in numerical and graphical format) on the team page
|
|
|
|
* User can see the Win: Loss ratio over time (as a line chart) on the Games page for each team
|
|
|
|
* User can see their team ranked amongst other teams within a league (i.e. standings)
|
|
|
|
* User can see their personal Wins, Ties, and Losses (in numerical and graphical format) on the home page
|
|
|
|
|
|
|
|
| Test of | Test Instructions | Example |
|
|
| Test of | Test Instructions | Example |
|
|
|
|---|---|---|
|
|
|---|---|---|
|
| ... | @@ -29,17 +42,31 @@ |
... | @@ -29,17 +42,31 @@ |
|
|
|
|
|
|
|
### Robert Young
|
|
### Robert Young
|
|
|
|
|
|
|
|
1. As Robert Young, I want to manage a kids' soccer league so that my son and the kids in my community can engage in more physical activity and team sports.
|
|
EPIC: "As Robert Young, I want to manage a kids' soccer league so that my son and the kids in my community can engage in more physical activity and team sports."
|
|
|
* As Robert Young, I would like to be able to create a new sports league.
|
|
- User Story: "As Robert Young, I would like to be able to create a new sports league."
|
|
|
* **(Met)** User can create a league in their desired sport.
|
|
- **Original Acceptance Criteria:**
|
|
|
* **(Met)** User can specify the name and description.
|
|
- Users can create a league in their desired sport.
|
|
|
* As Robert Young, I want to be able to view and manage teams of my league.
|
|
- Users can specify the name and description.
|
|
|
* **(Discontinued, this permission was given to team owner instead)** League owner has ability to change certain attributes to teams.
|
|
- **Final specific features implemented:**
|
|
|
* **(Met)** League owner can view all the teams inside their league.
|
|
- Matches the original acceptance criteria.
|
|
|
* **(Discontinued due to time required to implement)** League owner can invite players.
|
|
- User Story: "As Robert Young, I want to be able to view and manage teams of my league."
|
|
|
* **(Discontinued, this permission was given to team owner instead)** League owner can remove players from the league.
|
|
- **Original Acceptance Criteria:**
|
|
|
* As Robert Young, I would like to be able to easily communicate information between the team owners.
|
|
- League owner has the ability to change certain attributes to teams.
|
|
|
* **(Discontinued due to being out of scope and time required to implement)** League owner and team owners are able to send and receive messages.
|
|
- League owners can view all the teams inside their league.
|
|
|
|
- League owners can invite players and remove players from the league.
|
|
|
|
- **Final specific features implemented:**
|
|
|
|
- League owners can view all the teams inside their league.
|
|
|
|
- League owners can remove the league.
|
|
|
|
- The team owners can remove players from the team, therefore removing them from the league.
|
|
|
|
- Teams only have a name so there is no attribute for league owners to change. This permission would be given to the Team owner if there were attributes to change.
|
|
|
|
- Members are free to join Teams inside of Leagues, can be removed by Team owners.
|
|
|
|
- User Story: "As Robert Young, I would like to be able to easily communicate information between the team owners."
|
|
|
|
- **Original Acceptance Criteria:**
|
|
|
|
- League owners and team owners are able to send and receive messages.
|
|
|
|
- **Final specific features implemented:**
|
|
|
|
- Originally intended to have an in-app messaging system for communication between teams in a league.
|
|
|
|
- Members of a team are able to see the phone numbers and emails of other team members.
|
|
|
|
- Members not part of a team are able to see emails of members on different teams or leagues.
|
|
|
|
|
|
|
|
|
|
|
|
|
| Acceptance Criteria | Test Instructions | Example |
|
|
| Acceptance Criteria | Test Instructions | Example |
|
| ... | @@ -99,34 +126,31 @@ |
... | @@ -99,34 +126,31 @@ |
|
|
|
|
|
|
|
### Jim Halpert
|
|
### Jim Halpert
|
|
|
|
|
|
|
|
As Jim Halpert, I want to create be able to create and manage my teams with effective communication so that my team can be the strongest in the league.
|
|
EPIC: "As Jim Halpert, I want to create be able to create and manage my teams with effective communication so that my team can be the strongest in the league."
|
|
|
|
|
* User Story: "Being team owner I should have access to all the teams I am part of, also I can update the members list as per required."
|
|
|
* Being team owner I should have access to all the teams I am part of, also I can update the members list as per required.
|
|
* **Original Acceptance Criteria:**
|
|
|
* User can check all the teams he own or he is member **(Met)**
|
|
* User can check all the teams he own or he is member
|
|
|
|
|
* User can act as admin for the respective group, he can ban or add new members
|
|
|
* User can act as admin for the respective group, he can ban **(Met)**
|
|
* **Final specific features implemented:**
|
|
|
|
|
* Matches the original acceptance criteria except for adding new members, new members have to click on join team by themselves but being admin owner can remove them.
|
|
|
* User can act as admin for the respective group, add new members **(Not Met)**
|
|
* User Story: "See team info for individual teams (including members, history of games, etc)."
|
|
|
|
|
* **Original Acceptance Criteria:**
|
|
|
|
|
* User can check the info for the player in a team and plan matches based on it.
|
|
|
* See team info for individual teams (including members, history of games, etc)
|
|
* User can notify teams for the game if there are some last-minute change
|
|
|
* User can check the info for player in a team and plan matches based on it. **(Met)**
|
|
* **Final specific features implemented:**
|
|
|
|
|
- The owner can check the individual player info and stats for performance
|
|
|
|
|
* User Story: "Being I team owner I am always looking for a good player to build a stranger team and increase our network."
|
|
|
|
|
* **Original Acceptance Criteria:**
|
|
|
|
|
* User can find and invite them a player with good stats
|
|
|
* User can notify teams for game if there are some last minute change **(Not Met)**
|
|
* **Final specific features implemented:**
|
|
|
|
|
* Matches the original acceptance criteria partially, the Owner can look up in other teams for the player and check their performance and for inviting user contact information can be used.
|
|
|
* Being I team owner I am always looking for good player to build stranger team and increase or network.
|
|
* User Story: "Being team owner I should be able to create a new team(groups) and manage them."
|
|
|
* User can find player with good stats **(Partially met, users can click on and see the information for a particular member of a team, but cannot yet see the stats or record of this user, we are planning on implementing this for our final product)**
|
|
* **Original Acceptance Criteria:**
|
|
|
|
|
* Users should be able to create a team and delete them as needed.
|
|
|
|
|
* User can update team information as an admin
|
|
|
* User can invite them player with good stats **(Not Met)**
|
|
* **Final specific features implemented:**
|
|
|
|
|
* Users can create new teams and delete them as needed.
|
|
|
* Being team owner I should be able to create new team(groups) and manage them.
|
|
* User can create new games and enter the game stats
|
|
|
* User should be able to create team and delete them as needed. **(Met)**
|
|
|
|
|
|
|
|
|
|
* User can update team information as an admin **(Not Met)**
|
|
|
|
|
|
|
|
|
|
| Acceptance Criteria | Test Instructions | Example |
|
|
| Acceptance Criteria | Test Instructions | Example |
|
|
|
| --- | --- | --- |
|
|
| --- | --- | --- |
|
| ... | | ... | |
