Testing: best practices
Jorge Bellon-Castro <[email protected]> Sat, 11 Jan 2025 13:19:42 +0000
| Newsgroups | gmane.comp.video.videolan.vlc.devel |
|---|---|
| Message-ID | <CAHj0YyDfvTpfqHQFrZ=1RupPjmCJVNF6sRv75873htgfMMpssw@mail.gmail.com> |
Good afternoon, I submitted a few bug fixes and extensions to the dbus control module in the past. One thing I noticed is that there is no integration testing for this. Even if this is not interesting for the VLC project specifically (in which case I would not submit any merge request), I think it could be handy for me to have some sort of small tests that validate my current and specially future changes. I am looking for some good practices to implement a few test cases. Some of the basic things I will need to do is to queue media to play and inspect the tracklist. I found there are two ways test queue media to be played: some tests use files in the sample directory and others use the "mock://" uri scheme. Are there any advantages of using one over the other? My plan was to use dbus-launch to have a dbus daemon process local to a specific test. Thanks in advance for any tips. Jorge _______________________________________________ vlc-devel mailing list To unsubscribe or modify your subscription options: https://mailman.videolan.org/listinfo/vlc-devel