That's a shortcut button :-) click on the link to see the testcase itself:

http://packages.qa.ubuntu.com/qatracker/milestones/291/builds/46578/testcases/1430/results

Nicholas

On 06/18/2013 08:35 PM, Istimsak Abdulbasir wrote:
Sorry for the confusion. In some of the testcases, I noticed there was only an option to submit a pass result but not a failed result.

This testcase only has a "pass with no bugs". If it failed, submitting a bug report will be the next course of action. I was wondering if we could also have to option to write a comment to notify of anything interesting we may come across during the test 

Istimsak Abdulbasir


On Tue, Jun 18, 2013 at 5:47 PM, Nicholas Skaggs <[email protected]> wrote:
Istimsak,
Transmission is fixed -- third time is the charm, I'm sure of it! :-)

What do you mean by passing a failed result? The best place to store critical information intended for developers is in your bug report :-) Are you wanting to pass feedback along even if the test passes? I need a little more detail here on what your after :-)

Vasudevan,
Thanks for sharing your notes. On the unity testcases most of them are probably just updates we need to do to the testcase as you said.
Each cycle they tweak things and our tests can get behind :-) For the rest I'll just leave my comments in your doc:-)

On the introspection piece, if nautilus has got you down, you can try some of the new QML apps. Despite Carla's habit of 
finding weird things with autopilot (breaking things is a wonderful trait for a tester, go carla!), they are much easier and more straightforward 
to write tests for. Consider picking up a test or two there to keep your sanity -- fighting with a GTK app can get to you, trust me! Have a look here
for the list of the needed tests:

Thanks!

Nicholas


On Tue, Jun 18, 2013 at 2:52 PM, Istimsak Abdulbasir <[email protected]> wrote:
This package does not a proper testcase associated with it.



On Tue, Jun 18, 2013 at 2:23 PM, Istimsak Abdulbasir <[email protected]> wrote:
We also need the option pass a failed result and to write comments on our findings. We won't be give critical information back to the developers if there is no way of explaining our findings.

Istimsak Abdulbasir


On Mon, Jun 17, 2013 at 4:43 PM, Nicholas Skaggs <[email protected]> wrote:
Ok, I added testcases for these products that somehow failed to push the first time :-)

Simple Scan
Brasero
System Settings
Transmission

In addition installation instructions should exist for all packages. Thanks!


Nicholas

On 06/15/2013 09:59 PM, Istimsak Abdulbasir wrote:
I am unable to view the testing procedures for some of the package milestones for this weeks cadence testing.



On Fri, Jun 14, 2013 at 6:49 PM, Nicholas Skaggs <[email protected]> wrote:
Whew! See that went quicker than expected ;-) Everything should be up now, please ping if you find a gap.

Cheers,

Nicholas


On 06/14/2013 06:25 PM, Nicholas Skaggs wrote:
Alright, I know several of you are particularly excited about this. Our first cadence week is here. Starting June 15th, we'll be testing images and packages over the course of the next week. So what is cadence testing? Have a look at this page to get more information:

https://wiki.ubuntu.com/Testing/Cadence

In short, as a community we're testing different things about every ~2 weeks in ubuntu, and sharing results to flesh out bugs and problem areas. The full schedule is here, but note the release schedule changed TODAY, so this will be updated as well to reflect those changes very soon.

https://wiki.ubuntu.com/QATeam/Cadence/Saucy

So what's up for testing this week? The daily images, the default applications in ubuntu (we'll start tracking them all throughout the cycle) and a new version of alsa testing. Full details are here:

https://wiki.ubuntu.com/QATeam/Cadence/Saucy/Week1

If you need help submitting results, have a look at this page, https://wiki.ubuntu.com/Testing/QATracker, and the walkthroughs listed. Of particular interest is the ISO testing and Cadence Week testing walkthroughs.

https://wiki.ubuntu.com/Testing/Cadence/Walkthrough
https://wiki.ubuntu.com/Testing/ISO/Walkthrough

Do note that you don't need anything special to participate in cadence week testing! Both an installed version of the development branch of ubuntu (aka saucy) in a VM or on a real box, or even a live session of the lastest daily image will work.

Good luck! Bear in mind this is the first week for our new format, so there may be growing pains. Feedback is very much appreciated. Thanks and Happy Testing everyone,

Nicholas

PS. A note; as of this email, I am still adding the ubuntu default apps, slowly but surely to the package tracker. They should be there before tomorrow :-) Also the version tracking is still coming online in case your watching :-)


--
Ubuntu-quality mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality








-- 
Ubuntu-quality mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Reply via email to