[02:56] anyone know where today's daily-live of lubuntu is? === om26er_ is now known as om26er === _salem is now known as salem_ === mmrazik is now known as mmrazik|lunch [12:48] balloons, are you instructions from your post on the 14th on your blog still good to use for Unity testing? [12:48] s/you/your === jibel changed the topic of #ubuntu-testing to: Welcome to Ubuntu QA and Testing | http://qa.ubuntu.com/ | Currently testing Precise daily images - Beta 1 next week - Sync your images! | http://iso.qa.ubuntu.com === greyback is now known as greyback|lunch === Ursinha_ is now known as Guest31670 === greyback|lunch is now known as greyback === yofel_ is now known as yofel === Ursinha_ is now known as Guest56087 === Claudinux is now known as Guest18454 === bladernr_afk is now known as bladernr_ [19:36] hey akgraner [19:36] all the unity goodness is in precise atm [19:36] so, they aren't looking for testing atm [19:36] however, during beta1 we'll be doing more manual testing [19:37] sorry, my box keeps locking up so if I seemingly go afk.. you'll know why === salem_ is now known as _salem [20:42] balloons, okie dokie :-) [21:24] sure [21:24] hello! [21:24] hello hello ;-0\) [21:25] ahh.. idling eh hehe [21:25] alrighty, so on the testcase wiki, we as a community have been attempting to go thru and update all the testcases that are there [21:26] balloons: there's also an effort led by gema to move those into litmus or the next version of it, right? [21:26] however the long-term plan is to not use that wiki for various reasons.. we can't get metrics, hard to track, hard to report pass/fail and in particular which step.. no linking of bugs to test case failures [21:26] cr3, yes case conductor is being looked at to replace [21:26] which is the successor of litmus [21:32] balloons: oK, so what I'm seeing is ... no tests are shown to select :) is this what you get too? [21:33] roadmr, what I want (and at one point got) was a list of tests to run, with the expansion arrows to expand to specific test cases [21:33] what i get now is a list of the test case names (as in local.txt.in) and then all the specific tests which should be underneath them listed below [21:34] and in the case of some of the tests, none of the actual specific tests show up.. just the general name [21:34] i trust that makes sense? [21:34] ah, yes [21:34] sounds like a suiteness problem :) [21:34] hehehe [21:35] can it be run from the tree I branched or does it have to be installed? [21:36] it can be run [21:36] execute bin/checkbox-app-testing from the root folder [21:38] is your system Oneiric or Precise? [21:39] I see all the tests in one flat list [21:39] I guess you'd like the gedit ones to appear under gedit tree-lke? [21:40] precuse [21:40] precise, and yes [21:41] ok, checking [21:41] the tests won't work out properly as they are displayed [21:41] why not? they should run individually just fine [21:42] btw the shotwell tests have a problem: shotwell/swp-002 has indentation inconsistencies in the description (remember the space at beginning of each line!) [21:42] the tests don't all display [21:42] yes exactly :-) [21:42] but I couldn't figure out what was wrong [21:42] how did you spot tha? [21:42] balloons: the logfile is your friend! checkbox.log [21:42] balloons: I use "less" to open it and then /ERROR [21:42] checkbox.log != system out [21:43] kk.. [21:43] any errors in parsing jobs will be here [21:43] i wasn't seeing any errors in terminal running.. i expected to see them [21:43] per your binary file it will be (by default) in ~/.checkbox/checkbox-app-testing.log [21:43] no, as it is errors are output to the logfile only. This can be changed in the bin/... script [21:44] you can set --log-level=error --log= [21:44] (yes, log=blank) - this will output errors and criticals to stdout [21:45] roadmr.. kk changing some of this stuff so I can see it [21:49] * roadmr wrestles with checkbox [21:51] argh.. i fixed those errors in shotwell once roadmr [21:51] i think when the machine crashed several times this afternoon I lost them :-) [21:51] hehe [21:51] oh ;( that's bad! well looking at the log is an easy way to catch 'em [21:51] yes [21:51] +1 on the log [21:51] thank you [21:52] cool shotwell is showing up, errors are showing up [21:52] cool cool [21:54] I think I found the other problem, let me test and I'll tell you [21:54] k thanks [21:55] wohoo! yes, ok have a look at jobs/local.txt.in [21:55] $CHECKBOX_APP-TESTING_SHARE should be $CHECKBOX_APP_TESTING_SHARE [21:55] so it basically wasn't finding the sub-jobs because it was pointing to the wrong place (wrong variable) [21:57] nice [21:58] that was a piece of a massive rename [21:58] i missed that file though on the cleanup [21:58] thanks! [21:58] let's see what it looks like now [21:58] hehe no prob, easy to miss [21:59] alrighty [21:59] so i think this is going to be good now [22:00] so let's talk about checkbox-qt for a moment.. [22:00] sure :) [22:00] where did things end up with it? could I get these jobs added to it instead? [22:04] balloons: it should work! [22:05] hmm.. ok [22:05] balloons: it does contain some ubuntu friendly-specific bits but the job file format remains the same, so you should be able to create a bin based on that for checkbox-qt and have it work mostly as what you have now does [22:05] checkbox-qt is a nicer gui [22:05] balloons: if anything, it's a question of maturity, with checkbox-qt you'd be testing two things: whatever you're testing and checkbox-qt itself :) [22:05] haha [22:05] yes, that's the other piece [22:06] heh [22:06] the important bits are the settings for the interface_module, interface_class and data_path in the .ini file [22:06] ok, let me get this piece working first :-) [22:06] but good to know [22:07] if it works out, I might try for using the qt interface instead [22:07] sure! well if you want to give -qt a go and see if it already works well enough for you, it'd be great for us - the extra exposure will let us find and fix bugs faster [22:07] it's already in precise dailies (and will be in Beta 1) [22:08] yes indeed [22:23] balloons: http://pad.ubuntu.com/checkbox-orca-unity does this look about right? [22:24] alanbell, yea that looks great [22:29] AlanBell, balloons : jobs need to be separated by spaces, not sure if you folks are doing that in a post-processing step [22:29] what is a job? [22:29] roadmr, yes [22:29] bingo alan [22:29] ok, great [22:29] AlanBell: yes, that's better now :) [22:29] roadmr, can you have a space in the name? [22:29] feel free to join in with the multiplayer text editor [22:29] orca/starting orca? [22:30] hehe multiplater [22:30] balloons: no, sorry :( use underscores [22:30] should names be descriptive? [22:30] fixed AlanBell :-) [22:30] yay [22:30] for what i've done it follows the old wiki format [22:30] networkmanager/nm-vpnc-001 [22:30] basically use a unique number, and in this case a 2 letter code [22:31] since nm has so many tests, we have a middle descriptor in there as well [22:31] but just make it descriptive so the output will make sense to you [22:31] ok [22:31] at this point, standards are a bit loose [22:31] you could do it that way [22:31] or-001, or-002, etc [22:32] but whatev's [22:32] no matter [22:32] so that isn't something the user sees is it? [22:33] they do see it sort of.. it's the title of the window while the test is run [22:33] but it's not in the test text anywhere [22:33] ok [22:33] tried using checkbox with orca and the monitor off? [22:34] I have never tried.. roadmr? [22:37] balloons: nope! sorry :( hehe [22:37] it should work, it's a rather vanilla gtk application, so Orca shouldn't have a problem with it [22:37] ok, now to clean up some more of those errors [22:44] roadmr, I'm looking at the log and it's hard for me to figure out what's wrong [22:44] on my syntax in the jobs [23:10] alanbell, feel free to submit a merge request whenever your all set on that orca test. thanks so much for making one! [23:14] yeah, I need to go through the tests with Pendulum (in fact I think the merge request might come from Pendulum)