[Bug 55666] New: only monitors SelfHandleChanged if the CM is obsolete

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Oct 5 17:10:30 CEST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=55666

          Priority: medium
            Bug ID: 55666
          Keywords: patch
                CC: guillaume.desmottes at collabora.co.uk,
                    jonny.lamb at collabora.co.uk, xclaesse at gmail.com
          Assignee: simon.mcvittie at collabora.co.uk
           Summary: only monitors SelfHandleChanged if the CM is obsolete
        QA Contact: telepathy-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: simon.mcvittie at collabora.co.uk
          Hardware: Other
            Status: ASSIGNED
           Version: unspecified
         Component: tp-glib
           Product: Telepathy

I was refactoring Aliasing in MC (bug forthcoming) as a follow-up to Bug
#55391. Then I noticed MC made no attempt to track the self-handle changing,
which is clearly wrong for at least Idle (assuming Idle even implements
SelfHandleChanged, which it might not: Bug #17332). Then I fixed that, wrote a
regression test, and discovered it failed because telepathy-glib doesn't
respond to the signal being emitted...

This turns out to be because the regression test emulates an old CM, because it
hooks GetSelfHandle so it can trigger a particular corner-case; and that's a
problem when emulating a newer CM because it's harder to hook GetAll. So to
test this properly, we have to expose the mixin's GetAll() implementation to CM
code. Additional yak-shaving.

When porting to 'next' we just deleted that test, which is ... not really the
right approach.

How we test this depends which branch(es) we want to get the tests into.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.



More information about the telepathy-bugs mailing list