archive-info.com » INFO » H » HSKUPIN.INFO

Total: 368

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Firefox Automation report – week 13/14 2014 | hskupin.info
    discovered even more Flash crashes of the same type we decided to use the debug version of Flash on our Windows systems Main reason is that those builds don t crash Sadly given that they would give us way more information But Adobe should at least know where the crash is happening Also given that we do not have any private data on our test machines we decided to actually upload a minidump from one of those crashes to Bugzilla This information actually helped Adobe a lot So we will continue doing that Last but not least Henrik was able to fix another 7 bugs for TPS Those were broken tests a broken behavior of the TPS test extension or enhancements Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 13 and week 14 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 13 and week 14 automation ci firefox firefox automation mozmill testing Post navigation Previous Post Firefox Automation report week 11 12 2014 Next Post Automation Training Day on May 21st Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 3 Replies 0 Comments 3 Tweets 0 Facebook 0 Pingbacks Last reply was May 9 2014 EdgarsLabRat View May 9 2014 moz Henrik Skupin Firefox Automation report week 13 14 2014 http t co vjIVou1H00 Reply Planet Ateam View May 9 2014 Henrik Skupin Firefox Automation report week 13 14 2014 http t co LqtduTp1cF Reply planetmozilla

    Original URL path: http://www.hskupin.info/2014/05/09/firefox-automation-report-week-13-14-2014/ (2016-05-01)
    Open archived version from archive


  • ci | hskupin.info | Page 3
    weeks in January Highlights With the new year our team has been reorganized and we are part of the Mozilla QA team again That means we will have a way closer relationship to any feature owner and also working towards in bringing more automation knowledge to everyone The goals for our team are getting worked out and I will present those in one of my following blog posts As of now you can find our team page on the Mozilla wiki under Firefox Automation Since the landing of all the new features for Mozmill CI on our staging machine before Christmas we have no longer experienced any crash of the Jenkins master Given that Henrik pushed all the changes to our production system We are totally happy that the incremental updates made our system that stable and that Mozilla QA doesn t have cope with outages Henrik and Jarek were both working on the mozfile 1 1 release to make it more stable in terms of removing files when those are still in use or don t have the right permissions set Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 1 and week 2 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda and notes from the first Firefox Automation meeting of week 2 automation ci firefox firefox automation jenkins mozmill mozqa Mozilla Automation Development report week 51 52 2013 January 24 2014 Henrik Skupin 5 Comments Wow somehow I totally missed to send out reports for our automation work Most likely that happened because of the amount of work I had in the past couple of weeks So for now lets do a final update before the title will be updated to Firefox Automation report by the year 2014 Highlights We have released Mozmill 2 0 3 to fix a couple of issues see dependencies on bug 950831 seen with Firefox Metro builds and our Firefox shutdown code We pushed those changes together with the releases of mozmill automation 2 0 3 and the new mozmill environment files to our mozmill ci staging instance for baking Henrik was able to finish the work in setting up our new mozmill ci staging instance in the SCL3 datacenter Please see bug 947108 for details With it we have the identical environment as the production instance and can see regressions immediately and not when we merge to production which was pretty bad in the past couple of week So RIP old staging server One of our goals for quarter 3 in 2013 was to setup a web based configutation tool for ondemand testruns in mozmill ci which can be used by QA people to trigger testruns for beta and release builds Cosmin jumped on it and got the first version implemented You can find a running instance on Github for now Later we want to make the tool available via http www mozqa com To make our mozmill ci system more stable Henrik pushed a large set of new features and fixes to the staging instance Our plan was to let it bake over the Christmas holidays with the hope that Jenkins will run way more stable now Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 51 and week 52 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda and notes from the last Automation Development meeting of week 51 automation automation development ci jenkins mozmill Mozilla Automation Development report week 49 50 2013 December 17 2013 Henrik Skupin 5 Comments It s getting closer to Christmas So here the 2nd last automation development report for 2013 Also please note that all team members including myself who were dedicated to Firefox Desktop automation have been transitioned back from the A Team into the Mozilla QA team This will enable us to have a better relationship with QA feature owners and get them trained for writing automated tests for Firefox Therefor my posts will be named Firefox Automation in the future Highlights With the latest release of Firefox 26 0 a couple of merges in our mozmill tests repository had to be done Work involved here was all done by Andreea and Andrei on bug 945708 To get rid of failed attempts to remove files after a testrun with Mozmill Henrik was working on a new version of mozfile which includes a method called remove now It should be used by any code given that it tries multiple times to remove files or directories if access is getting denied on Windows systems We released Mozmill 2 0 2 with a couple of minor fixes and the above mentioned file removal fixes Beside that mozmill automation 2 0 2 and new mozmill environments have been released We are still working on the remaining issues with Mozmill 2 0 and are hoping to get them fixed as soon as possible So that an upgrade to the 2 0 x branch can happen Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 49 and week 50 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda and notes from the last two Automation Development meetings of week 49 and week 50 automation automation development ci firefox mozmill Mozilla Automation Development report week 47 48 2013 December 6 2013 Henrik Skupin 4 Comments This is again an overview about the highlights of our work in week 47 and 48 this year Sorry for the delay of a couple of days but some critical work was holding me off from writing this post Highlights Henrik and Dave were working on a couple of Mozmill CI

    Original URL path: http://www.hskupin.info/tag/ci/page/3/ (2016-05-01)
    Open archived version from archive

  • Automation Development report – week 40 2013 | hskupin.info
    change in Firefox has caused this misbehavior of Mozmill Hopefully we can get this fully investigated and fixed soon For Gaia related work Dave has released a couple of interesting software updates which are gaiatest 0 16 b2gpopulate 0 10 and b2gperf 0 10 Beside that you might also want to have a look at Dave s blog post about the new command line interface tool for Gaia which let you run commands directly via the command line Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development ci gaia mozmill Post navigation Previous Post Automation Development report week 39 2013 Next Post Mozmill 1 5 24 released Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 2 Replies 0 Comments 2 Tweets 0 Facebook 0 Pingbacks Last reply was October 10 2013 Planet Ateam View October 10 2013 Henrik Skupin Automation Development report week 40 2013 http t co uf7ZXm3CU8 Reply planetmozilla View October 10 2013 Henrik Skupin Automation Development report week 40 2013 http t co xvMJGnJNa7 Reply Photostream October 2013 M T W T F S S Sep Nov 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2 2016 Review of automation work Q4 2015 January 9 2016 Automation Survey Follow up January 5 2016 Results of the Firefox Automation Survey December 3 2015 Survey about sharing information inside

    Original URL path: http://www.hskupin.info/2013/10/10/automation-development-report-week-40-2013/ (2016-05-01)
    Open archived version from archive

  • gaia | hskupin.info
    and cut off elements in our mozmill ci production environment That s a big step forward because with that we no longer have any other test machines which run Mozmill tests on a production like system Everything is combined in a single continuous integration system To make that happen Henrik had to fix a couple of dependencies across mozmill ci mozdownload and down to pulsetranslator As of now we will not regularly check the test results but will report them once in a while Reason for that is the lack of human resources or any automation which syncs the results with the l10n dashboard With yesterdays release of Firefox 24 0 we got another extended support release ESR That means we have to cover both 24 0 x ESR and 17 0 x ESR releases for the next 12 weeks The necessary jobs for mozmill ci have been created and our Pulse listeners adjusted We finally updated our mozmill environment to make use of the new and shiny mozmill automation package That allows us to do signed off releases instead of direct repository checkouts for mozmill ci which caused a bit of breakage since it exists We have new packages available for download for Mozmill 1 5 and 2 0rc5 To let us have an easier transition from Mozmill 1 5 to the upcoming version 2 0 Henrik setup a new mozmill ci instance which runs the same kind of tests as production but with Mozmill 2 0rc5 The setup was already helpful given that we discovered a regression which didn t let us run Mozmill on OS X 10 6 With all the remaining blockers landed we will have another release candidate It will be out this week In terms of Mozmill tests for Firefox we finally were able to separate out tests which make use of remote test data to a separate testrun With that step our functional testrun only uses local resources served via httpd js Big thanks here goes to one of our new contributors with the name Balazs Juhasz Not to leave gaia alone I also want to mention some of the highlights in that area The gaia ui tests for example are using mozdownload now to download b2g desktop builds for testing Support for mobile builds will hopefully land soon too Beside that Dave pushed two software releases of b2gperf 0 7 with logging included and b2gpopulate 0 9 with a fix for nightly builds Last but not least we have to give credits to Johannes who finished the patch to get the first automated tests for mozdownload via mozhttpd landed It s the base for all the other tests we need to get full test coverage across all the different scrapers Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development b2g ci firefox gaia mozmill Mozilla Automation Development report week 36 2013 September 10 2013 Henrik Skupin 4 Comments It looks like

    Original URL path: http://www.hskupin.info/tag/gaia/ (2016-05-01)
    Open archived version from archive

  • Automation Development report – week 38 2013 | hskupin.info
    environment With it we have a defined release schema now and do no longer pull automation changes from the Mercurial repository for each change This allows us to deeply test the scripts before the release and will not cause that massive test failures when a mistake was made Further Dave landed features like timestamp output in the console log listing of injected environment variables and HTTP logging for our update tests Especially the latter should help us a lot while investigating update test failures Last but not least Henrik also landed ANSI color support for the console which will be used by Mozmill 2 0 to show colored output for test results Beside all that we also released the next release candidate for Mozmill which is v2 0rc6 Read this thread for more details Just to add the previously setup mozmill ci instance for Mozmill 2 0 was of big help here given that we discovered a couple of unknown issues and were able to fix them all in a quick turnaround With that release we also pushed mozmill automation 2 0rc6 and an updated mozmill env For Gaia we were able to finalize a very important step we worked on for a long time and which will help everyone working on that product It s the move of the gaia ui tests from the separate github repository into the gaia main repository With it we have always tests which are synced with the latest feature additions and bug fixes in Gaia Also developers can more easily run those tests and we can detect regressions before they actually land in the repository Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development ci firefox firefox os gaia mozmill Post navigation

    Original URL path: http://www.hskupin.info/2013/09/24/automation-development-report-week-38-2013/ (2016-05-01)
    Open archived version from archive

  • Automation Development report – week 37 2013 | hskupin.info
    to the upcoming version 2 0 Henrik setup a new mozmill ci instance which runs the same kind of tests as production but with Mozmill 2 0rc5 The setup was already helpful given that we discovered a regression which didn t let us run Mozmill on OS X 10 6 With all the remaining blockers landed we will have another release candidate It will be out this week In terms of Mozmill tests for Firefox we finally were able to separate out tests which make use of remote test data to a separate testrun With that step our functional testrun only uses local resources served via httpd js Big thanks here goes to one of our new contributors with the name Balazs Juhasz Not to leave gaia alone I also want to mention some of the highlights in that area The gaia ui tests for example are using mozdownload now to download b2g desktop builds for testing Support for mobile builds will hopefully land soon too Beside that Dave pushed two software releases of b2gperf 0 7 with logging included and b2gpopulate 0 9 with a fix for nightly builds Last but not least we have to give credits to Johannes who finished the patch to get the first automated tests for mozdownload via mozhttpd landed It s the base for all the other tests we need to get full test coverage across all the different scrapers Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development b2g ci firefox gaia mozmill Post navigation Previous Post Automation Development report week 36 2013 Next Post Automation Development report week 38 2013 Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify

    Original URL path: http://www.hskupin.info/2013/09/18/automation-development-report-week-37-2013/ (2016-05-01)
    Open archived version from archive

  • b2g | hskupin.info
    The test which is an orangutan based script driving the gaia ui will be run on the B2G emulator using TBPL builds from mozilla central Memory dumps will be grabbed and results posted to AWSY with the ultimate goal in identifying and preventing Firefox OS memory leak regressions For more information please see the tracking bug Get SoftVision to lead the automation efforts for QA with our oversight Our team members from the test automation team at Softvision are helping us for a long time now in maintaining the Mozmill tests repository by fixing broken tests and creating new ones Also they have assisted in the final work for the Mozmill 2 0 release and other tools we own To give them more responsibility we want to bring all of them into the position to handle the Mozmill CI system on their own This is necessary given the much broader scope of tasks everyone in our team is assigned to Therefore we will do trainings and demos in our Ask an expert meetings Team Goals There are also some additional goals which do not scale across teams but are also important to note Deploy Eideticker CI system for Firefox OS We have to implement a continuous integration system for the Firefox OS start up and scrolling tests using an external camera More details about this goal can be found on bug 904837 Extend Mozmill CI to cover most of our localized builds To lower the amount of possibly broken beta and release builds we have to extend our tests to cover nearly all supported locales Therefore we have to bring more nodes online in our CI system and further enhance the tests to run more efficient The ultimate goals would be to test all of our 90 locales If you are interested to help us please let us know or check issue 270 Create web application for on demand update jobs We want to reduce the failure rate when setting up the configuration for on demand update tests in our Mozmill CI system Therefore a simple web application has to be created which allows us to pick the configuration like what can be done with the trychooser If you want to help please check bug 915164 Stretched Goals Last but not least we also have goals which are stretched and we might work on if there is time left Setup try server like Mozmill CI system To help everyone who is working on creating new or fixing broken Mozmill tests we want to have a try server like system That means you could push your patch and it will be tested across platforms and Firefox versions Investigate requirements for community driving tool One of the goals from Henrik is to lower the amount of volunteers who are leaving our team or even Mozilla because of lack of activity from our side Given that there is no good way in keeping in touch with everyone yet a tool has to be

    Original URL path: http://www.hskupin.info/tag/b2g/ (2016-05-01)
    Open archived version from archive

  • firefox | hskupin.info | Page 3
    discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 13 and week 14 automation ci firefox firefox automation mozmill testing Mozilla Firefox Automation report week 11 12 2014 May 5 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 11 and 12 Highlights After Henrik got started on updating the TPS test framework for Firefox Sync tests he got it into a state that it is working with the new Firefox Accounts feature coming with Firefox 29 0 For details please see bug 966434 Fixing the backward compatibility for the old Sync authentication is his next step With the release of Mozmill 2 0 6 and the initial support of handling crashes we found a major Adobe Flash crash on our Windows nodes when clearing cookies We started to investigate and reported the problem appropriately so that Adobe is aware of it For other crashes which are related to Firefox directly we would still have to retrieve and print the stack to the console But we cannot do this until the crashreporter symbols are available for Nightly builds on ftp mozilla org We will continue implementing this feature into Mozmill once the former bug has been fixed Given that the release of Firefox 28 was upcoming Andreea has taken care of all the mozmill tests related branch merges To be prepared for our first Automation Training days Cosmin updated our Mozmill Crowd extension to ease the first steps for new contributors to our projects Now the extension is working again for all the latest Firefox releases Even with the Firefox Metro projects seeing canceled we want to finalize our nearly ready Mozmill tests for Firefox Metro and get them landed That way we can pick up development if necessary in the future So Daniel was able to get additional 4 tests finished by this week In week 12 Henrik finished the basic implementation work for TPS in being able to switch between Firefox Accounts and the old Sync authentication Both methods are working now and can be used for testing As next step we have to investigate and fix all the remaining failing TPS tests Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 11 and week 12 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 11 and week 12 automation firefox mozmill testing training Mozilla Firefox Automation report week 9 10 2014 April 11 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 9 and 10 I for myself was a week on vacation A bit of relaxing before the work on the TPS test framework should get started Highlights In preparation to run Mozmill tests for Firefox Metro in our Mozmill CI system Andreea has started to get support for Metro builds and appropriate tests included With the help from Henrik we got Mozmill 2 0 6 released It contains a helpful fix for waitForPageLoad which let you know about the page being loaded and its status in case of a failure This might help us to nail down the intermittent failures when loading remote and even local pages But the most important part of this release is indeed the support of mozcrash Even that we cannot have a full support yet due to missing symbol files for daily builds on ftp mozilla org we can at least show that a crash was happening during a testrun and let the user know about the local minidump files Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 9 and week 10 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 9 and week 10 automation automation development ci firefox metro mozmill QA Mozilla Firefox Automation report week 5 6 2014 March 14 2014 Henrik Skupin 5 Comments A lot of things were happening in weeks 5 and 6 and we made some good progress regards the stability of Mozmill Highlights The unexpected and intermittent Jenkins crashes our Mozmill CI system was affected with are totally gone now Most likely the delayed creation of jobs made that possible which also gave Jenkins a bit more breath and not bomb it with hundreds of API calls For the upcoming release of Mozmill 2 0 4 a version bump for package dependencies was necessary for mozdownload So we released mozdownload 1 11 Sadly a newly introduced regression in packaging caused us to release mozdownload 1 11 1 a day later After a lot of work for stability improvements we were able to release Mozmill 2 0 4 This version is one with the largest amount of changes in the last couple of months Restarts and shutdowns of the application is way better handled by Mozmill now Sadly we noticed another problem during restarts of the application on OS X bug 966234 which forced us to fix mozrunner Henrik released mozrunner 5 34 which includes a fix how mozrunner retrieves the state of the application during a restart It was failing here by telling us that the application has quit while it was still running As result Mozmill started a new Firefox process which was not able to access the still used profile A follow up Mozmill release was necessary so we went for testing it As another great highlight for community members who are usually not able to attend our Firefox Automation meetings

    Original URL path: http://www.hskupin.info/tag/firefox/page/3/ (2016-05-01)
    Open archived version from archive