> > {{result|pass|adamwill|TC1}}
> > {{result|fail|adamwill|TC1|123456}}
> > {{result|fail|adamwill|TC1|123456|111222}}
> >
> > I think that's no less readable than the original schema.
>
> It isn't at all, but it has the rather large problem that it breaks the
> API :) All existing {{result}} entries in all pages will be invalid.
> That seems like a deal-breaker. We're kind of locked forever into the
> first five fields being 'result', 'username', 'bug#', 'bug#', 'bug#', I
> think, to preserve existing results.
Ah, right. So, the solutions could be:
a) name the template differently, e.g. {{test}}, {{testcase}}, {{testresult}}, {{result2}}
b) write a script to convert all pages using {{result}}
a) is easier than b), but more inconvenient. Both should be doable.
What I don't like, however, is that I'd like to avoid displaying names for TC results (because we will be aggregating many results and it would be too space consuming), but display them for RC results (because we won't be aggregating results and often it's helpful to easily see who tested what - without using tooltips). But it would be a bit stupid to have two different templates for that (even though {{tc}} and {{rc}} could be quite memorable and of course they are pre-filled), and I don't know how to achieve that using the same template. I don't have an answer here.
> > My only concern is that things would get out of hand and the tables
> > would start to grow a lot. But in that case we can either prune it by
> > hand when needed, or refresh the whole page (for example we have a
> > single page for TC1/TC2/TC3, then there's a lot of results, so we
> > create a fresh new page for TC4-TCx. Rinse and repeat). In this case
> > it would still be relatively easy to spot test cases which were not
> > tested in a long time, because you would have approximately just one
> > historical page (going not too far into history) to check and compare
> > to the current one, which is manageable (if the current page is for
> > TC4-TC5, and I can see results for TC1-TC3 summarized on a single
> > historic page, I can then easily compare blank cells).
>
> I guess another problem here is it makes the process somewhat more
> complex; right now we have a fairly simple SOP for doing a test release
> event, which is 'create the results pages and send out the mails'. I
> guess it becomes 'decide whether to create a new results page, if so
> name it according to this new naming scheme'. Not that bad, I guess, but
> a bit more work. How did you envisage naming the pages?
Yeah, this would require some good ideas and the instructions to set up a new page would get a bit more complicated.
I wonder if this could be an interesting idea:
1. Set up "Test Results:Fedora 21 Alpha TC Install" and point "Test Results:Current Installation Test" to it
2. Use it until it grows too large (e.g. TC1-TC3)
3. Copy the contents into "Test Results:Fedora 21 Alpha TC1-TC3 Install" and replace "Test Results:Fedora 21 Alpha TC Install" contents with a fresh template (i.e. cleaning up all results)
4. Goto #2 or until RC is reached
The benefit is that we don't have to update "Test Results:Current Installation Test" during the whole TC process, and the process is quite easy to remember. The "Test Results:Fedora 21 Alpha TC Install" page would contain a full testing history (accessible in through wiki history), which might be considered advantage or disadvantage.
>
> (it also means you can't reliably find the correct results page by just
> plugging the appropriate fields into the known format, I guess, unless
> we're careful about setting up redirects.)
I assume we would still use categories, and would place the link prominently to the top of the "Test Results:Fedora 21 Alpha TC Install" page, so it would be easy to display and navigate through the previous results pages. But yes, you wouldn't be able to directly access pages from your address bar by just knowing the syntax.
If we used a different approach than categories (for example just links on a page named "Test Results:Fedora 21 Summary", we wouldn't even need to create pages like "Test Results:Fedora 21 Alpha TC1-TC3 Install". We would just link to a certain point in history. Which also seems quite usable.
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
