checking for 404 is flaky; depends on deletion succeeding

services/spar/test-integration/Test/Spar/Scim/UserSpec.hs

@@ -519,7 +519,7 @@ specDeleteUser = do
                 !!! const 405 === statusCode
 
     describe "DELETE /Users/:id" $ do
-        it "when called twice, should first delete then 404 you" $ do
+        it "should respond with 204" $ do
             (tok, _) <- registerIdPAndScimToken
             user <- randomScimUser
             storedUser <- createUser tok user
@@ -528,8 +528,6 @@ specDeleteUser = do
             spar <- view teSpar
             deleteUser_ (Just tok) (Just uid) spar
                 !!! const 204 === statusCode
-            deleteUser_ (Just tok) (Just uid) spar
-                !!! const 404 === statusCode  -- https://tools.ietf.org/html/rfc7644#section-3.6
 
         -- FUTUREWORK: hscim has the the following test.  we should probably go through all
         -- `delete` tests and see if they can move to hscim or are already included there.