Comment 8 for bug 548824

Bryce Harrington [2010-05-19 18:04 -0000]:
> Hi Martin, thanks for the clarification! I had assumed you were looking
> to move from use of the web interface to using launchpadlib calls

Not for the blob uploading, just for the bug filing. Or alternatively,
get a more robust way of using the +filebug page from a program (or,
any way that works at all at the moment..)

> We're still a bit unclear on this bug. Could you explain what exactly
> you're wanting to test here? I.e. are you testing that launchpad
> actually receives the data blob?

That, plus that it decodes the blob correctly, sets the right
subscribers and privacy status, etc. This is meant to become a part
of Launchpad's test suite for "important customers", as requested by
Diogo. I. e. we want to test that apport and launchpad have a working
interface to each other.

> We're wondering if we can just rely on launchpad's own tests to
> ensure the pages themselves are working correctly

If LP already has tests for blob uploading, decoding, and bug
attaching, then that's certainly sufficient.

> and just focus on testing the specific apport needs themselves.

I also use the test suite for apport's launchpad backend itself, to
both test new features, make sure that the existing ones keep working
through launchpad changes, and test my workarounds for Launchpad
bugs/crashes (of which we had and have plenty). For these tests I need
some "synthetic" bug reports which I can mess with during the tests.