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 5/6 2014 | hskupin.info
    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 we have started to record our meetings now So if you want to replay the meetings please check our archive Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 5 and week 6 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 Firefox Automation meetings of week 5 and week 6 automation ci firefox firefox automation mozdownload mozmill Post navigation Previous Post Firefox Automation report week 3 4 2014 Next Post Join our first Automation Training days on March 24 26 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 5 Replies 0 Comments 5 Tweets 0 Facebook 0 Pingbacks Last reply was March 14 2014 Planet Ateam View March 14 2014 Henrik Skupin Firefox Automation report week 5 6 2014 http t co JXEVkbMDKP Reply planetmozilla View March 14 2014 Henrik Skupin Firefox Automation report week 5 6 2014 http t co BeMSylagwF Reply EdgarsLabRat View March 14 2014 moz Henrik Skupin Firefox Automation report week 5 6 2014 http t co B2InjPAlyF Reply mozillian View March 14 2014 Planet Henrik Skupin Firefox Automation report week 5 6 2014 http t co Nud6WWCZVc Reply PlanetFeeds View March 14 2014 Henrik Skupin Firefox Automation report week 5 6 2014 A lot

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


  • Automation Development report – week 34 2013 | hskupin.info
    number of locales to test over the curse of the next few weeks For details and a follow up discussion please check the thread on the mailing list To stay on top of running our Mozmill tests on the latest OS versions Henrik added 6 new Ubuntu 13 04 nodes to our CI cluster Three of them are running a 32bit version while the other three have 64bit installed Most likely as of today we will remove the Ubuntu 12 10 machines from the cluster Sadly we are still scratching our head around the current problems with Windows 8 1 preview release Due to issues with the LoginManager we most likely see our nodes getting disconnected when an user is logging into such a machine via VNC The failure thrown doesn t seem to be that known yet so fixing the problem and bringing those nodes online will not happen soon If anyone has ideas what it could be please let us know Thanks to our automation members from the Softvision team Andreea Matei Andrei Eftimie Mario Garbi and Cosmin Malutan we were able to close out 4 of our existing mozmill test failures and also got 2 enhancements landed for Mozmill 2 0 Last but not least we want to thank Johannes for his contribution on the mozmill dashboard project With one of his latest patches it s now possible to correctly bookmark our individual dashboard instances with unique bookmark names Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development ci firefox jenkins mozdownload mozmill Post navigation Previous Post Automation Development report week 33 2013 Next Post Mozmill 1 5 22 and 2 0rc5 released Logging In Profile cancel Sign in with Twitter Sign in with Facebook or

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

  • Firefox Automation report – Q2 2015 | hskupin.info
    report to production If you want to have a sneak peak how it works just follow this link for Nightly builds More details about Treeherder reporting I will do later this quarter when the next pieces have been implemented Firefox UI Update Tests under RelEng My second deliverable was to assist Armen Zambrano in getting the Firefox UI Update tests run for beta and release builds on Release Engineering infrastructure This was a kinda important goal for us given that until now it was a manually triggered process with lots of human errors on our own infrastructure That means lots of failures if you do not correctly setup the configuration for the tests and a slower processing of builds due to our limited available infrastructure So moving this out of our area made total sense Given that Armen had already done a fair amount of work when I came back from my PTO I majorly fixed issues for the tests and the libraries as pointed out by him All that allowed us to finally run our tests on Release Engineering infrastructure even with a couple of failures at the beginning for the first beta But those were smaller issues and got fixed quickly Since then we seem to have good results If you want to have a look in how that works you should check the Marionette update tests wiki page Sadly some of the requirements haven t been completely finished yet So the Quality Engineering team cannot stop running the tests themselves But that will happen once bug 1182796 has been fixed and deployed to production Oh and if you wonder where the results are located Those are not getting sent to Treeherder but to an internal mailing list as used for every other automation results Other Work Beside the deliverables I got some more work done Mainly for the firefox ui tests and mozmill ci While the test coverage has not really been increased I had a couple of regressions to fix as caused by changes in Firefox But we also landed some new features thankfully as contributed by community members Once all that was done and we agreed to have kinda stable tests new branches have been created in the repository That was necessary to add support for each supported version of Firefox down to ESR 38 0 and to be able to run the tests in our Mozmill CI via Jenkins More about that you will find below The only task I still haven t had time for yet was the creation of proper documentation about our tests I hope that I will find the time in Q3 Mozmill CI got the most changes in Q2 compared to all the former quarters This is related to the transition from Mozmill tests to Marionette tests More details why we got rid of Mozmill tests can be found in this post With that we decided to get rid of most of the tests and mainly start from scratch

    Original URL path: http://www.hskupin.info/2015/08/11/firefox-automation-report-q2-2015/?replytocom=55331 (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – Q2 2015 | hskupin.info
    to report to production If you want to have a sneak peak how it works just follow this link for Nightly builds More details about Treeherder reporting I will do later this quarter when the next pieces have been implemented Firefox UI Update Tests under RelEng My second deliverable was to assist Armen Zambrano in getting the Firefox UI Update tests run for beta and release builds on Release Engineering infrastructure This was a kinda important goal for us given that until now it was a manually triggered process with lots of human errors on our own infrastructure That means lots of failures if you do not correctly setup the configuration for the tests and a slower processing of builds due to our limited available infrastructure So moving this out of our area made total sense Given that Armen had already done a fair amount of work when I came back from my PTO I majorly fixed issues for the tests and the libraries as pointed out by him All that allowed us to finally run our tests on Release Engineering infrastructure even with a couple of failures at the beginning for the first beta But those were smaller issues and got fixed quickly Since then we seem to have good results If you want to have a look in how that works you should check the Marionette update tests wiki page Sadly some of the requirements haven t been completely finished yet So the Quality Engineering team cannot stop running the tests themselves But that will happen once bug 1182796 has been fixed and deployed to production Oh and if you wonder where the results are located Those are not getting sent to Treeherder but to an internal mailing list as used for every other automation results Other Work Beside the deliverables I got some more work done Mainly for the firefox ui tests and mozmill ci While the test coverage has not really been increased I had a couple of regressions to fix as caused by changes in Firefox But we also landed some new features thankfully as contributed by community members Once all that was done and we agreed to have kinda stable tests new branches have been created in the repository That was necessary to add support for each supported version of Firefox down to ESR 38 0 and to be able to run the tests in our Mozmill CI via Jenkins More about that you will find below The only task I still haven t had time for yet was the creation of proper documentation about our tests I hope that I will find the time in Q3 Mozmill CI got the most changes in Q2 compared to all the former quarters This is related to the transition from Mozmill tests to Marionette tests More details why we got rid of Mozmill tests can be found in this post With that we decided to get rid of most of the tests and mainly start from

    Original URL path: http://www.hskupin.info/2015/08/11/firefox-automation-report-q2-2015/?replytocom=55335 (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – Q2 2015 | hskupin.info
    If you want to have a sneak peak how it works just follow this link for Nightly builds More details about Treeherder reporting I will do later this quarter when the next pieces have been implemented Firefox UI Update Tests under RelEng My second deliverable was to assist Armen Zambrano in getting the Firefox UI Update tests run for beta and release builds on Release Engineering infrastructure This was a kinda important goal for us given that until now it was a manually triggered process with lots of human errors on our own infrastructure That means lots of failures if you do not correctly setup the configuration for the tests and a slower processing of builds due to our limited available infrastructure So moving this out of our area made total sense Given that Armen had already done a fair amount of work when I came back from my PTO I majorly fixed issues for the tests and the libraries as pointed out by him All that allowed us to finally run our tests on Release Engineering infrastructure even with a couple of failures at the beginning for the first beta But those were smaller issues and got fixed quickly Since then we seem to have good results If you want to have a look in how that works you should check the Marionette update tests wiki page Sadly some of the requirements haven t been completely finished yet So the Quality Engineering team cannot stop running the tests themselves But that will happen once bug 1182796 has been fixed and deployed to production Oh and if you wonder where the results are located Those are not getting sent to Treeherder but to an internal mailing list as used for every other automation results Other Work Beside the deliverables I got some more work done Mainly for the firefox ui tests and mozmill ci While the test coverage has not really been increased I had a couple of regressions to fix as caused by changes in Firefox But we also landed some new features thankfully as contributed by community members Once all that was done and we agreed to have kinda stable tests new branches have been created in the repository That was necessary to add support for each supported version of Firefox down to ESR 38 0 and to be able to run the tests in our Mozmill CI via Jenkins More about that you will find below The only task I still haven t had time for yet was the creation of proper documentation about our tests I hope that I will find the time in Q3 Mozmill CI got the most changes in Q2 compared to all the former quarters This is related to the transition from Mozmill tests to Marionette tests More details why we got rid of Mozmill tests can be found in this post With that we decided to get rid of most of the tests and mainly start from scratch by only porting

    Original URL path: http://www.hskupin.info/2015/08/11/firefox-automation-report-q2-2015/?replytocom=55420 (2016-05-01)
    Open archived version from archive

  • May | 2015 | hskupin.info
    failures As result we started to partially skip tests which were failing There was no time to get any of those fixed Happily the latest version of Mozmill is still working kinda nicely so no other work had to be dedicated for this project Most of my time during the last quarter I actually had to spent on Marionette especially building up wrapper scripts for being able to use Marionette as test framework for Firefox Desktop This was a kinda large change for us but totally important in terms of maintenance burden and sustainability The code base of Mozmill is kinda outdated and features like Electrolysis e10s will totally break it Given that a rewrite of the test framework is too cost intensive the decision has been made to transition our Mozmill tests over to Marionette Side effect was that a lot of missing features had to be implemented in Marionette to bring it at a level as what Mozmill offers Thanks for the amazing work goes to Andrew Halberstadt David Burns Jonathan Griffin and especially Chris Manchester For the new UI driven tests for Firefox Desktop we created the firefox ui tests repository at Github We decided on that name to make it clear to which product the tests belong to and also to get rid of any relationship to the underling test framework name This repository contains the harness extensions around Marionette a separate puppeteer library for back end and UI modules and last but not least the tests themselves As goal for Q1 we had to get the basics working including the full set of remote security tests and most important the update tests A lot of help on the security tests we got from Barbara Miller our intern from December to March She did great amount of work here and also assisted other community members in getting their code done Finally we got all the security tests converted My own focus beside the harness pieces were the update tests Given the complete refactoring of those Mozmill tests we were able to easily port them over to Marionette We tried to keep the class structure as is and only did enhancements where necessary Here Bob Silverberg helped with two big chunks of work which I m gladly thankful about Thanks a lot With all modules in place I finally converted the update tests and got them running for each version of Firefox down to 38 0 which will be the next ESR release and kinda important to be tested with Marionette For stability and ease of contribution we added support for Travis CI to our new repository It helps us a lot with reviews of patches from community members and they also can see immediately if changes they have done are working as expected The next big chunk of work will be to get those tests running in Mozmill CI to be renamed and the test reporting to use Treeherder Also we want to get our update

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

  • 11 | August | 2015 | hskupin.info
    to always add the log files as generated by running the tests to the report It will not happen via data URLs but as artifacts with a link to an upload location In our case we make use of Amazon S3 as storage service With all the pieces implemented we can now report to treeherder and covering Nightly Aurora Developer Edition Beta and Release builds As of now reporting only happens against the staging instance of Treeherder but soon we will be able to report to production If you want to have a sneak peak how it works just follow this link for Nightly builds More details about Treeherder reporting I will do later this quarter when the next pieces have been implemented Firefox UI Update Tests under RelEng My second deliverable was to assist Armen Zambrano in getting the Firefox UI Update tests run for beta and release builds on Release Engineering infrastructure This was a kinda important goal for us given that until now it was a manually triggered process with lots of human errors on our own infrastructure That means lots of failures if you do not correctly setup the configuration for the tests and a slower processing of builds due to our limited available infrastructure So moving this out of our area made total sense Given that Armen had already done a fair amount of work when I came back from my PTO I majorly fixed issues for the tests and the libraries as pointed out by him All that allowed us to finally run our tests on Release Engineering infrastructure even with a couple of failures at the beginning for the first beta But those were smaller issues and got fixed quickly Since then we seem to have good results If you want to have a look in how that works you should check the Marionette update tests wiki page Sadly some of the requirements haven t been completely finished yet So the Quality Engineering team cannot stop running the tests themselves But that will happen once bug 1182796 has been fixed and deployed to production Oh and if you wonder where the results are located Those are not getting sent to Treeherder but to an internal mailing list as used for every other automation results Other Work Beside the deliverables I got some more work done Mainly for the firefox ui tests and mozmill ci While the test coverage has not really been increased I had a couple of regressions to fix as caused by changes in Firefox But we also landed some new features thankfully as contributed by community members Once all that was done and we agreed to have kinda stable tests new branches have been created in the repository That was necessary to add support for each supported version of Firefox down to ESR 38 0 and to be able to run the tests in our Mozmill CI via Jenkins More about that you will find below The only task I

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

  • hskupin.info | Mozilla, Photography and the Daily Life | Page 3
    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 Mozilla Software Memchaser 0 6 has been released September 18 2014 Henrik Skupin 2 Comments The Firefox Automation team would like to announce the release of memchaser 0 6 After nearly a year of no real feature updates but also some weeks of not being able to run Memchaser in Firefox Aurora 34 0a2 at all due to a regression we decided to release the current state of development as a public release We are aware that we still do not fully support the default Australis theme since Firefox 29 0 but that s an issue which takes some more time to finish up Changes in 0 6 Upgrade to Add on SDK 1 17 201 Fix test start stop logging for File not found error 199 contentURL expects a string in Panel and Widget constructors 198 Bring the minimizeMemory implementation up to date 193 Use residentFast instead of resident for memory reporter 192 Use postMessage for widget and panel communication instead port object 185 Support incremental cycle collection statistics 187 Added a usage section to the README 178 Change require statements and update the SDK to 1 14 174 Simplify travis yml 172 Use dot to include files while invoking bin sh 169 Use failonerror attribute in exec tasks 168 For all the details about the 0 6 release please check our issue tracker on Github addons firefox memory mozqa Mozilla Software mozdownload 1 12 has been released September 18 2014 Henrik Skupin Leave a comment The Firefox Automation team would like to announce the release of mozdownload 1 12 Without any other release of our universal download tool in the last 7 months a couple of nice new features and bug fixes will make this release even more useful You can upgrade your installation easily via pip or by downloading it from PyPI Changes in 1 12 Display selected build when downloading 149 Add support for downloading B2G desktop builds 104 Download candidate builds from candidates and not nightly 218 Add Travis CI build status and PyPI version badges to README 220 Add Python 2 6 to test matrix 210 Fix broken download of mac64 tinderbox builds 144 Allow download even if content length header is missing 194 Convert run tests script to Python 168 Ensure that date option is a valid date 196 automation firefox mozdownload mozqa Mozilla Software Mozmill 2 0 7 and 2 0 8 have been released September 18 2014 Henrik Skupin Leave a comment The Firefox Automation team would like to announce the release of Mozmill 2 0 7 and Mozmill 2 0 8 Both versions had to be released in such a short time frame to ensure continuing support for Firefox Some latest changes done for Firefox Nightly broke Mozmill or at least made it misbehaving If you run tests with Mozmill ensure to upgrade to the latest version You can do this via PyPI or simply download the already pre configured environment Changes in 2 0 7 Bug 1066295 testMultipleLoads js is failing due to new HTTP Cache v2 Bug 1000098 Fix testPageLoad js test for invalid cert page Bug 1065436 Disable e10s until full support landed Bug 1062773 Disconnect errors invalidate the report Bug 999393 Expose assert and expect by default in sub modules Bug 970820 Mozmill aborts with socket timeout when trying to send the report Changes in 2 0 8 Bug 1067939 JSBridge and Mozmill broken due to let changes in bug 1001090 Please keep in mind that Mozmill 2 0 does not support electrolysis e10s builds of Firefox yet We are working hard to get full support for e10s added and hope it will be done until the next version bump mid of October Thanks everyone who was helping with those releases automation firefox mozmill mozqa Mozilla Firefox Automation report week 29 30 2014 September 8 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 29 and 30 Highlights During week 29 it was time again to merge the mozmill tests branches to support the upcoming release of Firefox 31 0 All necessary work has been handled on bug 1036881 which also included the creation of the new esr31 branch Accordingly we also had to update our mozmill ci system and got the support landed on production The RelEng team asked us if we could help in setting up Mozmill update tests for testing the new update server aka Balrog Henrik investigated the necessary tasks and implemented the override update url feature in our tests and the mozmill automation update script Finally he was able to release mozmill automation 2 6 0 2 two hours before heading out for 2 weeks of vacation That means Mozmill CI could be used to test updates for the new update server Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 29 and week 30 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 29 and week 30 automation ci continuous integration firefox mozmill mozqa Mozilla Firefox Automation report week 27 28 2014 August 13 2014 Henrik Skupin 1 Comment In this post you can find an overview about the work happened in the Firefox Automation team

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