Bug 26278 - regression test for calls from XMPP
Summary: regression test for calls from XMPP
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: fargo (show other bugs)
Version: git master
Hardware: Other All
: high enhancement
Assignee: Simon McVittie
QA Contact: David Laban
URL: http://git.collabora.co.uk/?p=user/sm...
Whiteboard: milestone4.4 done=9h est=9h
Keywords: patch
Depends on:
Blocks: 26097
  Show dependency tree / graph
 
Reported: 2010-01-27 09:29 UTC by Simon McVittie
Modified: 2010-02-01 08:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2010-01-27 09:29:10 UTC 
There's no regression test for calls from XMPP yet.
Comment 1 Simon McVittie 2010-01-27 11:19:30 UTC 
Ready for review but missing some coverage.
Comment 2 Simon McVittie 2010-01-27 11:48:48 UTC 
Test merged and is no longer blocking other work, but should still be extended to cover:

* codecs with nonzero number of channels

* codecs with parameters

* needing to ignore video codecs

* should the initiator be the bare or full JID? Currently it's the bare JID and
we assert that

* from-xmpp.py doesn't assert that the candidates have the right ports,
components

* from-xmpp.py doesn't assert whether the session-accept has any candidates;
should it?

* from-xmpp.py doesn't assert that the PTs in session-accept match the intended
PTs
Comment 3 Simon McVittie 2010-01-28 10:30:09 UTC 
I'll work on this more tomorrow.
Comment 4 Simon McVittie 2010-01-29 10:28:08 UTC 
Improved coverage, coverage stats, misc compliance fixes in <http://git.collabora.co.uk/?p=user/smcv/telepathy-fargo.git;a=shortlog;h=refs/heads/cov>.
Comment 5 Simon McVittie 2010-02-01 04:56:37 UTC 
Branch updated; took longer than the 8h estimate due to some bugs + fixes along the way.
Comment 6 Simon McVittie 2010-02-01 08:19:18 UTC 
Fixed in git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.