We must modify our existing E2E tests for Delete User to include these new scenarios; the end result may look something like this:
Feature: Delete User by ID Clients should be able to send a request to our API in order to delete a user. Background: Create two Users and logs in with the first user's account Given 2 new users are created with random password and email And the client creates a POST request to /login And attaches a valid Login payload And sends the request And saves the response text in the context under token Scenario Outline: Wrong Authorization Header Scheme When the client creates a DELETE request to /users/:userId And set the HTTP header field "Authorization" to "<header>" And sends the request Then ...
