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 51/52 2014 | hskupin.info
    test framework Henrik started to mass close existing bugs for Mozmill So only a hand full of bugs will remain open If there is something important you want to see fixed we would encourage you to start working on the appropriate bug For Mozmill CI we got the new Ubuntu 14 10 boxes up and running in our staging environment Once we can be sure they are stable enough they will also be enabled in production 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 the video recording and notes from the Firefox Automation meeting of week 51 and week 52 automation ci firefox marionette mozmill mozqa testing Post navigation Previous Post Firefox Automation report week 49 50 2014 Next Post Firefox Automation report Q1 2015 Logging In Post a Reply to Planet Ateam 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 March 2 2015 PlanetFeeds View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 In this post you can find an overview about the wo http t co ZUibrCoHft Reply Planet Ateam View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 http t co 60S1TxfeTI Reply planetmozilla View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 http t co X2lkkFF1zk Reply Photostream March 2015 M T W T F S S Jan May 1

    Original URL path: http://www.hskupin.info/2015/03/02/firefox-automation-report-week-51-52-2014/?replytocom=47703 (2016-05-01)
    Open archived version from archive


  • January | 2015 | hskupin.info
    will post more details about it 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 the video recording and notes from the Firefox Automation meeting of week 48 Due to the Mozilla all hands workweek there was no meeting in week 49 automation continuous integration marionette mozmill mozqa testing Mozilla Firefox Automation report week 47 48 2014 January 14 2015 Henrik Skupin 1 Comment In this post you can find an overview about the work happened in the Firefox Automation team during week 47 and 48 Highlights Most of the work during those two weeks made by myself were related to get Jenkins http jenkins ci org upgraded on our Mozmill CI systems to the most recent LTS version 1 580 1 This was a somewhat critical task given the huge number of issue as mentioned in my last Firefox Automation report On November 17th we were finally able to get all the code changes landed on our production machine after testing it for a couple of days on staging The upgrade was not that easy given that lots of code had to be touched and the new LTS release still showed some weird behavior when connecting slave nodes via JLNP As result we had to stop using this connection method in favor of the plain java command This change was actually not that bad because it s better to automate and doesn t bring up the connection warning dialog Surprisingly the huge HTTP session usage as reported by the Monitoring plugin was a problem introduced by this plugin itself So a simple upgrade to the latest plugin version solved this problem and we will no longer get an additional HTTP connection whenever a slave node connects and which never was released Once we had a total freeze of the machine because of that Another helpful improvement in Jenkins was the fix for a JUnit plugin bug which caused concurrent builds to hang until the former build in the queue has been finished This added a large pile of waiting time to our Mozmill test jobs which was very annoying for QA s release testing work especially for the update tests Since this upgrade the problem is gone and we can process builds a lot faster Beside the upgrade work I also noticed that one of the Jenkins plugins in use it s actually the XShell plugin failed to correctly kill the running application on the slave machine in case of an job is getting aborted The result of that is that following tests will fail on that machine until the not killed job has been finished I filed a Jenkins bug and did a temporary backout of the offending change in that plugin Individual Updates For more granular updates of each individual

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

  • 02 | March | 2015 | hskupin.info
    Eftimie and was sitting around for a while That addition allows us to use mozhttpd for serving test data via a local HTTP server Last but not least another important feature went in which let us better handle application disconnects There are still some more bugs to fix before we can actually release version 2 1 of Mozmill Given that we only have the capacity to fix the most important issues for the Mozmill test framework Henrik started to mass close existing bugs for Mozmill So only a hand full of bugs will remain open If there is something important you want to see fixed we would encourage you to start working on the appropriate bug For Mozmill CI we got the new Ubuntu 14 10 boxes up and running in our staging environment Once we can be sure they are stable enough they will also be enabled in production 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 the video recording and notes from the Firefox Automation meeting of week 51 and week 52 automation ci firefox marionette mozmill mozqa testing Photostream March 2015 M T W T F S S Jan May 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

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

  • Firefox Automation report – week 47/48 2014 | hskupin.info
    was released Once we had a total freeze of the machine because of that Another helpful improvement in Jenkins was the fix for a JUnit plugin bug which caused concurrent builds to hang until the former build in the queue has been finished This added a large pile of waiting time to our Mozmill test jobs which was very annoying for QA s release testing work especially for the update tests Since this upgrade the problem is gone and we can process builds a lot faster Beside the upgrade work I also noticed that one of the Jenkins plugins in use it s actually the XShell plugin failed to correctly kill the running application on the slave machine in case of an job is getting aborted The result of that is that following tests will fail on that machine until the not killed job has been finished I filed a Jenkins bug and did a temporary backout of the offending change in that plugin Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 47 and week 48 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 47 and week 48 automation ci jenkins mozmill Post navigation Previous Post Firefox Automation report week 45 46 2014 Next Post Firefox Automation report week 49 50 2014 Logging In Post a Reply to EdgarsLabRat 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 1 Reply 0 Comments 1 Tweet 0 Facebook 0 Pingbacks Last reply

    Original URL path: http://www.hskupin.info/2015/01/14/firefox-automation-report-week-47-48-2014/?replytocom=45045 (2016-05-01)
    Open archived version from archive

  • December | 2014 | hskupin.info
    work happened in the Firefox Automation team during week 43 and 44 Highlights In preparation for the QA wide demonstration of Mozmill CI Henrik reorganized our documentation to allow everyone a simple local setup of the tool Along that we did the remaining deployment of latest code to our production instance Henrik also worked on the upgrade of Jenkins to latest LTS version 1 565 3 and we were able to push this upgrade to our staging instance for observation Further he got the Pulse Guardian support implemented Mozmill 2 0 9 and Mozmill Automation 2 0 9 have been released and if you are curious what is included you want to check this post One of our major goals over the next 2 quarters is to replace Mozmill as test framework for our functional tests for Firefox with Marionette Together with the A Team Henrik got started on the initial work which is currently covered in the firefox greenlight tests repository More to come later Beside all that work we have to say good bye to one of our SoftVision team members October the 29th was the last day for Daniel on the project So thank s for all your work Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 43 and week 44 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 43 and week 44 automation ci firefox jenkins marionette mozmill testing Mozilla Firefox Automation report week 41 42 2014 December 17 2014 Henrik Skupin Leave a comment In this post you can find an overview about the work happened in the Firefox Automation team during week 41 and 42 With the beginning of October we also have some minor changes in responsibilities of tasks While our team members from SoftVision mainly care about any kind of Mozmill tests related requests and related CI failures Henrik is doing all the rest including the framework and the maintenance of Mozmill CI Highlights With the support for all locales testing in Mozmill CI for any Firefox beta and final release Andreea finished her blacklist patch With that we can easily mark locales not to be tested and get rid of the long white list entries We spun up our first OS X 10 10 machine in our staging environment of Mozmill CI for testing the new OS version We hit a couple of issues especially some incompatibilities with mozrunner which need to be fixed first before we can get started in running our tests on 10 10 In the second week of October Teodor Druta joined the Softvision team and he will assist all the others with working on Mozmill tests But we also had to fight a lot with Flash crashes on our testing machines So we have seen about 23 crashes

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

  • 14 | January | 2015 | hskupin.info
    Surprisingly the huge HTTP session usage as reported by the Monitoring plugin was a problem introduced by this plugin itself So a simple upgrade to the latest plugin version solved this problem and we will no longer get an additional HTTP connection whenever a slave node connects and which never was released Once we had a total freeze of the machine because of that Another helpful improvement in Jenkins was the fix for a JUnit plugin bug which caused concurrent builds to hang until the former build in the queue has been finished This added a large pile of waiting time to our Mozmill test jobs which was very annoying for QA s release testing work especially for the update tests Since this upgrade the problem is gone and we can process builds a lot faster Beside the upgrade work I also noticed that one of the Jenkins plugins in use it s actually the XShell plugin failed to correctly kill the running application on the slave machine in case of an job is getting aborted The result of that is that following tests will fail on that machine until the not killed job has been finished I filed a Jenkins bug and did a temporary backout of the offending change in that plugin Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 47 and week 48 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 47 and week 48 automation ci jenkins mozmill Photostream January 2015 M T W T F S S Dec Mar 1 2 3 4 5 6 7 8

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

  • 22 | January | 2015 | hskupin.info
    list of todo items and more clarity about so far unclear tasks In week 50 we got some updates landed for Mozmill CI Given a regression from the blacklist landing our l10n tests haven t been executed for any locale of the Firefox Developer Edition Since the fix landed we have seen problems with access keys in nearly each locale for a new test which covers the context menu of web content Also we would like to welcome Barbara Miller in our team She joined us as an intern via the FOSS outreach program as driven by Gnome She will be with us until March and will mainly work on testdaybot and the conversion of Mozmill tests to Marionette The latter project is called m21s and details can be found on its project page Soon I will post more details about it 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 the video recording and notes from the Firefox Automation meeting of week 48 Due to the Mozilla all hands workweek there was no meeting in week 49 automation continuous integration marionette mozmill mozqa testing Photostream January 2015 M T W T F S S Dec Mar 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

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

  • November | 2014 | hskupin.info
    a couple of helpful enhancements and fixes We released Mozmill 2 0 7 and mozmill automation 2 0 7 mainly for adding support of the v2 signed Firefox application bundles on OS X Sadly we quickly had to follow up with an appropriate 2 0 8 release for both tools because a let change in the JS Engine caused a complete bustage of Mozmill More details can be found in my appropriate blog post We were even able to finally release Memchaser 0 6 which is fixing a couple of outstanding bugs and brought in the first changes to fully support Australis One of our goals was to get the failure rate of Mozmill tests for release and beta candidate builds under 5 To calculate that Cosmin wrote a little script which pulls the test report data for a specific build from out dashboard and outputs the failure rate per executed testrun We were totally happy to see that the failure rate for all Mozmill tests was around 0 027 During the merge process for the Firefox 32 release Andrei has seen some test inconsistencies between our named branches in the Mozmill Tests repository Some changes were never backported and only present on the default branch for a very long time He fixed that and also updated our documentation for branch merges Something else worth for highlighting is also bug 1046645 Here our Mozmill tests found a case when Firefox does not correctly show the SSL status of a website if you navigate quickly enough The fix for this regression caused by about newtab made it even into the release notes Last but not least Andreea started planning our Automation Training day for Q3 So she wrote a blog post about this event on QMO Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 37 and week 38 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 37 and week 38 automation firefox mozmill testing Mozilla Firefox Automation report week 35 36 2014 November 6 2014 Henrik Skupin Leave a comment In this post you can find an overview about the work happened in the Firefox Automation team during week 35 and 36 Highlights Due to a lot of Mozmill test failures related to add on installation and search we moved from the addons dev allizom org website to the staging website located at addons allizom org Since then we experiencing way lesser test failures which are most likely network related In order to keep up with all test failures and requests for new tests we started our Bug triage meeting on a weekly basis on Friday For details we have created an etherpad If you are interested in helping us with Mozmill tests you can now find a list of mentored and good

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