Hi, For me, it seems there's two separate use cases. The first use case is to download original xml attachments, e.g., to inspect test steps, stdout/stderr and other information that is not (yet) visible in QA Reports UI. In this scenario, it would be confusing to update for example test result from fail to pass, if there's error message in stderr field.
I guess the use case Shao-Feng is describing is something like this: "As a [test engineer | test manager | someone else] I want to download test result as a csv in order to [ do further analysis in excel | to update/upload report | something else]". In such case, it would of course make sense to have the current results, not the original. Shao-Feng, could you clarify who (which role) wants to download the results and what she/he wants to do with them? Would they prefer result.xml format or some csv format? Could you also create a ticket for the issue, as it seems to be different from the original request. Best, Jarno > Date: Mon, 4 Apr 2011 19:54:38 +0300 > From: Poikaj?rvi Vesa <vesa.poikaja...@digia.com> > To: "Tang, Shaofeng" <shaofeng.t...@intel.com>, > "meego-qa@lists.meego.com" <meego-qa@lists.meego.com> > Subject: Re: [Meego-qa] [Qa-report]Regarding the Proposal for allowing > download of raw result files > Message-ID: > <94a88214e67edf4aa1f1ced7d26833a8301fd9d...@e2k7mail.it.local> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > > Not sure if you also received the feedback from Tina, Daniel, and Lei > > about this feature. Maybe you know, they also the end user of qa-reports. > > And all of them also insist the result files should be updated for > > keeping consistent with the database. > > Yes, I got them - I was just trying to point out that we're not talking > about the same thing: > > 1. The request I received was: > > As a user, I want to *download* the *original* result files I used when > creating the report since I want to check the details; > > 2. Whereas you want: > > As a user, I want to be able to *export* test results as XML once all > the results are in place etc. for some reason. > > >From the first request there's now a FEA request and also a proposal for > implementation. For that 2nd one there's discussion on this mailing list > but > no request in Bugzilla. > > Both can be done - these are not ruling each other out. You sent a link to > a bug about CSV export, shouldn't be too hard to add XML export as well > while > someone is already implementing this. These things are just conceptually > different even if both are about getting some stuff in XML format from QA > reports. For the first one the requirement is to get the *original* files, > not some files that have been updated based on some information in the > database. > > > Regarding the feature#14876, I think the original result file didn't > > match this feature at all. Especially making nonsense if the result > > file contain several thousand test-cases(In our full-path testing, > > more than 3 thousands test cases are involved.) Maybe a pop-up window > > or page could be used to show the output of the selected testcase. > > Instead of providing the result file. > > I'm sorry I don't get this - the feature request above is not related to > downloading (or exporting) files; it's about adding information to the > report (as a popup, hidden div, whatever) so that users could check the > output > of steps of a certain case *without* needing to download any files. So this > would be: > > As a user, I want to quickly be able to check stdout, stderr, return > value > and some other stuff for a single test case without needing to download > the XML files. > > > BR, > Vesa Poikaj?rvi >
_______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
