Testcase not recorded

[Istimsak Abdulbasir]

I see what you mean. I can see tests have been done on the unity package
during certain times, but not everyday.

I do follow the procedure. Basically, the daily builds are, like you said,
check ups for current stability and to find new features or bugs. After
awhile, the daily builds are frozen and a milestone is made from all those
daily builds. This milestone is then specifically tested to assure what we
have is in working condition if this image were to be pushed out to the
public. Then it goes back to the daily builds for further work until the
next milestone freeze. Sounds about right?


On Thu, Apr 11, 2013 at 9:23 PM, Nicholas Skaggs <
nicholas.skaggs at canonical.com> wrote:

>  You don't have to do it everyday :-) Let me explain a little how it
> works. When we test a specific milestone, like for example the mesa testing
> right now, we're testing a specific build with the goal of verifying it as
> stable and ready for general consumption. Images are tested this way too --
> when we have a specific milestone like an alpha or beta. At the start of
> the milestone, the image is frozen and tested. If we find bugs we need to
> fix, we'll rebuild the image and yes, we need new results against the new
> image we built when that happens. The old builds will be archived and
> available under the history link.
>
> However, the daily images are built automatically everyday no matter what.
> We test against them as a checkup to ensure things are running smooth, but
> we're not trying to release a specific daily until we freeze it, make a
> milestone and call for specific testing. Many folks test the image
> occasionally to see what's new, spot regressions or bugs, etc. We do
> intentionally test the images as part of our cadence testing, but again,
> that's once every couple weeks, not everyday.
>
> So let's give some examples so you can see this in action. Again take a
> look at mesa:
>
> http://packages.qa.ubuntu.com/qatracker/milestones/266/builds
>
> There's only one build. Go ahead and click the "See removed and
> superseded builds too<http://packages.qa.ubuntu.com/qatracker/milestones/266/history>"
> link. It will only show the one build.
>
> Now, try the same thing on unity testing from a few weeks ago:
>
> http://packages.qa.ubuntu.com/qatracker/milestones/262/builds
>
> You'll notice the last build pushed has no results -- but we did test it!
> The results are linked to the older builds. Click the "See removed and
> superseded builds too<http://packages.qa.ubuntu.com/qatracker/milestones/262/history>"
> link again. Noticed all the builds and results?
>
> Make sense?
>
> Nicholas
>
>
> On 04/11/2013 08:33 PM, Istimsak Abdulbasir wrote:
>
> So you are saying that I should complete all the test procedure for a
> particular testcase because a new image will be uploaded everyday?
>
>
> On Thu, Apr 11, 2013 at 1:53 PM, Nicholas Skaggs <
> nicholas.skaggs at canonical.com> wrote:
>
>>  Istimsak, I see what happened :-) New builds are posted daily, and it
>> won't show your results on today's build. If you want to see them you'll
>> need to look at yesterday's build:
>>
>> Here's your results from 4/7, 4/8, and 4/9 :-)
>>
>> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/41516/testcases/1300/results
>>
>> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/41672/testcases/1300/results
>>
>> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/41587/testcases/1300/results
>>
>> Does this make sense?
>>
>> Nicholas
>>
>>
>> On 04/11/2013 01:29 PM, Istimsak Abdulbasir wrote:
>>
>> I started the testcase for kubuntu raring i386 and completed the "install
>> to entire drive" procedure. When I looked back at the testcase to continue
>> the test, I noticed the kubuntu testcase did not record my test. Is there a
>> reason for that?
>>
>>
>>
>>
>> --
>> Ubuntu-quality mailing list
>> Ubuntu-quality at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-quality/attachments/20130411/d454f42a/attachment.html>