You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up from #997 (comment), allow testing via a web browser automation tool (i.e. selenium), which starts the game with certain settings #1036, plays a gamelog, then checks the status of the game. For example:
Start normal 2v2 game
Play game log: spawn creatures, creature 1 attacks creature 2
Check conditions: creature 2 health should be x
What we get:
Test suite to guard against regressions: run test suite, see whether abilities are broken
TDD: write the tests first, write code second. This also helps designers/developers communicate, i.e. the developer knows exactly what the designer wants some ability to do.
Easier reviews: no need for manual testing/verification, just run the tests; it's also easier to see if there's a test condition missing
Since the game has a replayable log, Selenium might not be really needed, as it's more meant for websites and apps that don't have such a feature. Instead we could add some command / hokey to the game that would start automated testing, so the whole browser thing could be avoided / optional. Results could be automatically submitted to a database. If we really want something downloadable, we could aim for #158.
Following up from #997 (comment), allow testing via a web browser automation tool (i.e. selenium), which starts the game with certain settings #1036, plays a
gamelog
, then checks the status of the game. For example:What we get:
What we need:
G.creatures.get("Gumble", "player1").stats.health === 123
, I haven't checkedThe text was updated successfully, but these errors were encountered: