[00:15] <thomasdelbeke> Hi guys
[00:15] <thomasdelbeke> server down?
[00:16] <thomasdelbeke> http://cdimage.ubuntu.com/daily/current/
[00:16] <thomasdelbeke> http://paste.ubuntu.com/116627/
[00:16] <thomasdelbeke> http://paste.ubuntu.com/116629/
[00:17] <charlie-tca> If you use the browser to go there, there are no alternate images today
[00:17] <thomasdelbeke> I know ...
[00:18] <thomasdelbeke> rsync don't work either ...
[00:18] <thomasdelbeke> I was gonna file bug
[00:18] <charlie-tca> rsync fails if the images are not there
[00:18] <thomasdelbeke> rsync -zhhP rsync://cdimage.ubuntu.com/cdimage/daily/current/jaunty-alternate-i386.iso ~/Desktop/rsync/jaunty-alternate-i386.iso
[00:18] <thomasdelbeke> yeah!
[00:18] <thomasdelbeke> hehe
[00:18] <thomasdelbeke> anyway
[00:19] <thomasdelbeke> just wanted to report
[00:19] <thomasdelbeke> thanks for feedback!
[00:19] <thomasdelbeke> cu
[00:19] <charlie-tca> Thank you
[07:31] <ara> morning all :)
[07:42] <ara> persia, I am around, in case you need help with the testcases wiki
[07:43] <persia> ara, Good morning.  Could you start with just an overview of what goes where, and how that interacts with the ISO tracker?
[07:45] <ara> persia: about the interaction with the ISO tracker, I have no clue. Better wait for schwuk to wake up, or If you're offline by the time he logs in, I will ask him for you
[07:46] <ara> persia: if you go to http://testcases.qa.ubuntu.com/ you can see, more or less, the structure
[07:46] <ara> persia: in applications you have to add test cases for the application, following the template at http://testcases.qa.ubuntu.com/TestCaseTemplate
[07:47] <ara> i.e. Nautilus: http://testcases.qa.ubuntu.com/Applications/Nautilus
[07:48] <ara> persia: you have to choose a 3-letter code per application, and then one number per test case (i.e. for nautilius: nfm-001, nfm-002,...)
[07:48] <persia> So, to add a new flavour, I'd add test cases for each of the applications concerned under Applications, and then link to them from a flavour page?
[07:49] <persia> Also, what's the filter for separation between "Applications" and "System"?
[07:50] <ara> persia: system is supposed to be for things that are better fitted for the System menu, rather than the Applications menu
[07:51] <ara> persia: about the flavour, yes, you can add one more to the home page, and then links (or includes) to other things under applications, system or install (for type of installations)
[07:51] <persia> Would that also extend to things under "Preferences" where there aren't that class of menus?
[07:52] <ara> persia: yes, I would do that way
[07:53] <persia> For the installer tests, is it safe to assume "Desktop" means LiveCD?
[07:54] <ara> persia: yes, that is what it means :-) the iso name says "desktop" :)
[07:55] <persia> Well, not all of them :)  http://cdimage.ubuntu.com/ubuntu-mid/daily-live/current/jaunty-mid-lpia.img doesn't have "Desktop"
[07:56] <ara> persia: :-)
[07:56] <ara> persia: you can request then a change of name in the wiki to be more "all flavours" compliant
[07:57] <persia> To whom would that request be directed?
[07:58] <persia> Also, I see a link from Applications to Applications/EvolutionMail and a link from Ubuntu/Applications to Ubuntu/Applications/Evolution
[07:58] <persia> Is there a guide as to which sort of naming scheme is correct?
[07:59] <ara> persia: mmm, I don't think there is a guide yet, let me try to find something. but the correct path is Applications/<application>, but we are still migrating those with the wrong path
[08:00] <persia> So "Ubuntu/Applications/Evolution" is wrong and "Applications/EvolutionMail" is correct?
[08:01] <ara> persia: yes
[08:03] <persia> Also, there are a couple situations where I would expect to request different sets of per-application tests for different flavours.  As an example, both Xubuntu and Ubuntu MID use thunar, but the use cases differ.  How should this be indicated?
[08:04] <ara> mmm, persia, that's tricky. because at the beginning we decided to go for <flavour>/Applications/<application>, but then heno and davmor2 decided to go for the current one. I don't know why... could you ask them instead?
[08:05] <persia> Sure.  Neither seems to be around just now, but probably in a couple hours, no?
[08:06] <ara> persia: davmor2 should be around in 30 min
[08:06] <persia> OK.  Is there anything else you think I should know before I start drafting test cases?
[08:07] <ara> persia: you can have a look to the spec, in case it provides you with more information: https://wiki.ubuntu.com/QATeam/Specs/TestcaseWikiMigration
[08:09] <persia> Looking about, I realise I have one other question: what does the "Tester" column indicate on pages like "Ubuntu/Applications"?
[08:11] <ara> persia: that page is not longer valid, but it used to mean the person that was in charge of the migration from /Testing/Cases to the new wiki
[08:13] <persia> If that page isn't valid, how is one to link the individual test cases to a flavour set?
[08:25] <ara> persia: I guess (just guessing) that the same one (maybe without the tester column) should be ok
[08:25] <persia> That makes perfect sense.  Thanks a lot.  I'll start framing a flavour, and poke davmor2 about how to handle specific cases on a flavour basis when he shows up.
[08:30] <ara> persia: cool. I am subscribed to the whole wiki, if I see something weird, I'll let you know :)
[08:31] <persia> Thanks!
[08:35] <persia> davmor2, Good morning.  ara says you understand about how to identify test cases for the testcase wiki.
[08:35] <davmor2> persia: I do indeed
[08:36] <davmor2> Why?
[08:36] <persia> So, I'm adding testing overviews for a couple more flavours, and wondered how to handle cases where the usage of an application differed due to differences in the environment (e.g. thunar for Xubuntu vs. Ubuntu MID).
[08:36] <persia> I'm guessing that each flavour only wants a subset of the test cases listed under the application, but I'm not sure how to indicate that.
[08:37] <davmor2> persia: Right at the minute the way things are working is as follows.
[08:38] <davmor2> 1: all applications go to /applications
[08:39] <davmor2> 2: you then make up a test plan under /testplans which pulls in the installation and apps you require testing
[08:40] <davmor2> 3: on the whole people won't test every app so pick between 3-5 (hopefully these will be randomised by a script schwuk is writing)
[08:41] <persia> Under /testplans?  Is that /Plans?  Also, how does that relate to the links on the front page to /Ubuntu and /Kubuntu?
[08:42] <davmor2> Tags for install cases are made up of xxx-111 where xxx=3 letters that tie into the case (eg ubiquity whole drive install becomes uwi) and 111 becomes 001 etc for each testnumber for each set of letters in a case
[08:43] <davmor2> persia: that was an old attempt that got dropped
[08:44] <persia> OK.  So if I want to create a set of cases for a flavour, where should I start?
[08:44] <davmor2> persia: /testplans isn't in till we get some cases together
[08:45] <persia> that page doesn't exist yet
[08:45] <persia> So, I should wait?
[08:45] <davmor2> persia: look at /Install most of  them are now complete
[08:46] <davmor2> persia: /testplans can just be added but at the moment there are no apps to put to it
[08:46] <persia> Right.  /Install, /System, and /Applications all look sane.  What I seek is more how to collect a set together to describe what needs testing for a given flavour.
=== jouston1 is now known as jouston
[08:49] <davmor2> the general idea will be that the /testplan page just contains a whole bunch of includes lines
[08:49] <davmor2> I'll link to an old example for you
[08:49] <persia> Which would include specific test cases, or applications to test?
[08:50] <davmor2> https://wiki.ubuntu.com/Testing/Ubuntu/LiveCd/LiveSession  Here is an example if you hit edit you'll get the drift
[08:51] <davmor2> persia: For us it means that we only need to update 1 test for an app rather than the entire testcase
[08:51] <persia> I see the advantage, and using includes makes sense.  I'm just trying to understand how to generate the set of things to test for a specific flavour, and where to put it.
[08:56] <davmor2> Right so the way the test plans will work is thus.  /Testplans/XubuntuLiveCd would be a page of plans that is just includes lines.  It will pull in 1 Live cd install case + 3-5 apps that are specific to Xubuntu so thunar, thunderbird and abiword as examples
[08:57] <persia> OK.  Now, how ought the differences in testing thunar for Xubuntu and Ubuntu MID be indicated?
[09:00] <davmor2> persia: None needed.  The codebase is the same.  However each testplan will have it's own test number.  So thunar under XUB-001 thu-001 would be different to thunar under MID-001 thu-001 but all the results for thunar can be pulled together etc
[09:01] <davmor2> hope that makes sense it did in my head
[09:01] <persia> Now I'm very confused.  Are there then two pages of thunar tests which are included?
[09:02] <davmor2> 3 pages of results can be drawn a test for thunar from results for thu-001 and then result for indvidual cases for xubuntu and mid
[09:03] <davmor2> need to go for a bit bbl
[09:03] <persia> OK.  Catch me when you're back, as I still don't think I understand.  I'll prep an example for discussion then.
[09:30] <davmor2> persia: ping
[09:32] <persia> davmor2, I've put together a small example that illustrates the two ways that I could understand the structure at http://paste.ubuntu.com/116733/
[09:33] <persia> Are either of these correct, or are you envisioning something else?
=== thekorn_ is now known as thekorn
[11:51]  * davmor2 goes to smoke testing as doesn't want issues with testcase :)
[12:43]  * ara -> lunch
[12:44]  * davmor2 working lunch nothing better to do :)
=== mvo_ is now known as mvo
=== cprofitt is now known as cprofitt_work
=== Erkan_Yilmaz is now known as Erkan_nam_viet_y
=== thekorn_ is now known as thekorn
=== erle64- is now known as erle-
[20:07] <cgregan> Does anyone out there have an Intrepid instance running in qemu with resolution over 800x600?