...
Moving manual test cases to Dead
After analyzing the test steps contained in the functional test and those in the test case(s) on which the former were based, and determining that they match, the tester should move the latter to Dead and write a comment in the ticket with the test case that it was moved to Dead because a functional test covering the feature that the manual test was verifying had been created, including a link to the automated test in it. One also has to link the ticket with the test case to the one concerning the creation of the automated test. If the test case that was moved to Dead contains the CoreRegression label, one should remove it, so that the test cases that are no longer valid do not appear in test cycles concerning regular or release candidate regression testing, causing confusion.
Having moved the test case(s) on which the functional test was based to Dead, the tester should browse through the test cases concerning the same component in order to check whether any other manual tests can also be moved to Dead or whether some steps contained in them can be deleted, as they are now covered by the automated test. Sometimes, it is possible to delete test steps in other test cases than the one on which the functional test had been based, as some of them concern very frequent actions, such as e.g. requisition approval. Of course, the test steps can only be removed if the test case will still make sense after their removal. If not, the steps should be kept as they are, despite them being covered by a functional test.
...