mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #1051] combined assertion tests for tests.integration.user_endpoints.test.test_current_user_save_and_unsave_tracks #627
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#627
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lishukie6588 on GitHub (Dec 7, 2023).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/1051
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.