Skip to content

Instantly share code, notes, and snippets.

@asvae

asvae/suggest-node-testing.md

Created August 6, 2017 11:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save asvae/bd00e254114c2bb189386cb5937cc231 to your computer and use it in GitHub Desktop.
Save asvae/bd00e254114c2bb189386cb5937cc231 to your computer and use it in GitHub Desktop.
Download ZIP
Suggesting node testing
Raw
suggest-node-testing.md

We suggest to use node.js for api integration tests.

Upsides

  • Code sharing between frontend and testers (Entity (sctructure + bound logic), Factory, Mapper).
  • Filling the test-coverage gap between backend and frontend. Currently this is the most untested and dangerous part.
  • Node is better than php to work with dynamic data structures.
  • Making frontend guys happy as our burden will be lightened.

Downsides

  • Testers should have to learn JS. Though tests don't pose much a difficulty.
  • Tests should be written. Reuse is around 70% of what testers need. 30% is integration tests specific.
  • Node is more resource intensive that phpunit. (negligible)
  • Stressing out backend team :P.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment