[15:13] <paulliu> alesage: hi. about lp:~indicator-applet-developers/unity8/indicator-power-autopilot-test. Can you do a merge trunk?
[15:14] <paulliu> alesage: I messed up my branches for the Notifications helpers.
[15:32] <alesage> paulliu, ok can get to in a bit, need coffee :)
[15:57] <alesage> paulliu, working on this merge
[16:05] <paulliu> alesage: ok. Thanks. And I'll rebase my stuff on your branch.
[16:21] <alesage> paulliu, this was a bit of a mess :) , pushed that--note that if you don't want your test to run on desktop you'll have to re-add that check to your class
[16:24] <paulliu> alesage: ok.
[16:27] <alesage> paulliu, everything ok?
[16:36] <alesage> elopio, ok to move these cards to *done* if two approves, n'est-ce pas?
[16:55] <elopio> alesage: yes, just please make sure that before moving them to done, all the useful information is copied to the test card in the backlog.
[16:56] <alesage> elopio, aha good point, will do
[16:59] <elopio> thanks ale
[16:59] <elopio> alesage:
[16:59]  * knome serves elopio an ale
[17:02] <elopio> an ale sage. I'm not worth it.
[17:12] <alesage> elopio, I'm wondering now if "opio" means something?
[17:13] <elopio> alesage: it means opium.
[17:13] <josepht> +++
[17:16] <alesage> our team should have the best parties
[17:17] <elopio> it does. They have karaoke.
[17:17] <knome> i haven't heard any ales that are flavored with sage
[17:17] <balloons> do you karaoke knome >/
[17:17] <knome> nope
[17:17] <knome> sorry :P
[17:17] <alesage> neither have I now that you mention, maybe I'll try brewing one knome
[17:17] <knome> but i'll drink the ales for you...
[17:18] <knome> especially if you karaoke (:
[17:18]  * elfy notices the ping for ale ... 
[17:26] <balloons> lol.. it's teatime for me (already had a cup), but I suppose it's happy hour for you two
[17:26] <elfy> :)
[17:27] <elfy> I'll drink to your health
[18:09] <elfy> balloons: you seeing this ? http://ubuntuforums.org/showthread.php?t=2262798&p=13216826&viewfull=1#post13216826
[18:09] <elfy> I did last night when I booted it to check something else
[18:13] <balloons> elfy, I haven't but I was wanting to try an image this week. I'll keep it in mind when I try
[18:14] <knome> if you both didn't notice, i updated https://wiki.ubuntu.com/QATeam/Contact today
[18:14] <knome> and the header too
[18:14] <knome> some slight visual changes
[18:14] <balloons> Ohh home -> quality
[18:15] <balloons> knome, a big thank you.. if you lived any closer I'd send you some baked goodies. I'm afraid they won't be very tasty by the time they would get to you from here :-(
[18:15] <knome> hehe
[18:15] <knome> that's fine
[18:15] <balloons> I love the visuals.. good design is very nice :-)
[18:15] <elfy> knome: I did actually and I did a tiny little change to it actually :)
[18:16] <knome> i just noticed
[18:16] <elfy> I'll be looking at the manual testing pages again at the end of the week - try and get them all done and dusted
[18:18]  * balloons notes every main page fits in one screen.. no scrolling
[18:20] <knome> balloons, you have time for some hacking on the wiki?
[18:34] <dobey> http://pastebin.ubuntu.com/9902391/
[18:34] <dobey> balloons: ^^ any idea why i would be seeing the error on line 18 with the command being used there?
[18:34] <balloons> knome, sure
[18:35] <knome> balloons, i think the following pages can be deleted
[18:35] <knome> https://wiki.ubuntu.com/QATeam/BugDayFocus
[18:35] <knome> https://wiki.ubuntu.com/QATeam/BugSampling
[18:35] <knome> https://wiki.ubuntu.com/QATeam/DesktopBugMigration
[18:35] <knome> https://wiki.ubuntu.com/QATeam/ProposedTeamStructure
[18:35] <knome> https://wiki.ubuntu.com/QATeam/Resources
[18:36] <knome> https://wiki.ubuntu.com/Testing/DailySmoke
[18:36] <knome> EOF
[18:37] <knome> https://wiki.ubuntu.com/QATeam/AutomatedTesting seems to have a lot of good stuff, maybe it should be the default target for autotesting related stuff, instead of the wonky https://wiki.ubuntu.com/QATeam/ContributingTestcases/
[18:37] <knome> would propose to move/redirect that to https://wiki.ubuntu.com/QATeam/ContributingTestcases/Automatic to keep consistent with the structure
[18:39] <balloons> dobey, looking
[18:39] <knome> also unsure about the use for https://wiki.ubuntu.com/QATeam/Overview; it seems to duplicate content in various places... like yet another "FAQ" page
[18:39] <knome> especially, see https://wiki.ubuntu.com/QATeam/Bugs
[18:40] <balloons> the overview is a bit of faq
[18:40] <balloons> worthy of cleanup or removal
[18:41] <knome> it's too early to say if we need a separate FAQ page
[18:41] <balloons> bugs might be more useful.. I wonder if it's referenced anywhere
[18:41] <knome> balloons, apparently not
[18:42]  * balloons is nostalgic at https://wiki.ubuntu.com/QATeam/ProposedTeamStructure
[18:43] <balloons> I'm deleting the pages referenced
[18:43] <knome> okay
[18:46] <knome> what do you think of https://wiki.ubuntu.com/QATeam/Glossary
[18:46] <knome> do we really need a glossary that's so comprehensive?
[18:47] <knome> " black box testing: Testing, either functional or non-functional, of a component or system without reference to its internal structure. "
[18:47] <knome> that doesn't help me understand what black box testing is
[18:47] <knome> nor have i ever seen that term used in ubuntu quality
[18:48] <balloons> heh, that's pretty comphrensive. Ideally we wouldn't need it, but we do use QA specific terms
[18:48] <knome> wouldn't it be more useful to list only those terms that are actually used and try to link them with reality?
[18:48] <balloons> I'm not sure a gloassary is helpful or not in dealing with that issue however
[18:48] <knome> what about just linking to the source doc
[18:49] <knome> " exploratory testing: An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. "
[18:49] <balloons> indeed, it's linked
[18:49] <knome> this is like... very technical/lawyer text
[18:49] <knome> it's useless for a regular person
[18:49] <balloons> I imagine most definitions will also go beyond people
[18:49] <balloons> yes, defining the word with more qa terms helps nothing
[18:50] <knome> i would define ET as "testing where the tester tests the application(s) by working on their daily tasks"
[18:50] <knome> or sth...
[18:50] <knome> ok, i'll move the link to the source doc to FAQ, and redirect the glossary page there
[18:50] <balloons> dobey, so your log is interesting to say the least. Does using something besides qemu change things? does it work?
[18:50] <balloons> sounds excellent
[18:52] <dobey> balloons: i have no idea. i suspect not though
[18:53] <dobey> balloons: does jenkins use something besides qemu?
[18:55] <balloons> dobey, I can't say what jenkins uses, but you obviously can review the logs of the app in question to see the commands it's using
[18:56] <knome> balloons, https://wiki.ubuntu.com/QATeam/RequiredManualTests - is this at all up-to-date?
[18:57] <dobey> balloons: are any click packages having their autopilot tests run under adt-run in jenkins at the moment?
[19:02] <balloons> dobey, reminders should be
[19:02] <balloons> it's possible however they backed that out and used phablet-test-run anyway
[19:03] <balloons> best to talk to CI; plars and fginther
[19:03] <balloons> et la
[19:03] <balloons> knome, ahh, we should revamp that.. it's in the launchpad project now, tagged bugs
[19:04] <balloons> I'd delete the page and link there instead
[19:04] <dobey> :-/
[19:05] <knome> balloons, https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?field.tag=todo ?
[19:06] <balloons> knome, exactly
[19:06] <balloons> dobey, have you ever spoken to pitti about your difficulties?
[19:07] <knome> balloons, redirecting there now from the page
[19:08] <dobey> balloons: since he's in .de he's always already gone when i run into the problems. i was hoping knowledge about autopkgtest/autopilot was more spread out than just him
[19:09] <balloons> dobey, well heh, I've not been messing around with it recently but it always worked for me; I'm sure it still does. I did not mess about with qemu however, and only rarely the emulator. I was primarily interested in running on the device
[19:10] <dobey> i should probably write a lengthy e-mail complaining about the difficulty of having them, but meh, i don't want to build a bike shed
[19:10] <balloons> dobey, I mention pitti because you are hitting issues in pieces I'm not familar with, so it's hard for me to call it a bug or misunderstanding. Either way, you have discovered some "issues" along the way
[19:11] <dobey> balloons: well, qemu is how the jenkins jobs for the ubuntu packages run autopkgtests, so i was going with that, because most of the stuff i work on would have to fit in that infrastructure
[19:14] <knome> balloons, http://temp.knome.fi/qa/qawiki_diagram.svg
[19:14] <knome> balloons, that's still WIP and not complete, but i think it gives a great overview to pages that are "close" to the main branch in the QA team wiki
[19:14] <knome> balloons, the links mentioned here should be the #1 links to improve
[19:14] <balloons> ahh brillant
[19:15] <balloons> so I can trim down certain pages / combine them easily
[19:15] <knome> well at least you know which pages people will hit more often
[19:18] <knome> balloons, just updated the svg with some color...
[19:18] <knome> the green pages should be pretty much fine now
[19:18] <knome> the yellow pages are WIP
[19:20] <balloons> so what did you want to do with https://wiki.ubuntu.com/QATeam/AutomatedTesting? that page is interesting, although out of date
[19:20] <knome> i think that's a good base for the new automated testing stuff
[19:20] <knome> i would move it to QATeam/ContributingTestcases/Automatic once it's fleshed out
[19:21] <knome> i mean it's million times better than https://wiki.ubuntu.com/QATeam/ContributingTestcases/ already...
[19:22] <knome> and re: the diagram, i guess our goal is to get rid of all Testing/* pages too
[19:22] <knome> at least as links...
[19:22] <knome> so maybe that's another thing to consider :)
[19:25] <balloons> knome, I don't think anything is useful on https://wiki.ubuntu.com/QATeam/AutomatedTesting
[19:25] <balloons> after reviewing it
[19:25] <knome> aha...
[19:25] <knome> then i'll redirect it
[19:25] <balloons> knome, let's fix https://wiki.ubuntu.com/QATeam/ContributingTestcases/ then
[19:26] <knome> there are some subpages for that
[19:26] <knome> let me dig them up for you
[19:26] <knome> https://wiki.ubuntu.com/QATeam/ContributingTestcases/Index
[19:27] <knome> so i guess "Autopilot" it is only...
[19:27] <balloons> so we can ignore the manual stuff; elfy has good direction on tweaking that
[19:27] <knome> yep
[19:27] <knome> well except
[19:27] <knome> we'd like the tool in the repository
[19:27] <knome> so we didn't need to manage that in the wiki
[19:27] <balloons> yes, i assume he'll take care of that too
[19:28] <knome> probably not (:
[19:28] <balloons> one interesting thing / idea with contributing is that the tutorials are very similar
[19:28] <knome> also of potential interest: https://wiki.ubuntu.com/Testing/Activities/Index
[19:28] <balloons> for automated and manual even
[19:29] <balloons> I wonder if we could clean up our contributing testcases by making a nice generic tutorial / walkthrough somehow, but still giving specifics for the different options
[19:29] <knome> balloons, yeah... concerning the launchpad stuff
[19:29] <balloons> ahh you moved it :-)
[19:29] <knome> the work itself is very different
[19:29] <balloons> and consolidated, heh
[19:30] <balloons> the basic idea is the same; I remember not finding any good info ANYWHERE for using launchpad / bzr to contribute a merge proposal to a random project on launchpad
[19:30] <balloons> it's 99% the same for all of them
[19:30] <knome> yep...
[19:30] <knome> so we should write/gather a tutorial for that
[19:30] <balloons> so the fact we have that and cover it is kind of insane really
[19:30] <knome> i guess... https://dev.launchpad.net/UsingMergeProposals
[19:31] <knome> basically things you need to know are:
[19:31] <knome> 1) how to pull a branch
[19:32] <knome> 2) how to push a branch to a location that is valid for a merge proposal against the parent repository
[19:32] <knome> 3) how to do the actual merge proposal
[19:32] <knome> 1 and 3 are easy, 2 should be easy but will require explanation anyway..
[19:33] <balloons> precursor's to 1) include making an lp account, getting bzr installed on your machine, and getting bzr and lp setup on your machine
[19:33] <balloons> people get stuck before they even attempt pulling a branch
[19:33] <balloons> ohh and the ssh key thing, righto
[19:33] <knome> https://wiki.ubuntu.com/QATeam/DevelopmentToolsSetup
[19:34] <balloons> so setting up your lp account :-)
[19:34] <knome> covered!
[19:34] <balloons> yes, staring at the page. You took many subpages and consolidated them
[19:34] <knome> kind of
[19:34] <knome> and made it easier to look at
[19:34] <knome> so DevelopmentToolsUsage next? :P
[19:34] <balloons> so yea.. it's read and do https://wiki.ubuntu.com/QATeam/DevelopmentToolsSetup
[19:34] <balloons> then you can contribute to any project by doing 1-3 above
[19:36] <balloons> so I just wonder how we could compress https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual/Writing to assume the above
[19:36] <knome> i'll start the *Usage page
[19:36] <balloons> and is that "ok" / smart to do?
[19:36] <knome> what? :)
[19:37] <balloons> as I said the steps are all the same, the setup is the same. The details of what you do before proposing a merge proposal are the only things different between contributing
[19:37] <balloons> so we have several guides to contributing that cover the same things over and over
[19:37] <knome> i'll create that one common page
[19:37] <knome> so you can just link to that
[19:37] <knome> or tbe, first link to the setup page
[19:37] <knome> then the usage page
[19:38] <knome> then you can expect the user has everything set up
[19:38] <knome> and you don't need to worry about that side
[19:43] <knome> balloons, start: https://wiki.ubuntu.com/QATeam/DevelopmentToolsUsage
[19:45] <balloons> knome, I feel that that is a good idea.. I take it you agree :-)
[19:45] <balloons> should help elfy out too
[19:45] <balloons> buonasera Letozaf_
[19:45] <balloons> come stai?
[19:46]  * elfy will look later and see if it is actually simple or just simple from the point of view of you 2 ;)
[19:46] <Letozaf_> buonasera balloons  sto bene e tu ?
[19:49] <balloons> Molto buona :-) grazie
[19:49] <knome> balloons, https://wiki.ubuntu.com/QATeam/DevelopmentToolsUsage updated
[19:49] <Letozaf_> :-)
[19:49] <knome> balloons, just MP process left
[19:50] <balloons> knome, perhaps covering assigning bugs to you / merge proposals as well
[19:50] <knome> balloons, i'll do at least the MP process next
[19:52] <balloons> Letozaf_, so is shorts app still giving you issues?
[19:52] <knome> balloons, maybe you'll want to push a very general branch for ubuntu-manual-tests
[19:53] <knome> balloons, i'll use https://code.launchpad.net/~nskaggs/ubuntu-manual-tests/timeanddate as the example for now, but would probably be better to have a branch that is clearly used for illustration purposes (and to demonstrate a diff too!)
[19:54] <Letozaf_> balloons, yeah, I am trying to recreate the issue on my desktop, but test always passes on my desktop, looking at the video of the failure on Jenkings makes me think of a timing issue
[19:55] <balloons> knome, ohh like a complete example mp, diff, branch?
[19:55] <knome> actually, hold
[19:55] <Letozaf_> balloons, if I run autopilot3-sandbox-run -X -s 400x600x24  shorts_app.tests.test_rssreader.TestMainWindow.test_edit_topic shorts does not adapt to the 400x600 screen and it is cut off
[19:55] <knome> let's see if i can do this without referring to any existing branches
[19:57] <balloons> Letozaf_, ahh yes, you'll need a window manager
[19:57] <balloons> and, heh, my AP branch to land so the default autopilot sandbox has it
[19:58] <Letozaf_> balloons, oh, that's why :)
[20:00] <balloons> Letozaf_,
[20:00] <balloons> http://paste.ubuntu.com/9903609/
[20:01] <Letozaf_> balloons, thanks :)
[20:05] <knome> balloons, MPs covered at https://wiki.ubuntu.com/QATeam/DevelopmentToolsUsage
[20:06] <balloons> knome, you can use links for some of this.. ~ expands to there username, so code.launchpad.net/~ has there new branch on it
[20:08] <knome> *their :P
[20:08] <knome> but no, we can't really use links... because we don't know the branch name :P
[20:08] <dobey> you can link to just https://code.launchpad.net/~/ though
[20:08] <knome> and tbh, i usually rather use ~username than ~ to avoid confusion
[20:08] <knome> but we could add a note that they can also use that ^
[20:09] <knome> at least we have that tutorial in place now :)
[20:09] <knome> elfy, feel free to murmur at me if the page is hard to understand :P
[20:09] <dobey> well, i would do it as <a href="https://code.launchpad.net/~/">Your branches on Launchpad</a> or whatever, and avoid using usernames in things
[20:10] <dobey> or if you really want to use actual usernames, you can maybe do some funky JS with the launchpad API
[20:10] <knome> with the wiki... no js :P
[20:11] <elfy> knome: when I get to look properly I'll change things if they're not as simple as they could be ;)
[20:11] <balloons> yes, I think I did it by making the text say code.launchpad.net/~yourusername, and made it clickable is all
[20:12] <knome> balloons, dobey: happy now?
[20:13] <knome> elfy, ;)
[20:13] <knome> elfy, or you can murmur to me...
[20:13]  * dobey is never happy
[20:14] <elfy> knome: depends ...
[20:14] <knome> balloons, tbh, i think this is very low-level documentation... meaning that even other teams can use this as a documentation
[20:14] <elfy> mostly on how ridiculously voodooy the wiki is
[20:14] <knome> elfy, why not? you afraid of me biting you? :P
[20:14] <balloons> knome, :-) I offered only a suggestion. And yes, I agree it is very generic stuff
[20:15] <knome> so...
[20:15] <knome> need to fetch stuff for wife from the grocery store now
[20:15] <knome> bbiab
[20:15] <knome> -->
[20:15] <elfy> knome: not at all - you might want to be afraid of me biting you if you've made the page too difficult for members of the community to edit :D
[20:17] <knome> lol
[20:17] <elfy> :p
[20:17] <knome> elfy, the page is just as easily editable as any other page
[20:17] <elfy> go shopping :D
[20:17] <knome> whether the edits are good is a different thing
[20:17] <knome> haha
[20:17] <elfy> knome: yea ...
[20:17] <elfy> I've seen how easy the other pages are :|
[20:17] <knome> lol
[20:17] <elfy> :)
[20:17] <knome> no, that doesn't use that complicated markup
[20:17] <elfy> oh ok :)
[20:18] <knome> just those note boxes, which are relatively easy to understand
[20:18] <knome> that kind of stuff clearly isn't suitable for pages that aren't very static
[20:19] <knome> and the grumpy stuff you probably catched earlier on the wiki CSS is partly related to this... if we had access to easily do MP's for the CSS, we could drop most of the weirdo markup to begin with
[20:19] <knome> even from the main pages!!
[20:19] <knome> but...
[20:19] <knome> mrr.
[20:19] <knome> -->
[20:21] <Letozaf_> balloons, do not know if to be happy or not, but even with ap-sandbox shorts_app.tests.test_rssreader.TestMainWindow.test_edit_topic  the test passes on my desktop   :O
[20:27] <elfy> balloons: are we going to push the format script to the branch as it is?
[20:31] <knome> elfy, i can take care of that
[20:31] <knome> i guess we want to include some kind of README
[20:31] <elfy> yea
[20:32] <elfy> that said - there's no rush for it - so I might like to get my head around that
[20:32] <knome> sure
[20:32] <knome> works for me
[20:32] <elfy> might work for me too - who knows :)
[20:32] <knome> heh
[20:35] <balloons> knome, elfy ok, I'll let you guys handle it
[20:36] <knome> balloons, updated testwriter and developer role pages
[20:37] <balloons> Letozaf_, ohh excellent. so if it all passes in the sandbox, it should pass in jenkins
[20:37] <balloons> did you update it? it didn't pass for me
[20:37] <balloons> you should run it a few times as well of course to be sure
[20:38] <Letozaf_> balloons, I ran it without changes, that's the problem :P
[20:38] <Letozaf_> balloons, and yes I ran it more times, so I am a bit puzzled
[20:38] <balloons> Letozaf_, well notice on the mp.. sometimes it passes, sometimes it doesn't
[20:38] <balloons> Letozaf_, ohh..
[20:38] <balloons> it failed the first time for me
[20:38] <Letozaf_> balloons, I am trying to figure out why it's failing
[20:38] <balloons> is it running in the small screen now?
[20:38] <Letozaf_> balloons, even if I cannot reproduce the issue on my desktop
[20:38] <balloons> and I assume it is better than before.. it's passing a lot more often
[20:39] <Letozaf_> balloons, yes it's running in the small screen now
[20:39] <Letozaf_> balloons, but even if it fails only one time I assume it's not ok
[20:40] <balloons> Letozaf_, right, but improvement is improvement. So if you get stuck, I'll take the mp as improvement
[20:40] <Letozaf_> balloons, I will try a bit more and see what happens
[20:41] <balloons> Letozaf_, ok, I'll keep watching the mp
[20:42] <knome> elfy, are the two sober guys better at the header than the stoned one? :)
[20:43] <knome> or maybe those look stoned with nastier drugs :P
[20:43] <knome> not just alcohol
[20:43]  * elfy goes to look 
[20:44] <elfy> I guess so  ...
[20:44] <knome> :F
[20:45] <elfy> it's one of those visual things - looks like a stylised piston on a conrod to me :)
[20:45]  * knome shrugs
[20:45] <knome> i am not huge on the ubuntu pictograms either
[20:45] <knome> but...
[20:45] <knome> let's use them for now
[20:45] <elfy> yea
[20:46] <elfy> yep :)
[20:46] <dobey> what?
[20:46] <elfy> https://wiki.ubuntu.com/QATeam/Contact
[20:46] <knome> yeah?
[20:46] <elfy> the Contact icon in the header - piston on a conrod :)
[20:46] <dobey> that is a weird image
[20:46] <dobey> it's a hungry sloth
[20:46] <knome> oh heh.
[20:47] <dobey> or a platypus rather
[20:47] <elfy> ha ha
[20:47] <knome> balloons, what do you want to do with the qa subteams....
[20:47] <elfy> not seeing anything other than a piston now :(
[20:47] <dobey> doesn't look like a piston to me
[20:47]  * knome pokes elfy in the eye
[20:47] <knome> did that help?
[20:47] <dobey> but does totally look like a platypus
[20:48] <dobey> i've been looking at too many pistons and connecting rods lately for that to look like a piston to me :)
[20:48] <knome> balloons, wondering that they might be better at https://wiki.ubuntu.com/Teams
[20:48] <elfy> ha ha ha
[20:48] <knome> balloons, then link there...
[20:50] <alesage> veebers, I'm considering taking a reviews-break, want to pass along some helpful instructions :) , if you're second positive reviewer copy into mother-card; if rejecting push back to doing; forgive me if this is repetition :)
[20:51] <balloons> knome, the subteams are a bit weird to me
[20:51] <balloons> sure
[20:52] <knome> oki, will look at doing that
[20:52] <knome> mm, https://wiki.ubuntu.com/Teams already has qa
[20:52] <knome> so just expand that
[20:52] <knome> i guess
[20:52] <veebers> alesage: no worries. Please expand on "copy to mother card"
[20:53] <alesage> veebers, you'll find the mother card in "the big board" by number
[20:54] <veebers> alesage: ah right, so the results from the research cards goes into the 'write test' card
[20:54] <alesage> veebers, right right
[20:54] <elfy> knome: subteams page?
[20:54] <veebers> which isn't really the mother card (that would be the one that spawned the 1.2 million sub cards
[20:54] <veebers> (*note might not actually be that many cards)
[20:55] <knome> elfy, yes, moving the subteams to Teams
[20:56] <elfy> yea ... I got that - but is there a page with subteams on it? and what subteams? no idea there were any lol
[20:56] <knome> was in Contacts, i just snatched them :P
[20:57] <knome> actually, i'm not so sure of that
[20:58] <knome> i mean, moving them to the Teams page
[20:58] <knome> but i'm not so sure that they should be on the QA contacts page either
[20:58] <knome> maybe just a *simple* listing
[20:58] <knome> not a table form..
[20:59] <alesage> veebers, (* please consult with a physician before looking at this kanban board)
[20:59] <veebers> alesage: ^_^ (* your caffeine levels must be *this* high to enter this board)
[21:00] <alesage> ha
[21:01] <elfy> knome: oic ... ofc I know them lol - I think that's a mistake moving them from there
[21:01] <knome> yeah...
[21:01] <knome> though seriously, all teams except lubuntu have it coordinated through the main developer channels
[21:03] <knome> i'll try to formulate something sensible
[21:05] <elfy> I definitely think the qateam/contact page should have the list at the bottom still
[21:05] <knome> aha
[21:06] <knome> then i'll get it back... and refresh it :P
[21:06] <elfy> :)
[21:07] <alesage> veebers, elopio it's true that we need the oxide webdriver to introspect a webapp riiight?  asking because I'm working on a similar card atm
[21:08] <veebers> alesage: not sure sorry, never introspected a webapp
[21:09] <veebers> elopio: fyi I assigned you to card "SANITY-031" as I requested more info from JB. Not sure if that's the best way to do so
[21:25] <knome> elfy, maybe easier on the eyes now :)
[21:46] <elopio> veebers: yes, that's ok.
[21:46] <elopio> alesage: yes, webdriver is needed. There are some things possible from qml, but it's not nice.
[21:53] <veebers> elopio: can you re-link me that moztrap link you sent me earlier but I can't remember to find it? :_)
[21:54] <elopio> veebers: http://162.213.34.63:8000/manage/cases/?filter-status=active&filter-suite=1&pagesize=50&sortfield=created_on&filter-productversion=3&sortdirection=desc&pagenumber=1 ?
[21:54] <veebers> elopio: much appreciated thanks. Sorry for all the link asks
[21:55] <veebers> elopio: how did you tease that url out of moztrap? From what I see it likes to keep it's cards close to its chest
[21:55] <elopio> np
[21:56] <elopio> After you filtered, there is a link icon that shows you what i pasted.
[21:57] <elopio> It was hard to notice for me that it was a link icon.
[21:58] <veebers> elopio: ugh, I feel stupid now :-\ But instead I'll blame the application
[21:59] <elopio> :) i like the app. It just needs somebody to give it a little love.
[22:02] <veebers> elopio: I have 2 issues with it 1. the searching isn't fuzzy enough, 2. the url thing (makes it hard to link for other people etc.). Other than that it looks good (I don't really need to use it though)
[22:02] <alesage> elopio, I've started marking as "blocked" the stuff that needs attention, like in-limbo, not quite in-review
[22:05] <elopio> veebers: agree. I'd love to have time to fix it, and integrate it with our automated test results. But well, too late. That will be practitest, which I hope never to use.
[22:06] <elopio> alesage: that's good. Thanks.