On Tue, Jul 13, 2010 at 12:33 PM, Foster, Dawn M <[email protected]>wrote:

> On Jul 13, 2010, at 9:13 AM, Dave Neary wrote:
>
> >
> > I would suggest creating a "Testing team" page which could be used to
> > collect report templates, document the testing team and its processes,
> > and also collect all the test reports. Something like
> >
> > Testing team
> > Testing team/Test report template
> ...
>
> We should probably use Quality Assurance or QA instead of testing team to
> keep things consistent with the naming of teams on the governance page:
> http://meego.com/about/governance/quality-assurance
>
> >
> > etc....
> >
> > In general, if the testing team are going to be generating weekly test
> > reports, then unless there is historical interest in keeping old test
> > reports around, I would suggest that they be archived somewhere, and
> > that only the latest test reports (and, perhaps, the last test results
> > from a release to compare for regressions) be kept around.
> >
>
> This is a very good suggestion. Keep in mind that since the wiki keeps a
> history of previous edits, you might be able to keep your reports grouped on
> a single page. Here's an example:
>
> Title: QA/Core testing reports
> Subheadings for each week's report: Core testing report 20100709
> You could keep the most recent  5 reports on that page, and just delete the
> older ones from the page. The "deleted" content would still exist in the
> history for viewing.
>
> The you would have fewer pages, and it would be easier to find the
> information.
>

Whoever admins the mediawiki install may want to have a look at:
http://www.mediawiki.org/wiki/Subpages

We use subpages on http://www.elinux.org and they can be quite useful.

Categories are equally useful though if used effectively.

If I can help in anyway with the wiki admin, feel free to let me know.


> Regards,
> Dawn
>
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to