Skip to content

Improve integration test structure #78

@mdb

Description

@mdb

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions