I keep writing these one-off when I actually use tea. It seems like it's
worth including. It's especially useful for the root test, where you
don't necessarily want to create a test, but want to create a starting
environment. Exporting a type that always passes is preferrable to
making an explicit environment type, since we can maintain our
guarantees that our environment isn't an invalid value.
adding a nested Go modules file because I don't want to update tea's
go.mod file when the examples are run. I don't want to accidentally
check them in.
the env type represents a test environment. This was added as an
intermediate container that could store the saved fields of tests after
they're run, so that future tests could load them. Previously a test
could only get the attributes of the test that immediately preceded it.
This change allows tests to load attributes further back in the history.
this isn't going to work permanently, if there's a save field in one
test, then an intermediate test without that field, then a load field,
it won't be visible at the end test.
