lubuntu-qa team mailing list archive

[Phill Whiteside <PhillW@xxxxxxxxxx>]

Hi David & Nicholas,

Lubuntu is following 'main' for cadence and the beta / RC part.

@ David, I've still got tasks for our applications to be written to the
'new' syntax for tests. I've done a few for us to test with, but linking
these to autopilot has not been started. The test cases do take a bit of
brain power to write up as you have to try and cover everything a user
could do to an application.... It is a very useful exercise as it points
out changes due to updates of our applications in our historical test cases
and possible bugs in the applications.

Regards,

Phill.

On 29 November 2012 21:55, Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx>wrote:

>  David,
>     I'll leave the cadence questions to phillw -- I'm not sure how lubuntu
> wants to do QA this cycle :-)
>
>     On the autopilot question, yes it will work on any gtk or qt
> application. So it's possible to run tests on lxde as well -- I'd love to
> see a default application testsuite for lubuntu also. I think it would be a
> good thing for each flavor to pursue.
>
> Nicholas
>
>
> On 11/29/2012 09:37 AM, David L Conner wrote:
>
> Hi Nicholas, Phill:
>  I'm intending to focus more time on testing during this cycle and am
> really excited to see the new tools and testing schedule in action.  I
> noticed that this cadence cycle's primary focus is on LibreOffice and
> Unity.  Are there currently any plans to have Lubuntu focused cadence
> weeks?
>
> Regarding autopilot, will it currently work on non-unity desktops such as
> lxde?  If not, then are there any plans/blueprints for making it work with
> lxde?
>
> Thanks,
>
> David
>
>
>
> On Sun, Nov 25, 2012 at 11:56 PM, Nicholas Skaggs <
> nicholas.skaggs@xxxxxxxxxxxxx> wrote:
>
>> Ok, so we're a bit delayed in starting this because, well, there was a
>> Holiday in North America called Thanksgiving. Forgive me. :-p
>>
>> So, this week (through Saturday) is our first cadence week. What that
>> means is we will be focusing testing specific packages (or isos) during the
>> week. What you can do to help is to run through a testcase (or a few :-) )
>> at some point during the next week and report your results. The goal here
>> is NOT to make all the tests green everyday. Instead, we want to test on a
>> deeper level and really look for bugs in the software (or even the
>> testcases :-) ) so we can be confident in the health of the package(s) we
>> are testing. To that end, there is no daily target -- rather we want to
>> test through Saturday (whenever that is in your localtime ;-) ). Think
>> quality, not quantity (I know, it's a bad pun.. quality quality...)
>>
>> What this means practically is during the next week, try to execute some
>> testcases for our week 1 targets (which are libreoffice, unity autopilot
>> tests and the daily raring iso). You can find the wiki page detailing this
>> here:
>>
>> https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week1
>>
>> The master schedule can be found here:
>>
>> https://wiki.ubuntu.com/QATeam/Cadence/Raring
>>
>> Again, I would suggest finding a day and time that works for you and
>> adding your results. Feel free to use IRC (#ubuntu-quality on freenode) or
>> this mailing list to discuss any bugs you may find. At the end of the week,
>> I'll recap what we did (bugs, tests ran, etc), and we can evaluate the
>> results to see if further followup and focus is needed or not. Now, our
>> testing focus's each week will change in order to target packages that need
>> more QA work, or new packages that recently landed in QA.
>>
>> Now, this week I will also be posting the next bits in our autopilot
>> series -- intending to teach you about running and writing autopilot
>> testcases. Our cadence testing this cycle will include running both
>> automated and manual tests -- we need both ;-) You'll note the autopilot
>> unity testsuite is included this week. I hope our subsequent testing weeks
>> can feature some new automated autopilot tests written by some of you :-)
>> If writing automated tests aren't up your alley, don't worry we need manual
>> testcases too!
>>
>> Happy Testing everyone,
>>
>> Nicholas
>>
>> --
>> Ubuntu-quality mailing list
>> Ubuntu-quality@xxxxxxxxxxxxxxxx
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>>
>>
>
>


-- 
https://wiki.ubuntu.com/phillw