Skip to content

Empty values in test databases cause test failures, what to do? #6

@jasper-lyons

Description

@jasper-lyons

So we throw an error when there are not values in the db or defaults for content_keys. Dev's could just provide default values for everything (potentially good practice) but it feels a bit to boiler plate?

The other option is to just turn off that when in the test environment?

Or obviously to hide it behind a config value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions