When performing integration test, the mentioned test performs assertion calls to 2 separate user endpoint functions at 2 separate points, resulting in an inconclusive assertion test result for the latter current_user_saved_tracks_delete method in the situation that the first assertion call fails after calling the current_user_saved_tracks_add method.

Specifically, as shown in the following screenshot of the unit test in the provided
test suite, you can see the unit test containing the 2 assertion calls in lines 285
and 291 below each time the 2 tested API endpoints were supposed to be called.

However, as shown in the following screenshot of the test results, only the
assertion call in line 285 was called and the one in line 291 was aborted and left
inconclusive due to the triggered false response of the first one.