[Libreoffice-qa] Extensive docx conversion tests...

[Robinson Tryon]

On Mon, Apr 21, 2014 at 8:51 PM, Jay Philips <philipz85 at hotmail.com> wrote:
> Hi Robinson,
>
> Thanks for cc'ing me as i wasnt part of the list but have sent in a request
> to be part of it.

:-)

If you run into any problems, just ping me, and we'll do our best to
get it straightened out.

> I report most of the bugs on my twitter account <
> https://twitter.com/jphilipz/ > as i'm also testing kingsoft writer and
> calligra works, but after i complete the tests, i take all the tweets and
> put them into a text file and then .zip it along with all the test documents
> created during the test, and i place them at a public url for interested
> parties to have access to. As this is my current work flow, its difficult to
> make individual bug reports for each individual problem that occurs during
> the testing, but i will try to submit more.

Individual bug reports are best as bite-sized pieces for us, but we'll
do our best to work with anything that you submit. Because we have to
make the most of our QA and Dev time, the easier it is for us to repro
your results, and the faster we can get a Dev up to speed on the
precise details, the more bugs we can identify and squash each day :-)

> If i were permitted, i would
> like to send into the list a more customized test result .zip file just of
> libreoffice bugs, which would contain the related tweets (along with its
> related bug reports i've sent in), created test documents, and images of the
> errors. With this, i'm assuming it would be easy for the devs to create the
> necessary bugs reports with.

Generally speaking, the devs don't have time to create bug reports.
Right now QA has a backlog of 1100+ Unconfirmed bug reports, so we
have only limited time to create new bug reports ourselves. But if you
can create a formatted data file that contains tuples of
(Document/Document URL, What's wrong, Repro steps), we might be able
to find the time to turn those into bug reports.

If there's anything in particular we can do to make it easier for you
to submit bug reports, let me know. Because you're doing the original
testing, it's most helpful for us to have you listed as the reporter
in Bugzilla so that the QA Team and the devs can ping you with any
follow-up q's regarding the precise problems you're encountering, and
you can provide feedback on whether a proposed fix has actually
resolved the problems that you're seeing on your system.

>
> I look forward working with you and the QA team.

Hooray!

--R

-- 
Robinson Tryon
LibreOffice Community Outreach Herald
Senior QA Rodeo Clown
The Document Foundation
qubit at libreoffice.org