<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I wanted to cross-post this to our list
as well, as it contains some pertinent info, as well as what I've
written on my blog post this afternoon:<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.theorangenotebook.com/2013/03/kick-starting-quality-for-ubuntu-touch.html">http://www.theorangenotebook.com/2013/03/kick-starting-quality-for-ubuntu-touch.html</a><br>
<br>
In short, let's leverage our knowledge of manual and automated
testing for the new platform.. Starting with the core
applications. We'll also be getting into hardware testing, writing
some cool automated tests using umockdev
(<a class="moz-txt-link-freetext" href="https://github.com/martinpitt/umockdev">https://github.com/martinpitt/umockdev</a>) and autopilot if we can,
and in general smoke testing and dogfooding the images and apps as
they come. But there's no reason to wait! We can be involved now
and stay informed with what's happening on the platform, as well
as working with the developers to keep things humming along
nicely. There's plenty of cool stuff to do, enjoy and test no
matter what skills you bring to the table, and it's all happening
now.<br>
<br>
I'm excited about being a part of making sure ubuntu touch is an
amazing platform -- I know I want a ubuntu phone, and we can be a
big part of making it a nice experience.<br>
<br>
Squirming with excitement,<br>
<br>
Nicholas<br>
<br>
On 03/13/2013 07:03 PM, Nicholas Skaggs wrote:<br>
</div>
<blockquote cite="mid:514105DA.3030103@canonical.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Just wanted to drop by the list to say hello and introduce myself
and everyone else in ubuntu quality. I'm part of the quality
community team, and I can't want to dive in and help test all this
cool stuff you guys are putting together!<br>
<br>
To that end, I wanted to make you aware of a few things happening
now to help support the testing of these applications. There is a
pre-existing project,<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://launchpad.net/ubuntu-manual-tests/">https://launchpad.net/ubuntu-manual-tests/</a>,
and tracker, <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://packages.qa.ubuntu.com/">http://packages.qa.ubuntu.com/</a>,
that we as a team utilize for manual testing the current ubuntu
desktop images, applications, hardware, etc. In a nutshell, we as
a team regularly test the desktop images and applications on a
variety of real and virtual hardware. We maintain our tests in the
repository linked above, and utilize several 'qatrackers' to
record our results, ie packages.qa.ubuntu.com.<br>
<br>
With that in mind, we want to help test this new platform,
including the core apps. I've started to point folks within our
community towards the work that is going on here in order to have
some nice testing going on as your applications reach a usable
state. As an example, I took a look at the calculator app which
has made great strides against the design that has been posted
thus far. Using that design, I wrote several tests that walk
through a series of actions and expected results. You can see the
result here:<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bazaar.launchpad.net/%7Enskaggs/ubuntu-manual-tests/ubuntutouch/view/head:/testcases/touch/ubuntu%20calculator%20app">http://bazaar.launchpad.net/~nskaggs/ubuntu-manual-tests/ubuntutouch/view/head:/testcases/touch/ubuntu%20calculator%20app</a><br>
<br>
This test then ends up looking this this on our tracker (note this
is just a mockup on a dev site, don't submit results :-) );<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://packages.qa.dev.stgraber.org/qatracker/milestones/250/builds/27920/testcases/1560/results">http://packages.qa.dev.stgraber.org/qatracker/milestones/250/builds/27920/testcases/1560/results</a><br>
<br>
This raw seem a bit weird to look at for some of you, but I would
refer you to the following pages on how we write and maintain our
manual tests:<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.ubuntu.com/Testing/TestCaseFormat">https://wiki.ubuntu.com/Testing/TestCaseFormat</a><br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual">https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual</a><br>
<br>
So, what does this mean for all of you?<br>
<br>
-- If you have some manual tests for your application, please,
create and submit them to the repository! We'll make sure our
testing events utilize them. There's great tutorials if your new
to what a manual test should look like.<br>
-- If you need some manual testing of your application, please let
me know. We in ubuntu quality can help write tests if needed and
test your app.<br>
<br>
We as a community also have been working with autopilot, and have
some experience in writing those types of tests as well. There's
some excellent resources to help you, and I'm always interested in
automated tests if you need help :-) <br>
<br>
In short, let us help make your apps rock! We're excited about the
possibilities of the new platform and eager to get our feet wet
and help test all the new stuff.<br>
<br>
Cheers,<br>
<br>
<font face="Verdana">Nicholas</font><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>