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 Desktop automation goals Q1 2016 | hskupin.info
    for Linux right now it shouldn t matter that much given that nothing in our firefox puppeteer package is platform dependent so far Expanding testing to other platforms should be trivial later on For now the primary goal is to see test results of our tests in Treeherder and letting developers know what needs to be changed if e g UI changes are causing a regression for us If you are interested in more details have a look at bug 1237550 Documentation of firefox ui tests and mozmill ci We are submitting our test results to Treeherder for a while and are pretty stable But the jobs are still listed as Tier 3 and are not taking care of by sheriffs To reach the Tier 2 level we definitely need proper documentation for our firefox ui tests and especially mozmill ci In case of test failures or build bustage the sheriffs have to know what s necessary to do Now that the dust caused by all the refactoring and moving the firefox ui tests to hg mozilla org settles a bit we want to start to work more with contributors again To allow an easy contribution I will create various project documentation which will show how to get started and how to submit patches Ultimately I want to see a quarter of contribution project for our firefox ui tests around mid this year Lets see how this goes More details about that can be found on bug 1237552 automation ci continuous integration firefox marionette QA Post navigation Previous Post Review of automation work Q4 2015 Next Post Review of Firefox desktop automation work Q1 2016 Logging In Post a Reply to PlanetFeeds cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me

    Original URL path: http://www.hskupin.info/2016/02/02/firefox-desktop-automation-goals-q1-2016/?replytocom=60619 (2016-05-01)
    Open archived version from archive


  • January | 2016 | hskupin.info
    ui tests Finally the addition of test package support finished up my work on mozharness for Q4 in 2015 During all the time I was also sheriffing our test results on Treeherder e g mozilla central because we are still Tier 3 level and sheriffs don t care about it Mozmill CI Our Jenkins based CI system is still called mozmill ci even it doesn t really run any mozmill tests anymore We decided to not change its name given that it will only be around this year until we can run all of our tests in TaskCluster But lots of changes have been landed which I want to announce below We followed Release Engineering and got rid of the OS X 10 8 testing That means the used Mac minis were ready to get re imaged with OS X 10 11 The transition worked seamlessly Enhancements for test report submission to Treeherder by switching over to Hawk credentials and more understandable group names and symbols Preparation of all the machines of our supported platforms OSX 10 6 10 9 10 10 10 11 Ubuntu 14 04 Windows XP 7 8 1 to be able to handle mozharness driven tests Implemented and updated scripts to run firefox ui tests via mozharness and to allow Treeherder to fully parse our logs Addons Tools I also had some time to work on supporting tools Together with the help of contributors we got the following done mozdownload Release of mozdownload 1 18 1 and 1 19 to cope with the move of builds to AWS Nightly Tester Tools Porting back changes from the NTT fork called Utilu Nightly Tester Tools Memchaser Thanks to the tireless efforts from Szabolcs Hubai we got Memchaser working again in latest Firefox builds So all in all it was a productive quarter with lots of things accomplished I m glad that we got all of this done Now in Q1 it will continue and more interesting work is in front of me which I m excited about I will announce that soon in my next blog post Until then I would like to give a little more insight into our current core team for Firefox automation A picture taken during our all hands work week in Orlando early in December shows Syd Maja myself and David Lets get started into 2016 with lots of ideas discussions and enough energy to get those things done automation ci continuous integration firefox jenkins marionette mozqa Mozilla Automation Survey Follow up January 5 2016 Henrik Skupin 2 Comments As promised in my last post about the automation survey results I wanted to come up with a follow up to clarify our next steps in being more open for our activities discussions and also quarterly goals Sorry that it has been taken a bit longer but end of the quarter and especially the year is mostly packed with stuff to finish up Also the all hands work week in Orlando beginning of December

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

  • 02 | February | 2016 | hskupin.info
    to test nightly and release builds for en US but also a couple of other locales This might change later this year when mozmill ci can be replaced by running all the tasks in Taskcluster Anyway for now my job is to get the firefox ui tests running in Taskcluster once a build task has been finished Although that this can only be done for Linux right now it shouldn t matter that much given that nothing in our firefox puppeteer package is platform dependent so far Expanding testing to other platforms should be trivial later on For now the primary goal is to see test results of our tests in Treeherder and letting developers know what needs to be changed if e g UI changes are causing a regression for us If you are interested in more details have a look at bug 1237550 Documentation of firefox ui tests and mozmill ci We are submitting our test results to Treeherder for a while and are pretty stable But the jobs are still listed as Tier 3 and are not taking care of by sheriffs To reach the Tier 2 level we definitely need proper documentation for our firefox ui tests and especially mozmill ci In case of test failures or build bustage the sheriffs have to know what s necessary to do Now that the dust caused by all the refactoring and moving the firefox ui tests to hg mozilla org settles a bit we want to start to work more with contributors again To allow an easy contribution I will create various project documentation which will show how to get started and how to submit patches Ultimately I want to see a quarter of contribution project for our firefox ui tests around mid this year Lets see how

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

  • Firefox Automation report – week 33/34 2014 | hskupin.info
    for testing beta and release builds of Firefox across supported platforms That means we cover 30 of about 95 active locales now To cover them all a good amount of follow up work is still necessary Immediately we stopped to run add on tests for all branches except Nightly builds to save more time on our machines Henrik also continued on PuppetAgain integration for our staging and production CI systems One of the blockers was the missing proxy support but with the landing of the patch on bug 1050268 all proxy related work should have been done now Also on the continuous integration for TPS tests we made progress The implementation got that far for Coversheet that we made the Jenkins branch the active master There are still issues to implement or get fixed before the Jenkins driven CI can replace the old hand made one Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 33 and week 34 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 33 and week 34 automation automation development ci continuous integration firefox mozmill tps Post navigation Previous Post Firefox Automation report week 31 32 2014 Next Post Erster offizieller Halbmarathon 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 Photostream October 2014 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

    Original URL path: http://www.hskupin.info/2014/10/02/firefox-automation-report-week-33-34-2014/ (2016-05-01)
    Open archived version from archive

  • tps | hskupin.info
    for Coversheet that we made the Jenkins branch the active master There are still issues to implement or get fixed before the Jenkins driven CI can replace the old hand made one Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 33 and week 34 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 33 and week 34 automation automation development ci continuous integration firefox mozmill tps Mozilla Firefox Automation report week 31 32 2014 October 1 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 31 and 32 It s a bit lesser than usual mainly because many of us were on vacation Highlights The biggest improvement as came in during week 32 were the fixes for the TPS tests Cosmin spent a bit of time on investigating the remaining underlying issues and got them fixed Since then we have a constant green testrun which is fantastic While development for the new TPS continuous integration system continued we were blocked for a couple of days by the outage of restmail net due to a domain move After the DNS entries got fixed everything was working fine again for Jenkins and Mozilla Pulse based TPS tests For Mozmill CI we agreed on that the Endurance tests we run across all branches are not that useful but only take a lot of time to execute about 2h per testrun The most impact also regarding of new features landed will be for Nightly So Henrik came up with a patch

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

  • Firefox Automation report – week 31/32 2014 | hskupin.info
    After the DNS entries got fixed everything was working fine again for Jenkins and Mozilla Pulse based TPS tests For Mozmill CI we agreed on that the Endurance tests we run across all branches are not that useful but only take a lot of time to execute about 2h per testrun The most impact also regarding of new features landed will be for Nightly So Henrik came up with a patch to only let those tests run for en US Nightly builds Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 31 and week 32 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 32 There was no meeting in week 31 automation ci continuous integration firefox firefox automation mozmill tps Post navigation Previous Post Memchaser 0 6 has been released Next Post Firefox Automation report week 33 34 2014 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 Photostream October 2014 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

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

  • continuous integration | hskupin.info | Page 2
    CI to also run pulse triggered tests for all supported versions of Firefox on OS X 10 9 Since then 2 betas have been tested and no failures occurred I call this a great start Further I have prepared a further single Mac Mini for each 10 6 10 7 and 10 8 So we have 4 nodes per OS X version to run tests on Linux and Windows will follow shortly Further a fix has been landed for httpd js which solves one of our pain points in using that server With it we can save a lot of time and as already posted yesterday we have released Mozmill 1 5 24 for it Further please welcome our new contributor Kamil Kjozwiak who wants to help us with the creation of Mozmill tests for Firefox Metro Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad 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 this weeks Automation Development meeting automation automation development continuous integration mozmill testing Mozilla Review of Automation Services goals in Q1 2012 April 26 2012 Henrik Skupin Leave a comment Now three weeks after Q1 of 2012 has been passed by I finally have the time to give some details about our work happened during the first three months As usual we set a couple of goals we wanted to see by the end of the quarter All of them were kinda important so we did our best to get all of them done and we succeeded even if it was in the last minute So everyone of us was happy about the goal achievements Below you will find an overview of each of those projects For more detailed information I will follow up with additional blog posts by next week Mozmill CI system for release daily and l10n builds It has been taken a while for us to get to a state when we absolutely had to work on a continuous integration solution Seeing that more and more tests are getting automated with Mozmill and that we still require manual interaction or crontab jobs and tasks on Windows to get tests executed we had to find a better way in getting tests run After a bit of investigation we started by using Jenkins formerly known as Hudson And since beginning of this month we now have a system which runs our Mozmill tests for all the supported daily and beta candidate builds and for each tinderbox build based on l10n check ins on whichever branch As trigger we make use of Mozilla Pulse which informs us directly when builds have been made available Further we also had to ensure that tests can be triggered by on demand because update tests cannot be covered by Pulse yet and sometimes we have to re run tests against a specific build All in

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

  • Getting rid of the silence | hskupin.info
    be written in English I hope you will like that change Post navigation Previous Post Join our Make sure your code works session MozCamp Next Post Eine etwas andere Winterwanderung 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 Photostream March 2013 M T W T F S S Sep Aug 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 the Firefox Automation team November 23 2015 Firefox Automation report Q3 2015 October 20 2015 Crusial SSD bug and firmware fix September 28 2015 mozdownload 1 18 released September 14 2015 Firefox Automation report Q2 2015 August 11 2015 Recent Comments

    Original URL path: http://www.hskupin.info/2013/03/21/getting-rid-of-the-silence/ (2016-05-01)
    Open archived version from archive