Early in a project, test cases are created and bugs are revealed. Usual stuff right? Fast forward to project completion and now we are doing regression testing.
Looking through the test library, I have an example of a test that was created as a result of bad coding in early dev. This is an example for setting up a notification and checking that the password value is not lost.
Background: Given bob is a registered user Scenario: Setting up notification should not lose the password Given I am logged in as bob And I set up a notification Then I should see my password is still in the db And I should not see a blank field in the db
Cringe, I know this is not the proper use of Gherkin.
This has already been fixed back in the early phases of the project. There is little value to retest them because the code base has been established.
- Would it be a good idea to only test these once and never again?
- If I could go back in time, is there even any point to write this test case since they will only be tested once?
Maybe it’s just a case of tagging this kinds of tests as a one-off. Any of you had this experience?