zero icon indicating copy to clipboard operation
zero copied to clipboard

Flesh out automated testing

Open bmonkman opened this issue 5 years ago • 2 comments

We have the bare-bones pipeline but there is more work we could do to fill in the testing piece, including

  • examples of good practices around
  • unit testing
  • integration testing
  • smoke testing
  • testing branches
  • best tools, frameworks for each language

bmonkman avatar Aug 19 '20 19:08 bmonkman

Set up a chat with Shane Gearon about this

bmonkman avatar Oct 21 '20 23:10 bmonkman

Some suggestions: unit testing

  • Go: testify, go test. I've personally not used an external library for unit tests in go; so just having a dummy *_test.go file and relying on go test should suffice? go test alone would certainly qualify as a best practice.
  • Node.js: jest, npm test

integration testing I'm not very clear on what integration testing is. Wikipedia says it occurs after unit testing, but before validation testing. I view it as somewhere between unit testing and smoke testing. It should tie components together, but at what granularity?

Would this effectively be the same as the smoke test, but running in the local environment?

smoke testing With Zero we deploy to a staging environment, so having a smoke test that points there and does some trivial assertion should suffice. One question here is where should the smoke test configuration and code live?

testing branches What is this?

GrooveStomp avatar Nov 18 '20 17:11 GrooveStomp