You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2021. It is now read-only.
Just a todo thread for test cases. This has been bugging me for a while. We can't even do some functional testing because of highly superimposed components. I think integration testing can be done but have to figure out a way to do this properly.
Few tests we can do are:
crawl, and download songs (this can be done by temporarily downloading songs and deleting them)
can create a temporary test cache dir like ~/.playx-test where we could perform a few checks
Playlist checks can be functionally tested. We could try fetching list of song names.
The text was updated successfully, but these errors were encountered:
I think we can have like a dry run, in which case all the fetching and everything is done just that the songs are not played.
We can also add some fixed URL's for each parser that the parser will try to parse when we run the tests and we will get the results. For the time being it seems like that would be the easiest way to go?
Just a todo thread for test cases. This has been bugging me for a while. We can't even do some functional testing because of highly superimposed components. I think integration testing can be done but have to figure out a way to do this properly.
Few tests we can do are:
The text was updated successfully, but these errors were encountered: