Currently, the integration tests lack an intuitive structure. There's also no clear technique for establishing a pattern through which dependency values can be shared through the tests, but limited to an intended scope. For example, it could be worth sharing the ID of a created record set -- from a test of RecordSetCreate -- with a test of RecordSetUpdate and RecordSetDelete in an intuitive, well-organized way. Could something like ginkgo help establish that structure through Contexts, BeforeEachs, and scope?
Currently, the integration tests lack an intuitive structure. There's also no clear technique for establishing a pattern through which dependency values can be shared through the tests, but limited to an intended scope. For example, it could be worth sharing the ID of a created record set -- from a test of
RecordSetCreate-- with a test ofRecordSetUpdateandRecordSetDeletein an intuitive, well-organized way. Could something like ginkgo help establish that structure throughContexts,BeforeEachs, and scope?