When a internet connection issue appear, we need to refresh the page. Make auto reconection

• New rule in selection page
• New GamInterface in backend
• Page 1 : select the friend in the party
• Page 2 : create the team and select who is victory
• Page 3 : game result
• It's full frontend until the confirm button who send a request to backend to confirm the game result and run calculation

On a party of 3 vs 2, they were a problem of next player calculation. Maybe because those players has been disconnected from the party

Reduce the size of the sumary block

Make the score calculation backend

• Add MongoDB to indus docker compose
• Make the PoolGame object as an MongoDB document to be persisted
• Save the game on game finished

Description of needs

Drafts or UI templates

Acceptance criteria (done when...)

Tip: Write a checkboxed list of sentences in the present tense describing the desired state of the system.

GOOD (clear how to verify, it reports design and interaction decisions
agreed):

• The page shows a button only to logged in users
• The button has the style XXX and label "Logout"
• When pressed, opens a confirmation modal with "OK" and "Cancel" buttons
• ...

BAD (cannot be activated during verification, too arbitrary):

• Logout button
• Modal for confirmation

Validation scenarios

Hint: Use Gherkin syntax to lay them out. It is complete and explicit, human-readable but easy to convert into self-executable tests.

Tip: A scenario title should describe in a complete sentence what happens in that scenario, to improve readability and indability.

OK: Administrator logs into back-office
BAD: Backoffice login

Tasks

This section is populated by the developer and reports the expected practical activities to meet the requirements. Useful for estimating and for day-by-day monitoring. Better if it reports checkboxes to track completion.

• Task 1
• Task 2
• ...

Notes

Description of needs

Drafts or UI templates

Acceptance criteria (done when...)

Tip: Write a checkboxed list of sentences in the present tense describing the desired state of the system.

GOOD (clear how to verify, it reports design and interaction decisions
agreed):

• The page shows a button only to logged in users
• The button has the style XXX and label "Logout"
• When pressed, opens a confirmation modal with "OK" and "Cancel" buttons
• ...

BAD (cannot be activated during verification, too arbitrary):

• Logout button
• Modal for confirmation

Validation scenarios

Hint: Use Gherkin syntax to lay them out. It is complete and explicit, human-readable but easy to convert into self-executable tests.

Tip: A scenario title should describe in a complete sentence what happens in that scenario, to improve readability and indability.

OK: Administrator logs into back-office
BAD: Backoffice login

Tasks

This section is populated by the developer and reports the expected practical activities to meet the requirements. Useful for estimating and for day-by-day monitoring. Better if it reports checkboxes to track completion.

• Task 1
• Task 2
• ...

Notes

• When all players stay at the end, only one (maybe only the master) is kicked from the pool and the other is kick after 2 min (second cycle)
• When kicked cannot longer create game untill refresh

A blue flicker appear on smartphon when clicking on balls or faults

Description of needs

Drafts or UI templates

Acceptance criteria (done when...)

Tip: Write a checkboxed list of sentences in the present tense describing the desired state of the system.

GOOD (clear how to verify, it reports design and interaction decisions
agreed):

• The page shows a button only to logged in users
• The button has the style XXX and label "Logout"
• When pressed, opens a confirmation modal with "OK" and "Cancel" buttons
• ...

BAD (cannot be activated during verification, too arbitrary):

• Logout button
• Modal for confirmation

Validation scenarios

Hint: Use Gherkin syntax to lay them out. It is complete and explicit, human-readable but easy to convert into self-executable tests.

Tip: A scenario title should describe in a complete sentence what happens in that scenario, to improve readability and indability.

OK: Administrator logs into back-office
BAD: Backoffice login

Tasks

This section is populated by the developer and reports the expected practical activities to meet the requirements. Useful for estimating and for day-by-day monitoring. Better if it reports checkboxes to track completion.

• Task 1
• Task 2
• ...

Notes

Develop the possibility to the player to enable/disable ranked

Depends on #37 & #38

• Kick player after 60s the game change status
• Add a button to let the player leave the game

• All player need to join the party at first and make the team
• When the game has start, all player expect one player can disconnect, the game will be managed by the remaining one
• If a player try to rejoin the game, it will be bring back to the initial game
• The game manager need to handle offline player
• #56