Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semi-automated game log testing #1039

Open
cxong opened this issue Jul 7, 2016 · 3 comments
Open

Semi-automated game log testing #1039

cxong opened this issue Jul 7, 2016 · 3 comments
Labels
coding This issue requires some programming pipeline Affects how the project is being developed

Comments

@cxong
Copy link
Contributor

cxong commented Jul 7, 2016

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:

  1. Start normal 2v2 game
  2. Play game log: spawn creatures, creature 1 attacks creature 2
  3. 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

What we need:

@cxong cxong added the coding This issue requires some programming label Jul 7, 2016
@DreadKnight DreadKnight added the pipeline Affects how the project is being developed label Jul 7, 2016
@DreadKnight
Copy link
Member

DreadKnight commented Jul 8, 2016

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.

@DreadKnight
Copy link
Member

That #1036 issue was fixed a while ago, it helps out a bit :)

@DreadKnight DreadKnight added this to the 0.5 - Chimera milestone Oct 13, 2017
@DreadKnight
Copy link
Member

Testing suite, might come in handy https://www.cypress.io

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coding This issue requires some programming pipeline Affects how the project is being developed
Projects
None yet
Development

No branches or pull requests

2 participants