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".
  • Contact | hskupin.info
    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

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


  • Firefox Automation report – Q1 2015 | hskupin.info
    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 tests for Firefox releases executed by the RelEng system to further reduce the amount of time for signoffs from QE About this work I will talk more in my next blog post So please stay tuned Meeting Details If you are interested in further details and discussions you might also want to have

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

  • Mozilla | hskupin.info | Page 2
    04 LTS machines in staging and production which will soon replace the old Ubuntu 12 04 LTS machines A list of the changes can be found here Beside all that Henrik has started to work on the next Jenkins v1 580 1 LTS version bump for the new and more stable release of Jenkins Lots of work might be necessary here Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 45 and week 46 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 45 and week 46 automation ci jenkins mozmill windows Mozilla Firefox Automation report week 43 44 2014 December 18 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 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 on Windows machines per day And that all with the regular release version of Flash which we re installed because of a crash we have seen before was fixed But the healthy period did resist long and we had to revert back to the debug version without the protect mode Lets see for how long we have to keep the debug version active Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 41 and week 42 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 41 and week 42 automation ci firefox flash mozmill QA testing Mozilla Firefox Automation report week 39 40 2014 November 25 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 39 and 40 Highlights One of our goals for last quarter was to get locale testing enabled in Mozmill CI for each and every supported locale of Firefox beta and release builds So Cosmin investigated the timing and other possible side effects which could happen when you test about 90 locales across all platforms The biggest change we had to do was for the retention policy of logs from executed builds due to disk space issues Here we not only delete the logs after a maximum amount of builds but also after 3 full days now That gives us enough time for investigation of test failures Once that was done we were able to enable the remaining 60 locales For details of all the changes necessary you can have a look at the mozmill ci pushlog During those two weeks Henrik spent his time on finalizing the Mozmill update tests to support the new signed builds on OS X Once that was done he also released the new mozmill automation 2 0 8 1 package Individual Updates For more

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

  • Mozilla | hskupin.info | Page 17
    Bereich des Nachrichtenheaders Anhänge von Nachrichten können nun endlich gelöscht werden Hier gibt es aber noch einen Bug in Bezug auf die Entf Taste Nachrichtenfilter unterstützen jetzt auch das automatische Antworten und Weiterleiten von eingehenden E Mails Automatisches Speichern während der Eingabe von Nachrichten Unterstützung von serverseitigen Spam Filtern z B Spamassassin Für weitere Informationen lohnt sich ein Blick in die Release Notes Download Thunderbird 1 5 Alle Sprachen Mozilla Software SeaMonkey 1 0 beta ist da December 21 2005 Henrik Skupin Leave a comment Da das neue Logo für SeaMonkey als Blocker für die Beta Version von SeaMonkey gesetzt wurde und der Entscheidungsprozess mitsamt der Bereitstellung der endgültigen Grafiken etwas auf sich hat warten lassen ist es jetzt aber endlich soweit SeaMonkey 1 0b wurde gestern freigegeben Alle Neuerungen die in dieses Test Release eingeflossen sind werden in den Release Notes erwähnt Die Downloads stehen auf dem FTP Server zur Verfügung englisch deutsch Mozilla Software Firefox 1 5 veröffentlicht November 30 2005 Henrik Skupin Leave a comment Gestern Nacht hat die Mozilla Corporation mit ein paar Stunden Verspätung das neue Release von Firefox veröffentlicht Die über einjährige Entwicklungsdauer für die Version 1 5 hat sich nicht nur optisch gelohnt Stattdessen stecken im Backend jede Menge neuer Features die meist wohl erst mit dem zweiten Blick wahrgenommen werden aber die Bedienung und den Komfort extrem verbessern Alle Änderungen gegenüber den 1 0 x Versionen sind auf englisch in den 1 5 Release Notes nachzulesen Nachfolgend gebe ich einen kurzen Überblick Continue reading Firefox 1 5 veröffentlicht Posts navigation Previous 1 16 17 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

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

  • Review of Firefox desktop automation work – Q1 2016 | hskupin.info
    thorn in our eyes As final result I was even able to completely remove the firefox ui test package so that we are now free in moving our tests to any place in the tree In case you want to know more about our tests please check out our new documentation on MDN which can be found here https developer mozilla org en US docs Mozilla QA firefox ui tests Mozmill CI Lots of changes have been done to this project to accommodate the Jenkins jobs to all the Firefox UI Tests modifications Especially that I needed a generic solution which works for all existing Firefox versions The first real task was to no longer use the firefox ui tests Github repository to grab the tests from but instead let mozharness download the appropriate test package as produced and uploaded with builds to archive mozilla org It was all fine immediately for en US builds given that the location of the test packages json file is distributed along with the Mozilla Pulse build notification But it s not the case for l10n builds and funsize update notifications For those we have to utilize mozdownload to fetch the correct URL based on the version platform and build id So all fine A special situation came up for update tests which actually use two different Firefox builds If we get the tests for the pre build how can we magically switch the tests for the target version Given that there is no easy way I decided to always use the tests from the target version and in case of UI changes we have to keep backward compatibility code in our tests and Firefox Puppeteer This is maybe the most ideal solution for us Another issue I had to solve with test packages was with release candidate builds For those builds Release Engineering is not uploading nor creating any test archive So a connection had to be made between candidate builds and CI tinderbox builds As turned out the two properties which helped here are the revision and the branch With them I at least know the changeset of the mozilla beta mozilla release and mozilla esr branches as used to trigger the release build process But sadly that s only a tag and no builds nor tests are getting created Means something more is necessary After some investigation I found out that Treeherder and its Rest API can be of help Using the known tag and walking back the parents until Treeherder reports a successful build for the given platform allowed me to retrieve the next possible revision to be used with mozdownload to retrieve the test packages json URL I know its not perfect but satisfies us enough for now Then the release promotion project as worked on by the Release Engineering team was close to be activated I heard a couple of days before that Firefox 46 0b1 will be the first candidate to get it tested on It gave

    Original URL path: http://www.hskupin.info/2016/03/31/review-of-firefox-desktop-automation-work-q1-2016/?replytocom=61692 (2016-05-01)
    Open archived version from archive

  • Review of Firefox desktop automation work – Q1 2016 | hskupin.info
    thorn in our eyes As final result I was even able to completely remove the firefox ui test package so that we are now free in moving our tests to any place in the tree In case you want to know more about our tests please check out our new documentation on MDN which can be found here https developer mozilla org en US docs Mozilla QA firefox ui tests Mozmill CI Lots of changes have been done to this project to accommodate the Jenkins jobs to all the Firefox UI Tests modifications Especially that I needed a generic solution which works for all existing Firefox versions The first real task was to no longer use the firefox ui tests Github repository to grab the tests from but instead let mozharness download the appropriate test package as produced and uploaded with builds to archive mozilla org It was all fine immediately for en US builds given that the location of the test packages json file is distributed along with the Mozilla Pulse build notification But it s not the case for l10n builds and funsize update notifications For those we have to utilize mozdownload to fetch the correct URL based on the version platform and build id So all fine A special situation came up for update tests which actually use two different Firefox builds If we get the tests for the pre build how can we magically switch the tests for the target version Given that there is no easy way I decided to always use the tests from the target version and in case of UI changes we have to keep backward compatibility code in our tests and Firefox Puppeteer This is maybe the most ideal solution for us Another issue I had to solve with test packages was with release candidate builds For those builds Release Engineering is not uploading nor creating any test archive So a connection had to be made between candidate builds and CI tinderbox builds As turned out the two properties which helped here are the revision and the branch With them I at least know the changeset of the mozilla beta mozilla release and mozilla esr branches as used to trigger the release build process But sadly that s only a tag and no builds nor tests are getting created Means something more is necessary After some investigation I found out that Treeherder and its Rest API can be of help Using the known tag and walking back the parents until Treeherder reports a successful build for the given platform allowed me to retrieve the next possible revision to be used with mozdownload to retrieve the test packages json URL I know its not perfect but satisfies us enough for now Then the release promotion project as worked on by the Release Engineering team was close to be activated I heard a couple of days before that Firefox 46 0b1 will be the first candidate to get it tested on It gave

    Original URL path: http://www.hskupin.info/2016/03/31/review-of-firefox-desktop-automation-work-q1-2016/?replytocom=61698 (2016-05-01)
    Open archived version from archive

  • 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/ (2016-05-01)
    Open archived version from archive

  • 31 | March | 2016 | hskupin.info
    mozmill ci once Firefox 45 0 and its ESR release were out Adding mach support for Firefox UI Tests on mozilla central was the next step to assist in running our tests Required arguments from before are now magically selected by mach and that allowed me to remove the firefox ui test dependency on firefox harness which was always a thorn in our eyes As final result I was even able to completely remove the firefox ui test package so that we are now free in moving our tests to any place in the tree In case you want to know more about our tests please check out our new documentation on MDN which can be found here https developer mozilla org en US docs Mozilla QA firefox ui tests Mozmill CI Lots of changes have been done to this project to accommodate the Jenkins jobs to all the Firefox UI Tests modifications Especially that I needed a generic solution which works for all existing Firefox versions The first real task was to no longer use the firefox ui tests Github repository to grab the tests from but instead let mozharness download the appropriate test package as produced and uploaded with builds to archive mozilla org It was all fine immediately for en US builds given that the location of the test packages json file is distributed along with the Mozilla Pulse build notification But it s not the case for l10n builds and funsize update notifications For those we have to utilize mozdownload to fetch the correct URL based on the version platform and build id So all fine A special situation came up for update tests which actually use two different Firefox builds If we get the tests for the pre build how can we magically switch the tests for the target version Given that there is no easy way I decided to always use the tests from the target version and in case of UI changes we have to keep backward compatibility code in our tests and Firefox Puppeteer This is maybe the most ideal solution for us Another issue I had to solve with test packages was with release candidate builds For those builds Release Engineering is not uploading nor creating any test archive So a connection had to be made between candidate builds and CI tinderbox builds As turned out the two properties which helped here are the revision and the branch With them I at least know the changeset of the mozilla beta mozilla release and mozilla esr branches as used to trigger the release build process But sadly that s only a tag and no builds nor tests are getting created Means something more is necessary After some investigation I found out that Treeherder and its Rest API can be of help Using the known tag and walking back the parents until Treeherder reports a successful build for the given platform allowed me to retrieve the next possible revision to be used with

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