[00:04] <thetoxicarcade> balloons, if this is helpful, here's 10 minutes of torture: http://youtu.be/-rZ4zooGLGo
[05:12] <elopio> veebers: sorry, there's something crazy with my quassel. It won't connect again to the canonical server.
[05:12] <elopio> oh, it connected now.
[05:13] <elopio> veebers: anyway, if you are around and have some time, please take a look at http://pad.ubuntu.com/test-indicator-messages and let me know if it makes sense or is too complex/weird.
[05:14] <veebers> elopio: looks good with a quick glance, this is what I have so far (quick draft: https://docs.google.com/a/canonical.com/document/d/1pBy7CoQU6p5Yr3UT_iZmP6e_1IyOhaAMJAoV9CmjTMI/edit#)
[05:15] <veebers> elopio: I think the API code can be represented by python code with sphinx docstrings
[05:15] <elopio> veebers: cool. We are not too far.
[05:15] <veebers> I mean you already have the sphinx docstrings there anyway :-)
[05:16] <elopio> veebers: tomorrow we can agree on a format.
[05:16] <veebers> elopio: yeah, it's pretty close. Thomi has made some comments on that doc too that you might find useful to apply to yours
[05:16] <veebers> elopio: sounds good to me
[05:22] <veebers> elopio: right, I'm off for the night, see you tomorrow
[05:22] <elopio> bye
[15:32] <elopio> alesage: are you working today?
[16:39] <alesage> elopio hi, a bit under the weather but yes :)
[16:40] <elopio> alesage: sorry about that.
[16:40] <elopio> alesage: If you feel better and have some time, I would like to get some comments about http://pad.ubuntu.com/test-indicator-messages
[16:42] <alesage> elopio, I'll certainly get to, yes
[17:13] <elfy> balloons: https://code.launchpad.net/~elfy/ubuntu-manual-tests/1132847/+merge/237065
[17:13] <balloons> elfy, on it
[17:14] <elfy> ta :)
[17:18] <balloons> elfy, perfect, except the indentation is a bit off on "<dt>Check for existence of previously created file</dt>, at least in lp
[17:18] <balloons> I will approve
[17:19] <elfy> well don't if you really don't want to :)
[17:22] <balloons> elfy, I trust you'll fix the indentation and them merge yea
[17:23] <balloons> ?
[17:24] <elfy> if it's busted yea I'll fix, merge and sync it yep
[17:33] <elfy> balloons: okey doke all done
[17:38] <elfy> balloons: bug 1347670 - I left a question there a while back for you - forgot all about it till now - if you could look at some point
[18:08] <balloons> elfy, that is a bit odd for a testcase
[18:08] <balloons> elfy, I assume it "upgrades" because it wants to re-use the cd. I'm thinking it should just be tweaked to re-install not upgrade
[18:09] <elfy> balloons: that was my thinking when I went and looked properly, I'll get on a do that now there's consensus :)
[18:22] <elfy> balloons: ok - mp is there now for that https://code.launchpad.net/~elfy/ubuntu-manual-tests/1347670/+merge/242102
[18:27] <alesage> elopio I'm reviewing this pad and I see charles here too :) , have you introduced him to our task or is he snooping ;) ?
[18:28] <elopio> alesage: I also asked him for early feedback.
[18:28] <charles> alesage, I'm stalking you
[18:28] <alesage> I heard footsteps
[18:47] <alesage> elopio you might want to compare the ofono work in messaging-app with a helper that Antti made for indicator-network, which is in lp:indicator-network http://bazaar.launchpad.net/~indicator-applet-developers/indicator-network/trunk.15.04/view/head:/tests/autopilot/indicator_network/helpers/phonesim_manager.py
[18:57] <elopio> alesage: cool. That seem to have the enable/disable I was requesting.
[19:05] <balloons> elfy, hmm, that's a huge chunk of the testcase removed. I guess that makes sense. The upgrade tests are better checks for upgrades
[19:05] <balloons> approved
[19:11] <elfy> balloons: ok - you want me to merge etc?
[19:13] <elfy> doing it
[19:24] <thetoxicarcade> Question, if I'm running the cinnamon PPA and it makes me unlock twice from suspend, how do I report that?
[19:26] <elfy> manually at the 'package' you want to report it against
[19:27] <elfy> the auto reporting tool(s) don't like PPAs
[19:30] <balloons> right if you have a ppa, you aren't running software from the archive, so it's up to the ppa owner
[19:33] <thetoxicarcade> cool. How do I grab the running information if it's a login though?
[19:41] <Letozaf_> balloons, hi
[19:45] <balloons> Letozaf_, howdy
[19:46] <Letozaf_> balloons, I managed to fix the mess I made yesterday, but I do not succeed launching filemanager app in phone mode on my Desktop, it launches in normal mode
[19:47] <Letozaf_>  Launching process: ['/home/letozaf/autopilot-tests/ubuntu-filemanager-app/src/app/filemanager', '-testability', '-p ', '-q', '/home/letozaf/autopilot-tests/ubuntu-filemanager-app/src/app/qml/filemanager.qml']
[19:47] <Letozaf_> balloons, is the -p in the right place ?
[19:47] <Letozaf_> balloons, cannot put it before the -testability
[19:48] <balloons> Letozaf_, v
[19:48] <balloons> .http://paste.ubuntu.com/9077264/
[19:48] <balloons> wow, sorry bout that
[19:48] <balloons> that works for me
[19:48] <balloons> biab
[19:49] <Letozaf_> balloons, that's exactly what I did, how come it does not work :( have you got vivid ?
[19:49] <balloons> Letozaf_, yes
[19:49] <Letozaf_> balloons, aahh!! :O
[19:50] <balloons> Letozaf_, you also need to merge from trunk. There are qml changes required, and you have to rebuild after it
[19:50] <balloons> so it's in the binary
[19:50] <Letozaf_> balloons, aahh!! I thought lp:~carla-sella/junk/filemanager-try was alrady ok
[19:50] <Letozaf_> balloons, so that's why :-P
[19:50] <Letozaf_> balloons, ok so lets try again :)
[19:51] <Letozaf_> balloons, thanks
[19:51] <balloons> Letozaf_, lol yea. mege trunk, it should bring qml changes, then rebuild
[19:51] <balloons> Letozaf_, so everything works now though yes?
[19:51] <Letozaf_> balloons, yes a part that test :-P
[19:52] <balloons> I'm ready to merge what works, so I would update the branch on the mp
[19:52] <Letozaf_> balloons, ok
[20:02] <elopio> veebers: to confirm if I got it straight, I should add to my draft things like def, class and docstrings?
[20:03] <veebers> elopio: yeah, I would stub out what you have as python code with the docstrings etc.
[20:03] <elopio> ok, that will look good.
[20:03] <elopio> python is pretty.
[20:03] <veebers> ^_^
[20:04] <elopio> thomi: alesage: veebers: and what about the testing strategy for the test helpers? Currently I just explained it. Should I also make a skeleton of the tests that the helpers should have?
[20:05] <veebers> hmm, not sure, perhaps at this stage just note the scenarios needed for testing? i.e. this function needs a test for when x happens, for when y happens etc.
[20:05] <veebers> if needed we can expand that into a more cohesive skeleton
[20:07] <elopio> veebers: yes, I would prefer not to do the skeleton for that. Maybe only if it is not clear to devs.
[20:07] <veebers> elopio: ack, agreed
[20:11] <elopio> ok, I got to pick my bike from the mechanic. So long lunch, I'll bbl.
[20:24] <balloons> Letozaf_, so how do we look?
[20:26] <Letozaf_> balloons I am rebuilding ...
[20:53] <Letozaf_> balloons, this is weired, it fails on my PC, now the app starts correclty in phone mode but I get this failure:http://paste.ubuntu.com/9078285/
[20:54] <Letozaf_> balloons, the same one as before merging
[21:09] <Letozaf_> balloons, ok so now I fixed that error, but got a new one :(
[21:16] <Letozaf_> balloons, ok it's fixed, lets see if it passes on Jenkins now
[21:25] <Nothing_Much> quick question, are there some differences between Virtualbox in the repos in 14.10 and the Virtualbox from Oracle?
[21:26] <Nothing_Much> if so, then which version would be best for testing out the i386 version of unity 8?
[21:29] <knome> Nothing_Much, running the repository version gives you an easier and faster way to make sure whether you are having problems with virtualbox or the ISO you are testing, since several people can quickly confirm that
[21:30] <Nothing_Much> knome: alright cool, thanks
[21:30] <knome> as usually, if you don't have a very good reason to run an application version that is not in the official repositories, you shouldn't
[21:35] <alesage> veebers, tell me about this "get_properties" function, is it a standard thing to have for a fixture, e.g., are are we just mimicking the d-bus behavior?
[21:36] <veebers> alesage: sorry?
[21:36] <alesage> veebers, looking at yr sample code for the battery fixture
[21:37] <veebers> alesage: oh as mentioned in my code example? that was just a thought and is all changing now :-) The reason I had it there for the draft was because there was a dbus query example there to get those details out, not needed though
[21:37] <alesage> veebers, I see
[21:38] <veebers> I thought at the time, perhaps we'll need that. We don't. I'm just in the process of changing some of the docs I'm writing as we'll be using upower mock (python-dbusmock) now it appears. (code doesn't really change though)
[21:49] <thetoxicarcade> regarding reporting a bug in a PPA, there doesn't seem to be a guide on that in launchpad itself
[22:03] <balloons> thetoxicarcade, as we said, bugs in ppa's aren't intended to be reported in general
[22:04] <thetoxicarcade> at all, even to the owner of the ppa?
[22:04] <balloons> as in; it's up to the developer of the ppa
[22:04] <balloons> launchpad itself holds bugs for projects, so likely that's the place to report the bug
[22:04] <thetoxicarcade> yeah, just wish there was a button for some of these ppas, only half of them have one
[22:04] <balloons> you shouldn't report the bug against the ubuntu version of the package, if there is one
[22:05] <thetoxicarcade> oh, alright, we cool *playin it kool* hey I'm reporting a bug for the lxc container with my hardware am I doing this right?
[22:05] <balloons> ppa's are the wild west, more or less, lol.. It's a personal package archive
[22:05] <balloons> thetoxicarcade, are you playing with the unity8 ppa?
[22:05] <thetoxicarcade> :{D I knew that
[22:05] <thetoxicarcade> I am playing with the unity8 ppa and a really old and buggy cinnamon ppa
[22:06] <balloons> the unity8 ppa can be filed against unity8
[22:06] <balloons> cinnamon I've no idea
[22:07] <thetoxicarcade> https://bugs.launchpad.net/ubuntu/+source/unity8-lxc/+bug/1393960 how was this
[22:11] <balloons> thetoxicarcade, I would also point you @ #ubuntu-unity. But I suspect that might work
[22:18] <alesage> veebers, elopio, thomi, maybe we should have a master page wherein we ask for 'page-object-model'-type helpers, as much of this will be shared?  or treat separately?  thoughts?  e.g. "get_indicator_icon"
[22:19] <alesage> also veebers elopio thomi fwiw this is how the emulators/helpers stand atm http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/emulators/main_window.py#L65
[22:20] <veebers> alesage: can you elaborate on your first comment?
[22:20] <thomi> alesage: if there's common content then I have no problem linking to a common page. If it's in another sphinx bundle (like the autopilot docs) then we can use the intersphinx plugin to link to them
[22:22] <alesage> veebers, I see that elopio makes some requests for helper methods of Unity UI, e.g.
[22:23] <alesage> veebers, these might take the form of 'custom proxy objects' for indicator pages and menu items, e.g.
[22:23] <thetoxicarcade> AWESOME stuff
[22:23] <alesage> veebers, elopio if we do want to request these things then maybe make a page of limited suggestions?
[22:23] <alesage> veebers, is that clearer?  need elopio's feedback
[22:24] <elopio> alesage: do you mean, something to explain wshat the page object is, or to put all our helpers in the same place?
[22:24] <balloons> thetoxicarcade, afaict your bug report is in the proper place. The unity8 guys should have a look at it soon enough and if more info is needed I'm sure they will ask.
[22:25] <alesage> elopio, you might need to explain what it is, e.g., don't know if we want to put all the helpers in the same place (although that'd probably be best)--just want to put the documentation in the same place so as not to repeat
[22:25] <thetoxicarcade> many thanks.
[22:25] <balloons> thetoxicarcade, it might be useful to debug it a bit more; unable to start session doesn't tell us too much
[22:25] <alesage> elopio, wanting to see how you'll treat that request in your doc as you're the most experienced in this
[22:26] <balloons> thetoxicarcade, btw, I didn't get a chance to watch your video yet, but that's awesome you put one together!
[22:26] <thetoxicarcade> it basically cheats off your 55min for 10 min
[22:26] <thetoxicarcade> I contributed nothing, yet!
[22:27]  * balloons looks and sees a bug report
[22:27] <elopio> alesage: the explanation is here: http://developer.ubuntu.com/apps/platform/guides/acceptance-testing-using-the-page-object-model/
[22:27] <alesage> elopio, I'm aware ;) , wanting to know how to address in our docs
[22:28] <elopio> elopio: but as we are going to request them just to fill the methods from the API, what we need to take care is only to be requesting the right objects and methods.
[22:28] <elopio> heh, I pinged myself
[22:28]  * balloons snaps a screenshot
[22:28] <knome> elopio, congrats!
[22:28] <alesage> elopio careful!
[22:29] <elopio> alesage: ^ I think that it's enough just to name the class, method, and the return value we expect.
[22:29] <elopio> then the devs will make an MP that we will review. Maybe at that point we will have to tell them to make a method internal, or adjust a little the thing they are returning.
[22:30] <elopio> alesage: on the example for example, 'get_indicator_icon'
[22:30] <elopio> that doesn't follow the page object pattern. _get_indicator_icon should be an internal method, wrapped by a public method called something like:
[22:30] <thetoxicarcade> "alright everyone and welcome to the manual uos 1411 testing meeting"
[22:31] <elopio> has_new_notifications()
[22:31] <elopio> or is_alarm_set()
[22:31] <elopio> or is_wifi_connected()
[22:31] <thetoxicarcade> bye (I love the tidbits I catch here, wish I knew about this sooner) ((watching uos since I missed it (darn) )) (((BACON)))
[22:33] <alesage> elopio, to be clear, do we want to specify all of those functions now?  or ask for just the hardware/mocking/items and expect to go over the rest during code reviews
[22:34] <elopio> alesage: as I understood it, we want to specify all those functions now and make python skeletons for them.
[22:35] <elopio> not implementation details, but specify clearly what's the API signature that we expect from these testability python modules
[22:36]  * alesage just wants all to agree as veebers' draft has only hardware-ey mocks at this point
[22:39] <elopio> veebers: was it that I specified in too much detail, or that yours is work in progress?
[22:41] <veebers> mine is definiately a WIP, I didn't specify any helpers specific for the UI yet (trying to concentrate on the missing testability parts). i.e. there should be helpers for the notifications etc.
[22:45] <thetoxicarcade> where is the mockup for the ui for the bug tracker?
[22:54] <balloons> look at the notes in summit from the session
[22:56] <thetoxicarcade> okay, so at the summit not in the youtube video aaaaahhh (makes sense, come to think of it)
[23:42] <alesage> projects-team needing a review especially for specifying UI helpers--elopio you exspecially pls :) https://code.launchpad.net/~allanlesage/ueqa-code-proposals/indicator-datetime/+merge/242148
[23:46] <thetoxicarcade> I had this absolutely cool idea for the bug tracker then I realized we already have it, just not all mushed together into a wonderful visual dashboard of cases/builds/bug statusesezezez (who builds the errors.ubuntu.com page?)