Test page for workshops and installations

[juliendorra]

"il nous faudra une url avec une page de test avec 10 créatures et le sketch de fond pour envoyer à l'équipe de la gaité, pour qu'a minima il vérifie que ça charge, s'anime"
" dans /public/workshop/360/test/ une page paysage statique dédiée qui charge localement un .pde au lieu de les charger depuis le serveur. Elle sera accessible à paysage.xyz/workshop/360/test/"
"une page de test de performance. Je suggère de mettre un <input type=range> dessus pour faire varier le nombre de créatures"
"pas la peine de mettre 11 pde différents, une créature de complexité moyenne répétée N fois suffira"

[Anna-Livia]

When testing with Elsa of AMTDP, we had a test protocol :

• Person A creates a Playground
• The editor is displayed on Person A's screen
• Person A generates a creature
• When clicking on a creature the code appears in Person A's the code editor
• When clicking on go live the creature appears on Person A's screen
• Person B enters the same Paysage
• The editor is displayed on Person B's computer
• The creature created by person A is moving on Person B's computer
• Person B generates a creature
• When clicking on a creature the code appears in Person A's the code editor
• When clicking on go live the creature appears on Person A's screen
• Person A and Person B both see the two creatures on their computer

Another way to test would be to check the frame rate.

[jonathanperret]

@Anna-Livia I only just now saw your comment. You describe an good test script for verifying the behaviour of Paysage's code — since then we have automated some of this testing, e.g. in https://github.com/jonathanperret/paysage/blob/633ea6fba3ed04afa18f05068bf3f1a5e7f61d76/e2etests/tests/test.js).

But this issue is more about checking the environment for a workshop that is to use Paysage: does the network work? Do the rendering machines have enough power? Is the multi-screen layout correct? etc.