Re: Hackathons for Saucy
okies :) I've just checked, meetingbot is still in #ubuntu-quality-chat :) Regards, Phill. On 22 May 2013 16:43, Nicholas Skaggs nicholas.ska...@canonical.com wrote: I prefer to keep things like this in the channel -- I like activity. It's over a long period of time so it's not like 15 people will suddenly be swarming the channel, while others are attempting to do something else. Besides, if your hanging out with us, you can be hacking :-p That said, I'm happy to change it if it becomes an issue. Nicholas On 05/21/2013 07:05 PM, Phill Whiteside wrote: Hi Boss, Please check if the ubuntu-classroom area is available, it means that others can discuss other QA / testing things during the hackfests and we have set of logs for people to follow that are purely dedicated to those areas. If the area is not, then I strongly suggest using the secondary ubuntu-testing room and checking that the meetingology bot is present to take notes so that a full log is available. Regards, Phill. On 21 May 2013 19:58, Nicholas Skaggs nicholas.ska...@canonical.comwrote: Ok, it's time to schedule our hackathons for this cycle. (For those not familar with the idea of a hackfest, have a look here: https://wiki.ubuntu.com/QATeam/Hackfest) I'd like to springboard the autopilot work ASAP, so let's plan one for this month. We had three last cycle, or about one hackathon every two months. I think we'll end up with a few more than that this cycle ;-) It's much easier to host and run them earlier in the cycle, so I would suggest the following date/times: May 23rd from 1200 UTC to 2000 UTC June 4th from 1200 UTC to 2000 UTC June 13th from 1200 UTC to 2000 UTC We can plan more fests after -- but let's start with this. Cadence testing should kick off sometime after the last session listed, so it would be good to get as much done in advance of that. Does the date and times work well for everyone? If not, we can change around one of the June dates listed, but I would really like to get the first one in this week. I know everyone is ready to dive in again (me too!)! With that in mind, is there a volunteer who would be willing to put together a wiki page for the May 23rd date, ala, https://wiki.ubuntu.com/QATeam/Hackfest/20130319? I think we can modify the table and drop the 'tester' column and instead instruct people to simply assign themselves the bug. The big things for the first hackfest is autopilot 1.3 stuff and doing manual testcase review and marking off some of the needed cases :-) Once the page is ready, and your feedback is in, we'll do an official annoucement for the first hackfest. Thanks everyone! Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality https://wiki.ubuntu.com/phillw -- https://wiki.ubuntu.com/phillw -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Hi
hi im samuel gabbay im 15 years old and i really want to test software and beta builds for the team. im currently learnign html but i would like to write bug reports and get involved in the team. :) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Hi
Hi Samuel, welcome to the group! There is a test case hackathon tommorrow from 12:00 UTC - 20:00 UTC in our IRC channel #ubuntu-quality[1] Feel free to pop along! Regards, Phill. 1. https://wiki.ubuntu.com/QATeam/Hackfest/20130523 On 22 May 2013 17:33, Samuel Gabbay samuelgabb...@hotmail.com wrote: hi im samuel gabbay im 15 years old and i really want to test software and beta builds for the team. im currently learnign html but i would like to write bug reports and get involved in the team. :) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality https://wiki.ubuntu.com/phillw -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Sikuli
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/05/13 17:38, Phill Whiteside wrote: Hi, this dropped into my inbox[1] May be of interest :) Regards, Phill. 1. http://www.webupd8.org/2013/05/sikuli-atomation-tool-using-images-100.html -- https://wiki.ubuntu.com/phillw Sikuli is a great automation tool it does however come with a few issues. 1. It uses jython which is based on python 2.4 iirc 2. The ide is slow but very usable 3. If an image changes at all your script no longer works 4. There were a bunch of old libs that it depended on that are no longer available (this may be different now with the 1.0 release) 5. There were a couple of features of the ide that work well in windows/osx that are a little hit and miss in Linux again this may of been addressed. - -- You make it, I'll break it! I love my job :) http://www.ubuntu.com http://www.canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGc9pkACgkQT5xqyT+h3OgQfgCgpCe9ShOtLvEifdIDu2O1QPPX is4An1ZNMAa4X5kV9jGYiHKYzvptSFE7 =SwYX -END PGP SIGNATURE- -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Test case writing
We actually evaulated this tool some time ago before moving forward with the qatracker. At the time it was still very much in development :-) We even discussed importing and/or an API we could tap into. Ultimately we decided against adopting the tool, but what we use is always up for discussion, provided there are folks passionate about a tool and willing to help make the conversion. That said I found the tool a bit overkill and not well suited to our workflow. It is neat to see how far they've come since I played with it last however -- a wonderful team of folks work on it from mozilla :-) Nicholas On 05/21/2013 06:18 PM, Javier P.L. wrote: On 21/05/13 at 11:02pm, David Morley wrote: Just a quick heads up about a great tool for writing manual test cases. Moztrap , Moztrap is a server side tool that provides a simple interface for writing test cases. Because of it's frame work it is easy to modify steps, add and remove steps and a nice way to mark off that you have run the tests. Wowo, very impressive, I'm a little bit jealous =P, just checked https://moztrap.mozilla.org/runtests out I'm pretty sure that the tests could easily be added to the current tracker as an accompanying technology but thought I would give it a shout out :-) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Cadence Testing for Saucy
On 05/21/2013 11:48 PM, Nicholas Skaggs wrote: [..] So, in summary, let's hear your feedback on: 1) Switching to the new idea for tracking packages all cycle Well we could give it a try for Saucy and see how it works. The availability of milestones outside of the designated cadence weeks sounds a good idea too. 2) Lumping the packages together or making a milestone for each one I prefer making a milestone for each package, it looks more neat and clear to lookup. If we do decide to switch, we'll need to create a list of packages we care about :-) Nicholas Carla -- Carla Sella email: carla.se...@gmail.com https://launchpad.net/~carla-sella http://qa.ubuntu.com/ -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Cadence Testing For Saucy (Craig Hrabal)
On 22/05/13 19:34, Craig Hrabal wrote: The mockups are pretty excellent. I would argue that the second choice is better, and combining them into one looks better visually. I think the packages we care about list should refer mainly to default pre-installed packages within Ubuntu, obviously with a few exceptions, as the intent is to make sure the packages that will ship by default in saucy are as stable as possible. +1 from me. -Craig Hrabal I'd suspect that not everyone will feel quite the same - other than us /all/ releasing good systems to the world at large, I'd much prefer that the packages we care most about related to Xubuntu ;) Message: all Date: Tue, 21 May 2013 17:48:22 -0400 From: Nicholas Skaggsnicholas.ska...@canonical.com To:ubuntu-quality@lists.ubuntu.com ubuntu-quality@lists.ubuntu.com Subject: Cadence Testing for Saucy Message-ID:519beba6.5010...@canonical.com Content-Type: text/plain; charset=iso-8859-1; Format=flowed So vUDS is behind us and it's time to solidify the cadence testing schedule for Saucy. I've update the cadence page with actual dates now, starting June 15th. See the schedule here: https://wiki.ubuntu.com/QATeam/Cadence/Saucy Now in addition to that, as part of the https://blueprints.launchpad.net/ubuntu/+spec/community-s-quality-coverage blueprint we discussed the idea brought up by crhrabal and smartboyhw (thanks guys!). The outcome was an idea to change the way we do cadence testing. The iead was to track all the packages that we care about for the entire cycle -- things like our list of default applications firefox, thunderbird, nautilus, etc. As a new build of the package is published to the archive a new build is entered into the tracker and all subscribers to that package are notified. I promised to mock up the idea, and that's what I'm including below for discussion :-) Let's step back quickly for a moment though. For those not familiar with last cycle's cadence testing, let me describe it quickly. Every cadence week we created a milestone and chose packages to test. In addition we always tested the daily images during that week, as well as sometimes including a bit of hardware testing against the milestone. The cadence milestone was only open for the cadence week, after which the results would be frozen. Onto the mockups for the new idea! I've laid out two examples of how we could implement the new idea. The first shows the idea of lumping all packages into one milestone; http://packages.qa.dev.stgraber.org/qatracker/milestones/252/builds. If you then view the history http://packages.qa.dev.stgraber.org/qatracker/milestones/252/history you can see every package we're tracking, test results, and bugs. Clicking on any old build let's you see the details as well. The second shows the idea of giving each package a milestone; http://packages.qa.dev.stgraber.org/qatracker/milestones/253/builds. If you then view the history http://packages.qa.dev.stgraber.org/qatracker/milestones/253/history you can see only that package, test results, and bugs. Clicking on any old build let's you see the details as well. So what does this new idea do for us? -- Let's us follow a package for the entire cycle, and provides bugs linked to versions, and allows you to 'track' the status of the package in ubuntu -- Provides a summary report of bugs specific to that package that we've opened -- Allows you to subscribe to a package you like/care about and make sure it's tested -- Allows you to filter test results / versions / bugs by time What I'm looking to gather now is if we should switch how we test our packages as part of our cadence testing to the new system. Let me describe how it would work. Each cadence week we would: -- Test the daily images -- (Optionally, when requested) Perform laptop/hardware tests against specific image -- Test the packages we're tracking and ensure results are entered for the current builds The difference is that the milestones would be availible outside of the 'designated' cadence weeks and thus you are free to test the packages at any time, as always, but you can also now report your results! The cadence weeks stay a rallying cry towards us committing to test regularly to ensure the archive, images and packages are in good shape all throughout the cycle. So, in summary, let's hear your feedback on: 1) Switching to the new idea for tracking packages all cycle 2) Lumping the packages together or making a milestone for each one If we do decide to switch, we'll need to create a list of packages we care about :-) Nicholas -- next part -- An HTML attachment was scrubbed... URL:https://lists.ubuntu.com/archives/ubuntu-quality/attachments/20130521/0726ad4f/attachment.html -- I'm in favour of the more detailed options. I assume that to be milestones for each package we want to follow. I'm in favour of switching to this idea. I assume that we'll be able to tailor
Re: Sikuli
Xpresser does similar work without some of the caveats. https://launchpad.net/xpresser On 05/22/2013 12:47 PM, Dave Morley wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/05/13 17:38, Phill Whiteside wrote: Hi, this dropped into my inbox[1] May be of interest :) Regards, Phill. 1. http://www.webupd8.org/2013/05/sikuli-atomation-tool-using-images-100.html -- https://wiki.ubuntu.com/phillw Sikuli is a great automation tool it does however come with a few issues. 1. It uses jython which is based on python 2.4 iirc 2. The ide is slow but very usable 3. If an image changes at all your script no longer works 4. There were a bunch of old libs that it depended on that are no longer available (this may be different now with the 1.0 release) 5. There were a couple of features of the ide that work well in windows/osx that are a little hit and miss in Linux again this may of been addressed. - -- You make it, I'll break it! I love my job :) http://www.ubuntu.com http://www.canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGc9pkACgkQT5xqyT+h3OgQfgCgpCe9ShOtLvEifdIDu2O1QPPX is4An1ZNMAa4X5kV9jGYiHKYzvptSFE7 =SwYX -END PGP SIGNATURE- -- Chris Gregan Project Quality Manager Professional and Engineering Services Canonical USA Inc. cgre...@canonical.com cgregan[irc.freenode.net] W-781-761-9448 1024/8806032D E70F 7391 6C78 9B9E 6461 1CC7 B168 E1E7 8806 032D -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Hi
Great to have you on board Samuel Gabby. You are going to have a lot of fun :-) On Wed, May 22, 2013 at 12:33 PM, Samuel Gabbay samuelgabb...@hotmail.comwrote: hi im samuel gabbay im 15 years old and i really want to test software and beta builds for the team. im currently learnign html but i would like to write bug reports and get involved in the team. :) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Hackathon Tomorrow (May 23rd) 1200 UTC to 2000 UTC in #ubuntu-quality
Hi Nicholas, I tried testing all the existing autopilot scripts from trunk on my dev box running quantal 12.10 updated today morning after I pinged on the irc. autopliot 1.3 was built after disabling lttng option. Based on initial experience I guess I may have to create a guest image for latest build and try again. This is what I got on my dev env. both these appeared to go through -test_firefox -test_evince tests that failed - RuntimeError:Unable to find Autopilot interface -test_gedit -test_nautilus -test_shotwell -test_totem all these launched the respective apps and no further interactions. Did not run test_fileroller - the app is not working (after system update); can not create new archive of any type on my computer - this has nothing to do with autopilot . I have a screen shot of error, can post it if required. These are the lingering questions that I have for tomorrow's meeting: In setUp which should be used to launch target app? What is the criteria ? The scripts currently use one of the three: self.launch_test_application(appname) or self.start_app_window(appName) or self.mgr = ProcessManager.create(BAMF), self.mgr.start_app_window(appname) From where or how can we get the IDs of child windows/icons/buttons/labels etc? (in select_single etc) These are used to select/click/enter text on target windows in several test cases after getting a proxy object. Thanks, Vasudevan Vasudevan Kottilil On Wed, May 22, 2013 at 8:45 AM, Nicholas Skaggs nicholas.ska...@canonical.com wrote: Ok, so it sounded like most people are going to be able to make the quickly scheduled Hackathon. So, without further ado, tomorrow in #ubuntu-quality from 1200 UTC to 2000 UTC we'll be hacking on testcases. Hurray! https://wiki.ubuntu.com/QATeam/Hackfest/20130523 Our goals are: Re-organize the ubuntu-autopilot-tests trunk so known good tests are separated from those that are a work in progress Complete review of the manual testcases and bugs in ubuntu-manual-tests Migrate all the ubuntu-autopilot-tests testcases to autopilot 1.3 Clean up the old autopilot documentation and resource links from autopilot 1.2 to autopilot 1.3 See everyone tomorrow! Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Hi
Hey Samuel, Welcome to the club! You're not the only young person around: I'm 17. John Kim On Wed, May 22, 2013 at 9:33 AM, Samuel Gabbay samuelgabb...@hotmail.com wrote: hi im samuel gabbay im 15 years old and i really want to test software and beta builds for the team. im currently learnign html but i would like to write bug reports and get involved in the team. :) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
