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