Test Flows

[crisszkutnik]

Test flows

A likear:
OLL: Awkward3, C2, Dot1

Not logged

• Enter to Cubitorium
• Check Guide
• Read algorithms
• Visit a user profile
• Go to Practice
  • Select None
  • Select a few cases
  • Show how Practice is meant to be used
  • Pretend you forget a case and read from left panel
    • Go to "view case"
    • See other solutions that there exist
  • Go back to practice
  • Practice a bit more
  • Show statistics, delete performances, etc.
• The user is THIRSTY for more. So they connect their wallet

Logged

Similar to not logged

• Go to algorithms page, show that now we have Like
• Like a solution
• Change learning status
• Like a few solutions and set status to "Learning"
• Go to "My liked solutions" and see that we can view all those
• Go to Practice and "Select Learning"
• Briefly show that one can do the same and why it's handy to have this feature
• Go to "View case" on the last case, nos da el pie para lo que sigue:

Adding solutions

• User sees that a good solution is missing
• Click "Add" and show that we can add a solution
  • It shows the cube updating LIVE
  • Submit a solution that doesn't work and have it rejected
  • Submit a solution that is repeated and have it rejected
  • Submit a working solution
  • Explain what is going on. Show logs.
  • Show the funding
    • Set maxFundLimit to 0
    • Show that the user balance is affected (through solana balance or Phantom wallet)
    • Set maxFundLimit to a greater value (1000000000000)
    • Show that the user balance is only affected by 1000 lamports (tx cost)
• Show the same cycle, briefly, from the Algorithms page
• Go to "My solutions" and show that we can see what we submitted

Liking solutions

• Switch to a different wallet
• Like the solution we submitted a moment ago
• Go back to the previous wallet
• Show that we have a Like now. Our own likes don't count towards ourselves (we can either show that or not idc)
• Explain that this can be queried from anywhere, publicly, for free. Show how it is persisted in the blockchain (anchor shell + fetch the PDA).
• Show the user profile and update some stuff

Admin

• Try to add a case that doesn't exist, show that it fails
• Add a new algorithm set
• Try it again and it will work
• Explain the purpose (doesn't limit the sets to something hardcoded or unmodifiable). Any admin can add new sets of stuff. Admins should be trustworthy members of the cubing community.
• Show that we can add a new admin
  • Switch to the other wallet
  • Show that we can't see the admin panel
  • Go back to the admin wallet
  • Add privilege
  • Show that now the previous account can see that stuff

Si falta algo agreguen

[GuidoDipietro]

bueno ahi abri 6 issues

[GuidoDipietro]

bueno ahi abri 12 issues mas

[GuidoDipietro]

ahi van unos pares de flujos

[crisszkutnik]

como mierda editaste mi propio comentario

[GuidoDipietro]

facil te hackee y listo

[crisszkutnik]

pepepepe

Test flows

Set up inicial requerido

• Tener en un navegador A una wallet que sea admin y tenga plata
• Tener un navegador B con otra wallet que no sea admin y tenga plata
• Tener los logs del programa prendidos
• Haber corrido script de carga de datos
• Tener pre likeados soluciones de diferentes sets

---

En presentacion

• Explicar puzzles y sets @GuidoDipietro @AgustinVillarreal

A likear:
Awkward3, C2, Dot1

Not logged user (Mati)

• Enter to Cubitorium
• Check Guide
• Read algorithms
• Visit a user profile
• Go to Practice
  • Select a few cases
  • Show how Practice is meant to be used
  • Show statistics, delete performances, etc.
  • Pretend you forget a case and read from left panel -> You don't know how to solve
    • Stop timer
    • Click "view case" in left panel
    • See the solutions that exist
    • Go back
  • Go to Home
• The user is THIRSTY for more. So they connect their wallet

Logged

Adding solutions (Guido En)

• Go to Algorithms page
• Goes to case x -> @GuidoDipietro
• User sees that a good solution is missing
• Click "Add" and show that we can add a solution
  • It shows the cube updating LIVE
  • Submit a solution that doesn't work and have it rejected -> Dejar solucion aca @GuidoDipietro
  • Submit a solution that is repeated and have it rejected -> @GuidoDipietro
  • Submit a working solution -> @GuidoDipietro
• Go to Home
• Show that you can go to "Upload your Algorithms" page directly without going through the "Algorithms" page
• Go to "My solutions" and show that we can see what we submitted
• Go to Home

Like solutions (Cris)

• Go to algorithms page, show that now we have Like
• Like a solution
  • OLL: Awkward3, C2, Dot1
• Change learning status
• Like a few solutions and set status to "Learning"
• Mention why there is a dialog that groups transactions
• Go to "My liked solutions" and see that we can view all those
• Go to Practice and "Select Learning"
• Explain why this feature is handy
• Go to Home

Change user and check permissions (Cris)

• Switch to not admin user browser

• Go to user profile and show it has no data

• Quickly change user info

• Show updated user profile

• Go back to admin browser

• Show that we can add a new admin

  • Add privilege

• Go back to not admin browser

• Reload page

• Show that it can now access "Admin panel"

Admin (Nombrar solamente)

• Try to add a case that doesn't exist, show that it fails
• Add a new algorithm set
• Try it again and it will work
• Explain the purpose (doesn't limit the sets to something hardcoded or unmodifiable). Any admin can add new sets of stuff. Admins should be trustworthy members of the cubing community.

Logs

• Mencionar el treasury y que en la blockchain las transacciones y guardar cosas vale plata @GuidoDipietro
• Mostrar compresion a arbol de Huffman
• Mostrar que el treasury devuelve guita

[GuidoDipietro]

Miren loko obtuvimos un 10