Better local saving and review of results

Bug #305111 reported by Henrik Nilsen Omma
18
Affects Status Importance Assigned to Milestone
Checkbox
Won't Fix
Medium
Unassigned

Bug Description

The checkbox user should be able to save and review results locally as a natural part of the workflow. The last screen on checkbox should be something like:

Testing complete!

[View results] [Save results] [Submit results]

You would be able to click on any of the buttons in turn, so you could save the results locally first, then click review to see a local display of them and finally submit them.

Ideally, the user experience should be the same for checkbox and checkbox-compatibility except that c-c uploads the results to certify-web instead of LP. For the public checkbox client we are planning to add and XSLT to the XML file so that it can be viewed locally, saved and attached to bug reports and later viewed cleanly on-line.

My understanding is that c-c does not use XML but instead bpickle to transmit the results. Should we a) export an XML file from c-c used for local viewing or b) migrate from bpickle to XML to reduce the delta?

With a) we introduce a bit of confusion with having to save two types of files locally - an XML file for simple review and attachment and a bpickle file for official upload while with option b) we need to modify the result parsing on certify-web and will lose any advantages bpickle may have.

If we can connect the bpickle and XML files in an intuitive way (like a unique ID in the filename) then option a) might be fine. Normal users would only get the XML file while customers would also get the bpickle file that could be uploaded - otherwise the experience would be identical. The bpickle file contains the secure ID, which the XML doesn't and perhaps in the future some signature to discourage tampering with results.

Changed in checkbox:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
David Murphy (schwuk) wrote :

We could extend the c-c interface to *optionally* upload hardware information *only* to Launchpad (with appropriate disclaimers about visibility etc.).

With regards to migrating c-c to xml, this is unnecessary - the viewable report can be based on the internal data representation without any changes to the submission format used.

David Murphy (schwuk)
Changed in checkbox:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.