search

Innablr / revolver

AWS Powercycle Facility
MIT License
2 stars 3 forks source link

Local automated integration testing #122

Open alutman-innablr opened 5 months ago

alutman-innablr commented 5 months ago

With

we could automated integration testing and ensure a baseline minimum functionality of the program for each push.

  1. Run a minified build
  2. Copy invoke.js to the minified build dir
  3. Generate JSON of resources using zod with a predictable result. Produce a list of expected actions.
  4. TODO set revolver to a specific time
  5. Run a local execution of the generated resources and compare the action result to the expected.

This will shake out almost all issues except for AWS API calls and auth (we'd still set up a real e2e test in an environment but that would be on pre-release). Should also be very fast.

Related to: https://github.com/Innablr/revolver/issues/35

simon-anz commented 5 months ago

Why zod for resources? Why not just grab them from API for real, sanitise them, and commit them as json?

lyricnz commented 1 month ago

Just had a bug that lingered in develop for a couple of weeks because it wasn't functionally tested. https://github.com/Innablr/revolver/pull/342

Having some automated integration testing would have identified this earlier, maybe even pre-merge.