Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Make successful non-defaulting onCreate integration tests less verbose #2535

Open
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
@mdbooth

Description

We have a great deal of onCreate tests which expect the object to be created exactly as specified without modification. We currently require these tests to specify identical values for initial and expected. In the common case where they are identical, this makes the tests more error-prone to write and validate visually. It would be simpler if it were permitted to omit one of these values if it should be identical to the other.

I recommend that we allow expected to be omitted. If omitted, we default it to the value of initial.

Similarly for onUpdate tests, we could default the value of expected to the value of updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /