|
Wordle Status Check
|
We can check the status of the Wordle service by sending a GET to /api/service
|
|
1 |
10:13:42 |
050ms |
SUCCESS
|
|
Creating a new game
|
The new game should initially be In Progress
|
|
4 |
10:13:34 |
5s 386ms |
SUCCESS
|
|
Creating a new game
|
Each new game should be assigned a unique id
|
|
3 |
10:13:37 |
2s 752ms |
SUCCESS
|
|
Creating a new game
|
The new game should contain no moves
|
|
4 |
10:13:40 |
724ms |
SUCCESS
|
|
Game history and statistics
|
Game results are recorded in the game history
|
|
9 |
10:13:34 |
7s 771ms |
SUCCESS
|
|
Game history and statistics
|
Player statistics should appear in the leaderboard
|
|
11 |
10:13:42 |
2s 667ms |
SUCCESS
|
|
Game history and statistics
|
Game statistics can be retrieved for the current player
|
|
11 |
10:13:42 |
2s 834ms |
SUCCESS
|
|
Getting hints
|
We can request a hint for the current game via GET /api/game/{id}/hint
|
|
5 |
10:13:43 |
885ms |
SUCCESS
|
|
Getting hints
|
requestingAnotherHint(String)
3 passing test cases
|
|
6 |
10:13:45 |
332ms |
SUCCESS
|
|
Playing the game
|
Invalid words should be rejected with a 403 error
|
|
4 |
10:13:40 |
653ms |
SUCCESS
|
|
Playing the game
|
After the game has finished the answer can be revealed via via GET /api/game/{id}/answer
|
|
6 |
10:13:41 |
926ms |
SUCCESS
|
|
Playing the game
|
When we make a move, the move is recorded in the game history
|
|
5 |
10:13:42 |
634ms |
SUCCESS
|
|
Playing the game
|
We can check the current state of the game by sending a GET to /api/game/{id}/guesses
|
|
5 |
10:13:42 |
801ms |
SUCCESS
|
|
Playing the game
|
We can get the current game result by sending a GET to /api/game/{id}/result
|
|
4 |
10:13:43 |
588ms |
SUCCESS
|
|
Playing the game
|
If we try to ask for the answer by sending a GET to /api/game/{id}/answer
|
|
4 |
10:13:44 |
743ms |
SUCCESS
|
|
Playing the game
|
This is an example of a complete game played via the API
|
|
7 |
10:13:44 |
1s 032ms |
SUCCESS
|
|
Playing the game
|
We make a move by posting a word to the with the /api/game/{id}/word end-point
|
|
4 |
10:13:44 |
414ms |
SUCCESS
|
|
Playing the game
|
Each cell should be rendered in the correct color
3 passing test cases
|
|
6 |
10:13:45 |
355ms |
SUCCESS
|
|
Playing the game
|
shouldShowRowOfColoredCells(String, String, String, String, String, String, String)
3 passing test cases
|
|
6 |
10:13:45 |
485ms |
SUCCESS
|
|
Registering a new user
|
Password should be stored as a hashed password
|
|
1 |
10:13:34 |
4s 045ms |
SUCCESS
|
|
Registering a new user
|
Email must be unique
|
|
2 |
10:13:39 |
294ms |
SUCCESS
|
|
Registering a new user
|
Username must be unique
|
|
2 |
10:13:39 |
453ms |
SUCCESS
|
|
Registering a new user
|
Players need to register before they can login and play
|
|
1 |
10:13:40 |
312ms |
SUCCESS
|
|
Registering a new user
|
Logged-on players can play the game
|
|
3 |
10:13:40 |
578ms |
SUCCESS
|
|
Registering a new user
|
Password must not be empty
|
|
1 |
10:13:41 |
179ms |
SUCCESS
|
|
Registering a new user
|
Users cannot access the game without logging on
|
|
2 |
10:13:41 |
254ms |
SUCCESS
|
|
Registering a new user
|
Players can log on with their username and password
|
|
2 |
10:13:41 |
558ms |
SUCCESS
|