EZ Integration Tests

[tzaffi]

WIP

Related PR's at various stages of WIP'ness:

• go-algorand
  • Its ezTraces_test.go generates the disassemble.json fixture that is gonna end up in this PR.
• js-algorand-sdk

Random Thoughts

• Shouldn't we also automatically test paths?
  • In the disassemble example there is no difference between path and route. However, all the SDK's support introspecting path via a dedicated method, and the go rest client tracer ought to be able to spot this as well
  • This may obviate one sort of unit test that we always set up.
• The POST portion of any such test, could be understood to be the setup for the READONLY GET portion. A test in indexer could pick up where the rest-client left off, and modify the fixture to include indexer queries at the end.
• There is an SDK transaction creation unit tests with a "golden" containing the encoded signed transaction to be sent.
  • Could such a unit test be fixturized as well? Maybe not in an integration test, as absolute determinism may be required to generate the same transaction each time? Or maybe the transaction details could be asserted against instead?

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ tzaffi
❌ Zeph Grunschlag

---

Zeph Grunschlag seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}