loading...

Discussion on: From TDD to DDD: Building a .NET Core Web API - Part 7

blenderfreaky profile image
blenderfreaky

What about making the test "invertible", by adding a bool parameter which will swap failure and success around if set to true? That way the test would still exist and be green

Thread Thread
lucianopereira86 profile image
LUCIANO DE SOUSA PEREIRA Author

good idea.
I've made something similar but using enum.

Thread Thread
hidegh profile image
balazs HIDEGHETY

to make it clear, have separate SUCCESS and FAIL test is a good thing, like:

  • expect that all users with names less than 20 chars to be accepted
  • expect all users with names more than 20 chars to be rejected (rejection is accepted so it's our GREEN indicator).

best to do one test per fact, e.g. test the 20 char limit, test if there's at least a special char in the password and have multiple values for that test that should pass.

same way give multiple values for the test where the failing condition is tested, e.g.:
fact_password_without_special_chars_should_be_rejected