=== yofel_ is now known as yofel [02:28] stgraber: any ideas what could be causing this : http://paste.kde.org/699548/ [02:29] it also happens with any other mirrors I try [02:48] I guess the container's DNS is shot? [03:15] shadeslayer: it appears happy with archive.ubuntu.com though [03:42] stgraber: not really [03:42] stgraber: http://paste.kde.org/699572/ === balloons changed the topic of #ubuntu-quality to: Welcome to Ubuntu Quality | http://wiki.ubuntu.com/QATeam | Cadence Weeks: https://wiki.ubuntu.com/QATeam/Cadence/Raring/ | Hackfest March 19th! https://wiki.ubuntu.com/QATeam/Hackfest [05:41] Good morning [07:47] good morning [07:50] good morning [07:50] salut jibel [07:50] salut dholbach === yahska is now known as site_admin === codero is now known as _ak_ [11:48] ./quit [11:48] <_ak_> jacksonisaac: are you there ? [11:50] <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [11:50] <_ak_> <_ak_> [79f33d52@gateway/web/freenode/ip.121.243.61.82] has quit [Client Quit] [12:01] <__bot__> jacksonisaac : Are you willing to contribute? [12:01] Yes [12:01] What can I do? [12:01] hey all [12:01] <__bot__> Which is your field? [12:02] Ubuntu Desktop amd64 here. [12:06] Programming [12:06] Algorithms [12:15]

l [12:26] shadeslayer: you're missing a /ubuntu in the deb URL there [12:26] shadeslayer: http://archive.ubuntu.com/dists/quantal/main/binary-i386/Packages should be http://archive.ubuntu.com/ubuntu/dists/quantal/main/binary-i386/Packages [12:48] where is the best place to upload Hardware Profile? === _salem is now known as salem_ [13:17] roadmr: can you point me to a page where it explains how to run the checkbox wifi tests? [13:17] roadmr: not how to set up the router, but how to actually run them [13:17] gema_: hello! [13:17] roadmr: or better yet, where can I have a look at the source code :) [13:17] gema_: sure, let me find something for you [13:17] roadmr: thanks [13:17] gema_: oh that's easy :) the actual command that gets run is in a job file, those are in /usr/share/checkbox/jobs [13:18] gema_: you'd be looking at wireless.txt or suspend.txt (for the before and after suspend tests) [13:18] roadmr: ack, is that on any raring machine? [13:18] gema_: yep, it should be [13:18] ok [13:19] gema_: the command first creates the connection: /usr/share/checkbox/scripts/create_connection [13:19] $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK [13:19] gema_: then it runs the usual internet_test script: [13:20] /usr/share/checkbox/scripts/internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'` [13:20] gema_: it has a trap to ensure that the connection is deleted at the end, but this I just posted is the meat and potatoes of the test [13:20] roadmr: ack [13:20] gema_: and of course you can have a look at the scripts it uses [13:21] ok, I will try [13:21] thanks for your help [13:21] gema_: two things: this has to run as root, and the $WPA_* variables need to be defined [13:21] gema_: no problem, let me know if you run into trouble, either I or brendand can help [13:21] ok [13:21] roadmr: do you have a script to define those variables? [13:22] roadmr: ohh, you mean my network details [13:22] roadmr: gotcha, no prob [13:22] gema_: yes :) $WPA_BG_SSID is your network's SSID or name [13:22] roadmr: ack x) [13:23] gema_: if needed, $WPA_BG_PSK is the password (only needed if --security=wpa, the other option is --security=open) [13:24] gema_: if you look at monitor_wireless_connection, this uses iperf to do actual bandwidth measurements [13:24] gema_: for this to work you need to also set $SERVER_IPERF pointing to another system on the network running iperf, instructions for setting up the iperf server are in the wiki document I sent you [13:24] roadmr: ok, I have that one [13:27] balloons: hey, on https://blueprints.launchpad.net/ubuntu/+spec/community-1303-quality-ubuntuphone it looks like you have a work item for me that was really just a comment that I added, or was there something in that item that you intended for me to do? [13:28] balloons: iirc I was just pointing out that there were bug guidelines for that project already, because someone asked if there were guidelines for people wanting to file new bugs [13:29] hi guys! happy hackfest [13:30] plars: hey! :) [13:30] hi zyga [13:31] heyy! [14:02] hi folks, if anyone is using kvm for testing, is there a quick way to recover a reference image other than untar'ing a tarball or virsh snapshot-recover? [14:08] plars, I don't see any work item for you on that blueprint [14:08] mean, not in the work items feld [14:13] balloons: you're right, I was looking at the "work item" section in the whiteboard and didn't scroll down to the new and improved work items section of the blueprint [14:20] roadmr: do you have any nexus devices in the lab that you can use for testing? [14:21] gema_: nope, I don't :/ only a bunch of old laptops haha [14:21] gema_: brendand has a nexus 7 but it's not in a lab [14:21] roadmr: if we lent you one , could you run the wifi tests on it? [14:22] roadmr: and if so, who would be the contact person to deal with? [14:22] gema_, could someone help us getting it set up to auto deploy the images? [14:22] gema_: sure, we can do that, I can be the contact [14:22] brendand: nope, this would be a manual activity [14:23] roadmr: I need someone that can phisically get the device and run the tests on it [14:23] roadmr: as well as flashing it with the ubuntu image and the tablet image [14:23] gema_: I'm in the office/lab every day so I can do that [14:23] roadmr: do you live in lexington? [14:24] gema_: no, Montreal, but we also have a lab here with wireless testing stuff [14:24] roadmr: oh, ok, I thought your wireless lab was in lex [14:24] gema_: if you prefer Lexington then maybe we can convince spideyman to help [14:24] roadmr: I think it'd be easier [14:24] gema_: we have three wireless testing setups, one for each certification lab: Lex, Montreal and Taipei [14:24] roadmr: gotcha [14:25] roadmr: let me see if we have some hw we could use for this [14:50] hi, since this is supposed to be some hackfest today, I hope someone is around to help me :-) [14:50] PulseAudio upstream has an automated test suite [14:50] diwic, hello :-) [14:51] pitti, jibel do you guys know about the pulseaudio upstream tests suite? [14:51] I figured I should have it running as part of the -proposed stuff before it migrates over to the dev release [14:51] But I don't know where to start really [14:52] can you point out where the test suite lives? I'm assuming in there source repo somewhere [14:52] this is an autopkgtest rather than autopilot, right? [14:52] balloons, it's run by "make check" IIRC, or possibly "make tests" [14:52] diwic, yes, autopkg [14:53] diwic, hi, there are some guidelines in http://developer.ubuntu.com/packaging/html/auto-pkg-test.html [14:53] balloons, ok, so "make check" runs some tests it seems like [14:55] diwic, you'll need to add to your package a debian/tests/control file that describes the test dependencies and test executable and add a test executable in debian/tests/ [14:55] hmm, 1 of the 30 tests failed [14:56] in your case it would be a shell script that calls "make check" I guess [14:57] jibel, how does the test environment determine if "make check" was successful? [14:57] diwic: the most important point of that is to tell it to run against the system-installed pulseaudio instead of against the built source tree [14:57] diwic: can it do that? [14:58] pitti, I would typically say no, but can you explain why? [14:58] diwic: oh, and as a step even before that, I guess it shoudl run during package build, and make the build fail on test failures [14:59] diwic: that's the point of autopkgtest, to test the actually installed system instead of a build tree [14:59] diwic: this catches packaging errors (missing to install some files, etc.), changes in dependencies, and we can run it if a depending library changes [15:00] pitti, so running an upstream test suite shouldn't be an autopkgtest ? [15:00] pitti, the test does stuff like mixing stream 1 and 2 and checking that the result is correct [15:00] diwic: no, it's desirable to also run as autopkgtest, but it needs to run differently then [15:00] diwic: but usually the two have a different focus [15:01] diwic: so if we can make the upstream test suite run as autopkgtest we should do so [15:01] pitti, the test suite makes ~30 executables I believe. We don't install them. [15:01] but in many cases that's not easy to do [15:01] diwic: that's fine -- autopkgtest can still build your package to build the actual tests [15:02] pitti, now it sounds even more confusing. [15:03] diwic: so, step 1 should always be to fix "make check" and run it in debian/rules during package build [15:04] so that packages which regress on some architecture or due to a build dep change don't build and get into the archive at all [15:04] upstream test suites usually cover the fine details of funcionality [15:04] pitti, Ok, so far I follow. Can we make that optional somehow? [15:04] if that's covered during package build, then autopkgtest only needs to do some general smoketest to guard against packaging errors [15:04] pitti, if the test suite takes a minute to execute or so [15:05] such as calling paplay, ensuring that the daemon started, etc. [15:05] doing that is usually much easier than convincing "make check" to run against the system binaries (although this often isn't all that hard) [15:06] but if we can run the upstream test suite against the packaged/installed pulse, so much the better of course [15:07] pitti, I don't think it makes sense to run this test suite against the installed packages. They are free executables, making no use of libpulse etc. [15:08] diwic: ok, so they seem better during package build then [15:09] diwic: we might have an autopkgtest which just does a coarse "paplay" call with a dummy backend or so, to test triggerig of the daemon, installation of paplay and pulse, etc. [15:09] and a compile/link/run test against libpulse can't hurt either (to cover correct installation of headers, pkg-config, etc.) [15:09] pitti, ok [15:10] pitti, where will this autopkgtest be run? In some kind of vm? [15:10] diwic: yes, we create a server-like VM for each test run [15:10] tests have full root, can install any pacakge, etc. [15:11] pitti, is this what the "run-adt-test" command does? [15:12] pitti, but I assume the tests do not have access to real hw resources, such as sound cards? [15:14] diwic: right, prepare-testbed builds a VM, run-adt-test runs it in that VM [15:14] diwic: I'm not sure; kvm does emulate a simple sound card, so it could use that [15:15] pitti, oh, so it uses KVM internally === Ursinha_ is now known as Ursinha [16:03] balloons: webcam step removed. [16:03] xnox, you dropped the webcam screen on ubiquity? [16:03] balloons: yes. [16:04] nice.. I'll open a bug for it to get our testcases updated [16:04] starting with today's daily or tomorrow's? [17:02] Whew, busy day.. anyone else hacking on something? [17:03] might be quiet in here till the European folks have a chance to get home :-) [17:08] balloons: I'm now back and in lurking mode. There may be gaps in replying as it nearly evening meal time here. But I will get back to anyone who pings me. [17:15] balloons, Im working on bug 1154750 [17:15] bug 1154750 in Ubuntu Manual Tests "Test Needed: Ubuntu Software Center" [Medium,In progress] https://launchpad.net/bugs/1154750 [17:15] phillw, \o\ [17:15] SergioMeneses, :-) [17:16] balloons, I have a preview now... give a minute [17:17] balloons: / stgraber ubuntu-gnome is lot listing any builds on http://iso.qa.ubuntu.com/qatracker/milestones/243/builds although it does now appear on the 'Filter' list on the Left Hand Side. [17:17] s/lot/not [17:18] lunch time... I'll be back soon [17:24] phillw: that's because the ISO tracker wasn't asked to publish any daily since I created the product on it [17:35] stgraber: okies, so they will appear next cron-build? [17:41] phillw: probably. There's currently a bug on the cdimage build machine preventing them from publishing [17:44] okies, thanks for the update :) [18:09] hello, I am assuming this is the hackfest date,right? === cprofitt_ is now known as cprofitt [18:16] sak, you're right [18:20] balloons, take a look http://people.ubuntu.com/~sergiomeneses/sandbox/1497_Software%20Center%20Tests [18:20] hey sak [18:20] SergioMeneses, I'm looking [18:20] this looks really nice [18:21] balloons, I need to do: how to buy apps [18:21] hehe.. umm.. there are 'free' apps to buy, I'd use those [18:21] this testcase is huge [18:22] yes it is.. [18:22] balloons, what do you mean? [18:22] for instance, you can purchase command and conquer [18:22] and it costs $0 [18:22] :O [18:22] jejeje really [18:22] yea [18:24] hey ballons [18:25] balloons, seems easy, long but easy [18:25] sak, got something to hack on? need some help? [18:26] ballons, need help setting up manual test. the process is still a bit confusing [18:27] SergioMenesesif the test case is 'huge', you may want to think about splitting it down into smaller 'sub-tests'. I'm not sure if balloons has posted up the pcmanfm suite I sent him yet, but that would give you some sort of idea as to doing so. [18:28] sak, sure.. what test are you thinking about writing? [18:28] phillw, yes, your pcmanfm suite :-) Are you going to make a merge proposal for it [18:28] today is the day my friend! [18:29] phillw, I'm doing that ... even I have a chart [18:29] SergioMeneses, phillw is correct.. We've gone back and forth on how we approach things.. it's a choice to split or not.. for example, unity has many cases split into high level categories [18:30] for unity having all those cases in one doesn't make sense, but neither does having so many seperated [18:30] Breaking down the software center stuff into say a core testcase and then another testcase might make sense [18:30] I'll take a picture of my chart and share it with you jejeje [18:30] for instance, testing the software sources, etc, maybe goes in the secondary testcase [18:31] I want to right a testcase for usd-creator-gtk, since I have high value for this program, ballons [18:33] plus, i could us a crash course in bzr [18:34] sak, awesome. so I take it you have seen the tutorial on the wiki / youtube.. the youtube video goes way beyond the wiki.. it's very visual: http://www.youtube.com/watch?v=VO7DdlUSt_4&feature=youtu.be [18:34] sak, but of course, you've got me live to help you [18:34] videos \o/ [18:34] so the first thing you need to do is make sure your setup for launchpad [18:34] balloons, is a youtube star :D [18:34] you have an account right? can you link me to it? [18:35] SergioMeneses, lol.. yep.. 7 videos.. I'm a star! [18:35] i have a launchpad account, you want the link, ballon? [18:35] sak, we'll make sure you have an ssh key setup, then we can make sure you have bzr and launchpad on your box [18:35] sak, sure [18:36] i have kubuntu raring installed a bare metal. so in will use ot for the test [18:37] k.. so 'sudo apt-get install bzr' if you haven't [18:37] i setup the ssh key on debian, is that going to cause issues? [18:38] sak, no. just make sure it's attached to your launchpad account [18:38] https://launchpad.net/~/+editsshkeys [18:38] k [18:38] if you can bzr launchpad-login YOURNAME [18:38] and bzr whoami returns you, your all set :-0 [18:39] phillw, you should hop in here also mate! [18:42] sak, let me know if you hit any snags, or if your set up to now [18:47] zak at any rate, that was the hard part.. From there you can simply checkout the tests we have by branching [18:48] bzr branch lp:ubuntu-manual-tests [18:48] ballon, what is YOURNAME? Is this my profile name or my launchpad name? [18:48] sak, your launchpad id [18:48] ok [18:48] for me, it's nskaggs [18:49] https://launchpad.net/~nskaggs [18:51] sak, things work for you? [18:51] once you've set this up once, you don't have to do it anymore.. so it's all downhill from here [18:52] i did this but, bzr said, "saqman2060" does not seem to contain an email address. this is allowed but not recommended [18:52] balloons, phillw sak look http://people.ubuntu.com/~sergiomeneses/sandbox/tests-softwarecenter.jpg [18:52] SergioMeneses, think that deserves some sharing [18:53] i want that pen! [18:53] balloons, jejeje [18:53] I'm going to do a post and put it there :D [18:53] awesome! [18:53] I'm happy to reshare.. it's a nice photo.. I like the objects in it [18:53] well done [18:53] :) [18:54] sak, weird.. if it works though :-) [18:54] sak, so.. now you can move to the fun stuff [18:54] go ahead and branch the code and you'll get a copy of our tests on your machine [18:54] bzr branch lp:ubuntu-manual-tests [18:55] from there it's just a matter of making and editing files.. when your all done, it's a couple bzr commands to push it back to launchpad.. once you do one, you'll have it done. [18:55] *done=down [18:56] SergioMeneses, btw, you play guitar? [18:56] * balloons talks a quick offtopic detour [18:56] that is "bzr branch lp:ubuntu-manual-test" this is the right command? [18:56] balloons, no I don't jeje but I found it in UDS-R [18:56] sak, yes it is [18:57] sak, this page lists it: https://code.launchpad.net/ubuntu-manual-tests [18:57] it also gives you the push command you need to push your stuff back to launchpad when your done [18:57] see it? [18:57] in the bar to be more specific [18:57] SergioMeneses, ah-ha.. it's pretty cool [18:58] * balloons switches back to on-topic :-) [18:58] jeje yes it is [18:59] yes I see it [19:00] excellent.. So your all set up.. So now, it's just about writing the testcase [19:00] so you should see the new ubuntu-manual-tests folder.. did you go browsing around it and see the current tests? [19:01] for your software center test, it's a 'package', not hardware or an image :-) [19:02] so make a new file in the 'packages' folder and title it something like 'startup disk creator' [19:02] i think i have a problem with my ssh key. i am using irc on my phone, lol. switching to desktop [19:03] sak, lol.. ok, I'll wait for you to come back [19:03] has anyone else been testing Unity Lenses ID:1448? if you try click the search icon on 'home lens' its flashing random icons like calculator and audio for a split second Ill report it as a bug if so. =) [19:05] been following the instructions you guys gave sak . Works great. Think i'll test Gwibber if its available. [19:06] baudtrap, yep indeed it is [19:06] fetzed, weird... which step are you getting that in? [19:07] baudtrap, let me know if you need any help :-) [19:07] cool ;) [19:09] ok, balloon, I am back, I hope [19:09] At the start I clicked on the Search Icon messing about and noticed it, It was not during any steps I was playing about with it after install [19:10] im going to re create to see if its just a dodgey install [19:10] fetzed, <3.. you've got it down my friend [19:10] yep, if you can recreate, file a bug. I don't see it.. when you file, mention your graphics card / driver if it comes up again.. [19:10] it might be some weird rendering bug with your combination [19:11] sak_, :-) ok so ready to start on the test then? [19:12] Almost, ballon, but first I have to check my ssh key. This was the error I got trying to branch the code: "The authenticity of host 'bazaar.launchpad.net (91.189.95.84)' can't be established. [19:12] RSA key fingerprint is 9d:38:3a:63:b1:d5:6f:c4:44:67:53:49:2e:ee:fc:89. [19:12] Are you sure you want to continue connecting (yes/no)? yes [19:12] Warning: Permanently added 'bazaar.launchpad.net,91.189.95.84' (RSA) to the list of known hosts. [19:12] Permission denied (publickey). [19:12] ConnectionReset reading response for 'BzrDir.open_2.1', retrying [19:13] Permission denied (publickey). [19:13] bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist" [19:17] sak_, hmm [19:18] sak_, well if your not opposed to it, you could just generate a new key.. For now though, we can work on the testcase if you wish and go back to solving that issue [19:19] sak_, when you said you generated the key on the debian box, did you ssh copy the pub and key files over to your ubuntu box? [19:19] balloons, It appears that I do not have a private key on my kubuntu system, and the system that I used to create the private key, no longer exists :-) [19:19] Balloons, No :-( [19:19] sak_, lol.. see my reply above.. :-) Ok, then yea, let's just make you a new one [19:19] LOL [19:20] in the process of doing that [19:20] sak_, ok.. there's thing page if you need it: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Launchpad [19:23] thanks [19:30] meh... looks like my bug is a bug :( [19:33] Yes, IT WORKED. But I could not branch it in the dir I created because I created it with root. I I just branched it to profile folder [19:35] balloons: we've just had evening meal and I have found out today that the catalog stuff I have done has the wrong border settings for the printer :'( [19:35] phillw, :-( [19:35] sak_, yay! [19:36] fetzed, :-( That's good though too.. report the result and they can get to fixing it :-) [19:36] ok, did not see the startup-disk-test so this I am going to write and push to the branch [19:36] it happens, just means altering 10 pages of spreadsheet type entry and their associated images. [19:48] hey Letozaf_ [19:48] balloons, hey [19:48] Balloon, I just pushed an testcase to the branch /ubuntu-manaul-test/usb-creator-gtk [19:48] sak_, great, let me take a look [19:49] sak_, ok, so you see your branch on the page now? https://code.launchpad.net/ubuntu-manual-tests [19:49] if you click on it you can browse and propose it for merging [19:49] yes i do [19:50] however, you'll notice your changes are in there [19:50] Working on formating my testcase. Whats the proper way to indicate a success or a bug? [19:50] see the last revision? [19:50] sak_, so what you need to do is issue a bzr commit before you push [19:50] now, in order to do that let's review a bit of bzr commands [19:50] you made a new file that bzr doesn't now about [19:50] ok [19:51] i did [19:51] you can check this out by issuing bzr status [19:51] what does it say? [19:51] baudtrap, you mean an expected result? [19:51] nothing [19:52] what does 'bzr log | more' show? [19:52] does it show a revision 47 you committed? [19:53] baudtrap, if you haven't seen this pages, they should help; https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide; https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual [19:54] Balloon, did I do something wrong [19:54] ballons, oh yes. thanks, that helped. [19:56] sak_, :-). Not sure what happened.. But here's what you should do in order to get it up on launchpad quickly [19:56] bzr branch ... [19:56] bzr add FILENAME [19:56] bzr commit [19:56] bzr push [19:57] sak_, make sense? [19:58] In this order, with only these commands? I get the branch command, What filename am I adding? [19:58] sak_, you made a new test right? [19:58] balloons maybe this can help http://doc.bazaar.canonical.com/latest/en/user-guide/index.html [19:59] yes, balloon [19:59] sak_, great. So in order for bzr to include that in the repository, you have to use the bzr add command [19:59] so issue a bzr add with the path to the new file you made [19:59] k [20:00] SergioMeneses, :-) thanks [20:00] balloons, you haven't had time to look at the File-roller autopilot test have you ? [20:00] Letozaf_, \o [20:00] SergioMeneses, \o [20:00] no, but since your here, I can do whatever.. I'm here for whomever is hacking today :-) [20:01] balloons, File-roller or Thunderbird :) === yofel_ is now known as yofel [20:04] ooops balloons did I report that bug in the wrong place? [20:04] Letozaf_, you pick :-) What you wanna hack on? I guess tb is kind of out unless I can make something magic right [20:04] fetzed, you used ubuntu-bug right? [20:04] ye [20:05] balloons, yeah! so lets hack File-roller :) [20:05] fetzed, yea, normally that's how we like to report bugs.. for these call for testing sometimes they ask us to report them in a special way [20:05] this is one of those times :-) [20:05] http://packages.qa.ubuntu.com/qatracker/milestones/262/builds/40142/buginstructions [20:05] in general, checking the bug reporting link is a good idea :-) [20:05] ahh thats alright then <--- QA noob [20:06] no worries..I actually updated it.. originally I had ubuntu-bug in there.. and changed it after like 10 mins due to the team asking me to do so [20:06] they want to track things differently [20:07] so we'll pretend you saw it in those 10 mins.. how's that :-p [20:07] Letozaf_, sure thing.. [20:07] SergioMeneses, gonna push a merge request for your testcase? [20:07] sak_, how's it coming? [20:08] :P [20:08] not good. I am using the add command, but I all I get is "workingtree does not exizt". [20:08] sak_, ahh.. you need to be inside the folder you checked the code out of [20:08] else your bzr stuff will fail [20:08] balloons, we need to work on the "buy apps" part first, or not? [20:09] SergioMeneses, you can if you wish.. but you can also add it in later and merge it :-) [20:09] We are allowed to update existing testcases.. [20:09] they are never 'done' :-) [20:10] having a test that test 5/10 features is better than no test :-) [20:10] but what you've written is already so nice.. it covers most of it [20:10] Letozaf_, ok, so i'm having a lok [20:10] balloons, perfect then [20:11] so I think we can merge this part... we only have to do a small part of the process [20:11] balloons, the problem is I cannot make autopilot click on the 'Add files' button, I also tried using the menu items, but it doesn't work [20:11] Still not working balloons, I am in the package folder of ubuntu-manual-test [20:12] Letozaf_, just ran it.. I see that [20:12] let's take a look at the code shall we? :-) [20:12] balloons, yes of course! [20:13] sak_, ok, so your in the root folder.. and issuing the commands are failing? [20:13] yes [20:14] ohh.. right.. so bzr add testname gives working tree error [20:14] weird [20:14] what path should I be inputing [20:14] go up to the ubuntu-manual-test folder [20:14] and type bzr add * [20:14] that will add everything underneath is [20:14] baudtrap, how's it coming for you? [20:15] so Letozaf_ i see you have a find in there [20:15] is there another way to find the button - how exactly is it failing? [20:15] I mean, it didn't click it for me :-) [20:15] but I wonder if it's finding it [20:16] balloons, I tried also using the menu item instead of the button [20:16] i'm going to go look in the introspection tree [20:16] balloons, but did not work [20:17] balloons, yes now I am trying to use label="Add Files" but I think I had already tried and it did not work [20:17] Letozaf_, let's go after the label [20:17] lol.. that was my thought.. I'd start with the label [20:18] ohh [20:18] I see the 'Add Files' label [20:18] but I would use the name [20:18] Add_Toolbar.. that won't change with locale [20:18] balloons, doesn't work, same problem (I mean the label) [20:18] you see it? GtkToolButton, name=Add_Toolbar [20:18] balloons, oh! fine let me try [20:19] if not, there's several other ways we can define it probably.. [20:19] ballons, So i reviewed the '1332_Online Account Gwibber' testcase and had two unexpected results. Do i append those in the file or do i make my own file? [20:19] I believe! [20:19] balloons, done [20:19] https://code.launchpad.net/~sergiomeneses/ubuntu-manual-tests/ubuntu-software-center/+merge/154192 [20:21] balloons, :( name does not work either :( [20:21] baudtrap, if the testcase is out of date update it.. no need for a new file. If it's not and you want to expand it, go for it.. that testcase is specific to the online integration pieces of gwibber.. rather than gwibber itself, though there may be overlap [20:22] Letozaf_, so GtkImage, stock=add-files-to-archive [20:22]