Comment 25 for bug 1326653

Revision history for this message
Horia Uifăleanu (horia-uifaleanu) wrote :

I will use D-feet for the quick checks.

Google Test:
In what regards the other tests, a simple scenario testing would be to create a new DBus session to retrieve the info via the DBus interface and compare the results with the values from the singleton PlayerInfo::getCurrentPlayingTrack.
This approach might be suitable for unit tests as well.

MPRIS 2.2 standard:
I will start with the entries for the current playing track but basically, on long term, I would like to go on with all the items specified by MPRIS 2.2