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".
  • training | hskupin.info
    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 Join our first Automation Training days on March 24 26 March 21 2014 Henrik Skupin 9 Comments Building software is fun Spending countless hours or even days on something to get it finally working Helping someone who uses your software to speed up the daily workflow All that is fantastic and every developer loves that But don t let the dark side come up when customers are pointing you to a lot of software defects Are you still proud and will you continue the work as how you did it before Most likely not Or well lets say at least not when quality is what you want to ship So you will start to think about how to test your application You can do a lot of manual testing based on test plans or just do exploratory testing That will work as long as your application is not complex enough and can be done in a couple of minutes But once you have to do the same kind of steps over and over again for each release you will find it boring and loose the interest or concentration on it Failures will happen so that issues slip through your testing and bugs becoming part of the new release That s indeed something you eventually want to kill in the future But how There is an easy answer to this question Use test automation Create tests for each feature you implement or regression you got fixed Over time the enlarged suite of tests will make you happy given that you have to spend nearly no time on manual tests and have results in a split of the time needed before Releasing new versions of the application can be done much faster At some point when your application is large enough you might even not work alone anymore on that product There will be other developers or even software testers whose job is to plan and execute the testing strategy

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


  • Automation Development report – week 35 2013 | hskupin.info
    spent in testing everything Also because nearly all of the Jenkins plugins which we make use of had updates available and had a slightly different format of the XML configuration all our static files had to be updated too But by early last week we were able to push those bits to our staging server and running that version of Jenkins for a week hasn t brought up any kind of regression That s great To finish up the work Henrik published all bits and bytes to our production machine yesterday We will continue observing the memory usage and let you know if the situation got better Beside that we made a couple of changes to our list of available nodes for the mozmill ci cluster As of last week we brought our Windows 8 1 nodes 3x 32bit 3x 64bit online for preliminary testing Given that all went well and no further issues have been seen they are now fully integrated into jobs triggered by Pulse notifications Further we have replaced our existent Ubuntu 12 10 nodes with the current release of Ubuntu 13 04 That means we run our tests on Ubuntu 12 04 LTS and Ubuntu 13 04 for both 32bit and 64bit now As requested by Mozilla QA we have to run more tests for localized beta and release candidate builds of Firefox That will help us to finally stop releasing broken l10n builds like Firefox 24 0b1 to our users For all locales covered by our tests we do now check for start up failures like the XML parsing error for the main window So Henrik pushed a patch to production which enabled tests to be run for the first 10 most used locales of Firefox Individual Updates For more granular updates of each individual

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

  • Mozdownload 1.9 released | hskupin.info
    release automation firefox Mozilla Software Post navigation Previous Post Mozmill 1 5 22 and 2 0rc5 released Next Post Automation Development report week 35 2013 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 August 29 2013 planetmozilla View August 29 2013 Henrik Skupin Mozdownload 1 9 released http t co LrwGILLDKa Reply Planet Ateam View August 29 2013 Henrik Skupin Mozdownload 1 9 released http t co fYYDu7z9ur Reply Photostream August 2013 M T W T F S S Mar Sep 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

    Original URL path: http://www.hskupin.info/2013/08/29/mozdownload-1-9-released/ (2016-05-01)
    Open archived version from archive

  • Automation Development report – week 33 2013 | hskupin.info
    from application updates could be the problem and especially the new update overlay screen for Windows 8 updates The latter completely blocked our testing So Henrik Skupin re configured all existing nodes and templates by disabling any automatic update checks Bug 900860 Since that has been done no further application disconnects have been observed Lets cross the fingers that this will stay that way We noticed a massive disconnect of slave nodes in our Mozmill CI cluster early last week At the same time the response time of our Jenkins master was drastically slow Henrik investigated the problem and identified that our current VM is not able to handle the memory load with 2GB of memory So we increased the memory to 4GB which indeed stopped the swapping process of consuming about 60 cpu load nearly all the time Henrik will continue to watch the current memory consumption over the next weeks Further we will upgrade our Jenkins installation to the latest LTS version soon once all blockers are fixed Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development Mozilla Post navigation Previous Post 4 Centrum Galerie Nachtlauf Next Post Automation Development report week 34 2013 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 August 20 2013 planetmozilla View August 20 2013 Henrik Skupin Automation Development report week 33 2013 http t co 8hg4W4jUAy Reply Planet Ateam View August 20 2013 Henrik Skupin Automation Development report week 33 2013 http t co Xm49EFLm8T Reply Photostream August 2013 M T W

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

  • Join our “Make sure your code works” session @MozCamp | hskupin.info
    room 1 We still have a couple of seats left To be best prepared please read through our session details and try to setup your machine before you leave for MozCamp We have setup links to get all necessary tools and the prepared Ubuntu VM If you aren t able to do that don t worry we will have USB thumb drives available for you to grab all the data you will need As a sneak peak we will also give you a link to our introduction slides so that you can change your mind if you are unsure about your attendance Make sure your code works from Rob Wood and Henrik Skupin We are looking forward and can t await to meet up with you all So see you MozCamp on Saturday Update We are planning to send out prizes for the best hand crafted test s some days after MozCamp when we have reviewed all the written tests So please be aware of code correctness coverage and style while implementing the tests automation firefox firefox os mozcamp Mozilla qmo webapi Post navigation Previous Post Results of our first Ask an Expert automation session Next Post Getting rid of the silence 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 September 2012 M T W T F S S Aug 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 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2 2016

    Original URL path: http://www.hskupin.info/2012/09/05/join-our-make-sure-your-code-works-session-mozcamp/ (2016-05-01)
    Open archived version from archive

  • firefox os | hskupin.info
    out yourself Keep in mind that it is fully backward compatible with Mozmill 1 5 x So all of your existent tests will continue to work without modifications Beside that a lot of trouble came over us in terms of mozmill ci breakage As what I wrote in the last Automation Development report we were facing a lot of issues with all of our Windows nodes The high CPU load caused tests to run very slow and we even faced application disconnect issues with Firefox due to no response coming back to Mozmill Henrik was heavily working on to get those issues fixed The first step in disabling the Windows 8 1 nodes were already a good start and we got more stable testruns Now we are waiting for the VMs with the final version of Windows 8 1 which will hopefully be ready soon But also disabling the Windows Defender helped a lot we really don t need that on our nodes for testing Firefox So especially the suspicious installation and uninstallation duration for Firefox went down from about 4 minutes to only a couple of seconds That s the best time saver at all Further we disabled the Windows Error Reporting which came into the way because the huge amount of crashes we experienced lately With that nothing halts the execution of our tests A big thank you for the hint goes to Armen from the RelEng team Dave continued his work on Firefox OS and got some important new releases out for b2gperf 0 8 gaia test 0 14 and gaia test 0 15 Also you should have a look at this blog post for Building a harness for Eideticker with LEGO which is kinda amazing If you want to see it in real life and you are participating the Mozilla Summit in Brussels check out his booth at the innovation fair Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development firefox firefox os mozmill testing Mozilla Automation Development report week 38 2013 September 24 2013 Henrik Skupin 2 Comments The last week was more dedicated for maintenance We were working on features for mozmill ci to let us more easily debug failing tests especially with all the cpu load spikes we have seen across our Windows machines But we also got the final Mozmill 2 0rc6 release out Continue reading to find details Hightlights One of our biggest issues last week was definitely the drastic increase of the CPU load across all of our Windows nodes in the mozmill ci cluster It magically started when QA did the first ondemand tests for the upcoming Firefox 25 0b1 release Especially the Windows 8 1 machines started to sporadically disconnect from the Jenkins master over the day caused by some blue screen crashes related to the kernel At the end this happened hourly or even more often when the machines had to run tests Observing the task manager has been shown that specifically the Windows Defender real time protection is causing a high load which e g caused a slow down for installing Firefox from about 6 seconds to 4 minutes Disabling the real time protection helped us across all Windows nodes but not for Windows 8 1 which was still crashing and rebooting But also other processes like svchost for network services or the desktop manager showed a high CPU load Those we weren t able to figure out yet Stopping to run tests on Windows 8 1 preview release seemed to be the only option for us Now we are waiting for VMs with the final version of Windows 8 1 installed Lets see if that will work better Beside that our production CI instance got a couple of nice new features At first Henrik added support for the mozmill automation package which comes with the latest versions of the mozmill 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 Mozilla Automation Development report week 36 2013 September 10 2013 Henrik Skupin 4 Comments It looks like since everyone is back from the summer vacations we keep our productivity kinda high over the last couple of weeks During the last week we finished again a couple

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

  • mozcamp | hskupin.info
    interested in raising your skills in automation and want to help us to strengthen the quality of Firefox OS please join us on Saturday at 3 05pm in B2G room 1 We still have a couple of seats left To be best prepared please read through our session details and try to setup your machine before you leave for MozCamp We have setup links to get all necessary tools and the prepared Ubuntu VM If you aren t able to do that don t worry we will have USB thumb drives available for you to grab all the data you will need As a sneak peak we will also give you a link to our introduction slides so that you can change your mind if you are unsure about your attendance Make sure your code works from Rob Wood and Henrik Skupin We are looking forward and can t await to meet up with you all So see you MozCamp on Saturday Update We are planning to send out prizes for the best hand crafted test s some days after MozCamp when we have reviewed all the written tests So please be aware of code correctness coverage and style while implementing the tests automation firefox firefox os mozcamp Mozilla qmo webapi Photostream May 2016 M T W T F S S 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 January 5 2016 Results of the Firefox Automation Survey December 3 2015

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

  • qmo | hskupin.info
    code works from Rob Wood and Henrik Skupin We are looking forward and can t await to meet up with you all So see you MozCamp on Saturday Update We are planning to send out prizes for the best hand crafted test s some days after MozCamp when we have reviewed all the written tests So please be aware of code correctness coverage and style while implementing the tests automation firefox firefox os mozcamp Mozilla qmo webapi Mozilla Software MemChaser 0 2 released March 2 2012 Henrik Skupin 4 Comments Exactly one month after we have released our initial version of MemChaser version 0 2 has been made publicly available You can install the add on as usual from addons mozilla org or if it is already installed simply check for updates within the Add ons Manager A couple of subtle changes have been made which will give a better experience for users So we have combined the formerly two widgets in the Add on bar into a single one to prevent other extensions from inserting their widgets in between At the same time the width has been reduced to not waste too much space keep in mind that we are still blocked on a SDK bug which doesn t let the widget size adapt to the content length dynamically Given the recent landing of the incremental garbage collector in Nightly builds of Firefox we had to do some extra unplanned updates to support this new feature When you are running a Nightly build and an incremental GC happens the GC label will be replaced with iGC Further we have improved the parsing of the GC CC console messages to allow us to add more interested entries dynamically So this time we have added the reason and type global or compartmental for a GC and the number of collected entries from the cycle collector All three will be written together with all the other data to the log file and are not visible in the add on bar As reported by an user MemChaser v0 1 1 was affected by some memory leaks which were caused by the Add on SDK 1 4 Given the tireless efforts of the SDK devs nearly all of those leaks except for widgets have been fixed in version 1 5 which has been recently released and is now used by MemChaser 0 2 Beside all those visible changes we also made some improvements to our development process So we have added the Add on SDK as a submodule to our own repository on Github Also to get more traction we made the decision to move the MemChaser repository to the Mozilla account And last but not least we implemented the Travis CI integration to get our code automatically tested with each check in If you are interested in further information about the changes feel free to check our list of issues for 0 2 We would also like to welcome everyone who has interests

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