[rdo-list] Improving the test day experience

[Adam Huffman]

Hi Harry,

Where ought I to report bugs found in testing those docs?

Cheers,
Adam

On 21 Sep 2016 6:55 pm, "Harry Rybacki" <hrybacki at redhat.com> wrote:

> I would also like to throw out that we are in the process of expanding
> coverage for TripleO-Quickstart post-build generated documentation.
>
> For the last test day, we had three sets of example docs available[1]:
>  - minimal
>  - baremetal
>  - ovb
>
> Hopefully there will be docs for updates and upgrades to follow
> shortly. As discussed with rbowen in today's RDO meeting, we will have
> these docs linked in the test matrix for the next test day for
> increased visibility.
>
> [1] - http://images.rdoproject.org/docs/
>
>
> /R
>
> Harry
>
> On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena <javier.pena at redhat.com>
> wrote:
> >
> >
> > ----- Original Message -----
> >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving
> >> test day was brought up.
> >>
> >> Test day is, for the most part, about getting people to beat on the
> >> latest packages and find problems. However, since most of these problems
> >> are being found in CI, it's time to make test day also about giving
> >> people an opportunity to see what's coming in future releases. To that
> >> end, user experience is pretty important on test day.
> >>
> >> Several suggestions were made to improve the test day experience for
> >> folks that aren't already experts:
> >>
> >>
> >> * Test setup matrix cleanup? Remove tests that are no longer relevant.
> >>
> >> * More detailed, beginner-friendly instructions for testing. (Test day
> >> as product preview for potential users, or existing users who are not
> >> deep experts.)
> >>
> >> * Ask other teams to provide use cases they want to validate.
> >>
> >> * Tracking the tests on an etherpad with instructions, and registering
> >> people to use cases, so that we're sure that everything is being
> covered.
> >>
> >>
> >> While these are all great suggestions, each requires that someone
> >> actually step up and make it happen. Each test day, for example, we talk
> >> about better instructions for the test scenarios, and everyone agrees
> >> that it's a good idea.
> >>
> >> Anyways, as we start looking towards Ocata, are there other suggestions
> >> as to how we can make the test day more welcoming to folks trying out
> >> RDO for the first time, and existing OpenStack users looking for a
> >> preview of the next release, as well as the usual suspects? And, as
> >> importantly, people who are able to make some of these things happen?
> >>
> >
> > During today's RDO meeting, I had the idea of having a pre-baked image
> with the basic setup (base CentOS + configured repos, maybe some
> documentation included) in TryStack or a cloud provider that would like to
> help us during the test day. Then, each tester could create a VM in that
> environment and run their own test scenario.
> >
> > Thinking of it, it requires:
> >
> > - A prepared image (not a big deal, we could do it)
> > - A public cloud with enough resources for the test days, and enough
> security measures to prevent abuse
> > - Anything else?
> >
> > Regards,
> > Javier
> >
> >> Thanks.
> >>
> >> --Rich
> >>
> >>
> >> --
> >> Rich Bowen - rbowen at redhat.com
> >> RDO Community Liaison
> >> http://rdoproject.org
> >> @RDOCommunity
> >>
> >> _______________________________________________
> >> rdo-list mailing list
> >> rdo-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/rdo-list
> >>
> >> To unsubscribe: rdo-list-unsubscribe at redhat.com
> >>
> >
> > _______________________________________________
> > rdo-list mailing list
> > rdo-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/rdo-list
> >
> > To unsubscribe: rdo-list-unsubscribe at redhat.com
>
> _______________________________________________
> rdo-list mailing list
> rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe at redhat.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160925/46e6c4dc/attachment.html>