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 43/44 2014 | hskupin.info
    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 Post navigation Previous Post Firefox Automation report week 41 42 2014 Next Post Firefox Automation report week 45 46 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 December 2014 M T W T F S S Nov Jan 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

    Original URL path: http://www.hskupin.info/2014/12/18/firefox-automation-report-week-43-44-2014/ (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – week 41/42 2014 | hskupin.info
    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 Post navigation Previous Post Firefox Automation report week 39 40 2014 Next Post Firefox Automation report week 43 44 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 December 2014 M T W T F S S Nov Jan 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

    Original URL path: http://www.hskupin.info/2014/12/17/firefox-automation-report-week-41-42-2014/ (2016-05-01)
    Open archived version from archive

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

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

  • Firefox Automation report – week 39/40 2014 | hskupin.info
    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 granular updates of each individual team member please visit our weekly team etherpad for week 39 and week 40 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 39 and week 40 automation ci continuous integration firefox mozmill testing Post navigation Previous Post Firefox Automation report week 37 38 2014 Next Post Firefox Automation report week 41 42 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 November 2014 M T W T F S S Oct Dec 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 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/2014/11/25/firefox-automation-report-week-39-40-2014/ (2016-05-01)
    Open archived version from archive

  • ci | hskupin.info | Page 2
    result the landed changeset URL gets not printed to the console during its landing Henrik fixed that on bug 1010563 now which allows an easier copy paste of the link to our bugs Our team started to work on the new continuous integration system for TPS tests To be able to manage all the upcoming work ourselves Henrik asked Jonathan Griffin to move the Coversheet repository from his own account to the Mozilla account That was promptly done In week 24 specifically on June 11th we had our last automation training day for quarter 2 in 2014 Given the low attendance from people we might have to do some changes for future training days One change might be to have the training on another day of the week Andreea probably will post updates on that soon Henrik was also working on getting some big updates out for Mozmill CI One of the most important blockers for us was the upgrade of Jenkins to the latest LTS release With that a couple of issues got fixed including the long delays in sending out emails for failed jobs For more details see the full list of changes Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 23 and week 24 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 23 and week 24 automation ci firefox jenkins mozmill testing Mozilla Firefox Automation report week 21 22 2014 July 10 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 21 and 22 Highlights To assist everyone from our community to learn more about test automation at Mozilla we targeted 4 full day automation training days from mid of May to mid of June The first training day was planned for May 21rd and went well Lots of people were present and actively learning more about automation https quality mozilla org 2014 05 automation training day may 21st results Especially about testing with Mozmill To support community members to get in touch with Mozmill testing a bit easier we also created a set of one and done tasks Those start from easy tasks like running Mozmill via the Mozmill Crowd extension and end with creating the first simple Mozmill test Something which hit us by surprise was that with the release of Firefox 30 0b3 we no longer run any automatically triggered Mozmill jobs in our CI It took a bit of investigation but finally Henrik found out that the problem has been introduced by RelEng when they renamed the product from firefox to Firefox A quick workaround fixed it temporarily but for a long term stable solution we might need a frozen API for build notifications via Mozilla Pulse One of our goals in Q2 2014 is also to get our machines under the control of PuppetAgain So Henrik started to investigate the first steps and setup the base manifests as needed for our nodes and the appropriate administrative accounts The second automation training day was also planned by Andreea and took place on May 28th Again a couple of people were present and given the feedback on one and done tasks we fine tuned them Last but not least Henrik setup the new Firefox Automation Contributor team which finally allows us now to assign people to specific issues That was necessary because Github doesn t let you do that for anyone but only known people Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 21 and week 22 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 21 and week 22 automation ci firefox jenkins mozmill puppet testing Mozilla Firefox Automation report week 19 20 2014 July 3 2014 Henrik Skupin 2 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 19 and 20 Highlights When we noticed that our Mozmill CI production instance is quickly filling up the data partition and having nearly no space left to actually run Jenkins Henrik did a quick check and has seen that the problem were the update jobs Instead of producing log files with about 7MB in size files with more than 100MB each were present Inspecting those files revealed that the problem were all the SPDY log entries As a fix Henrik reduced the amount of logging information so it is still be helpful but it s not exploding In the past days we also have seen a lot of JSBridge disconnects while running our Mozmill tests Andrei investigated this problem and it turned out that the reduced delay for add on installations were the cause of it Something is most likely messing up with Mozmill and our SOCKS server Increasing the delay for that dialog fixed the problem for now We are using Bugsahoy for a long time now but we never actually noticed that the Github implementation was somewhat broken when it comes to filtering for languages To fix that Henrik added all the necessary language mappings After updating the Github labels for all of our projects we were seeing a good spike of new contributors interested to work with us Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 19 and week 20 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 19 and week 20

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

  • ci | hskupin.info | Page 4
    automation development ci firefox firefox os gaia mozmill Mozilla Automation Development report week 37 2013 September 18 2013 Henrik Skupin 3 Comments Another week passed by and there are only two weeks remaining until the end of Q3 That means we are working eagerly to get the remaining goals finished up Hightlights As of last week we are finally running our Mozmill l10n tests which discover duplicated access keys and cut off elements in our mozmill ci production environment That s a big step forward because with that we no longer have any other test machines which run Mozmill tests on a production like system Everything is combined in a single continuous integration system To make that happen Henrik had to fix a couple of dependencies across mozmill ci mozdownload and down to pulsetranslator As of now we will not regularly check the test results but will report them once in a while Reason for that is the lack of human resources or any automation which syncs the results with the l10n dashboard With yesterdays release of Firefox 24 0 we got another extended support release ESR That means we have to cover both 24 0 x ESR and 17 0 x ESR releases for the next 12 weeks The necessary jobs for mozmill ci have been created and our Pulse listeners adjusted We finally updated our mozmill environment to make use of the new and shiny mozmill automation package That allows us to do signed off releases instead of direct repository checkouts for mozmill ci which caused a bit of breakage since it exists We have new packages available for download for Mozmill 1 5 and 2 0rc5 To let us have an easier transition from Mozmill 1 5 to the upcoming version 2 0 Henrik setup a new mozmill ci instance which runs the same kind of tests as production but with Mozmill 2 0rc5 The setup was already helpful given that we discovered a regression which didn t let us run Mozmill on OS X 10 6 With all the remaining blockers landed we will have another release candidate It will be out this week In terms of Mozmill tests for Firefox we finally were able to separate out tests which make use of remote test data to a separate testrun With that step our functional testrun only uses local resources served via httpd js Big thanks here goes to one of our new contributors with the name Balazs Juhasz Not to leave gaia alone I also want to mention some of the highlights in that area The gaia ui tests for example are using mozdownload now to download b2g desktop builds for testing Support for mobile builds will hopefully land soon too Beside that Dave pushed two software releases of b2gperf 0 7 with logging included and b2gpopulate 0 9 with a fix for nightly builds Last but not least we have to give credits to Johannes who finished the patch to get the first automated

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

  • firefox | hskupin.info | Page 2
    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 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

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

  • firefox | hskupin.info | Page 9
    and FFT test group which do not require a restart of the browser Restart tests The restart tests cover the remaining tests and are able to even test complex paths which require a restart of the browser Now someone may ask how do we track the results There is no one sitting on that machine That s correct Therefor we use the rich feature set of Mozmill 1 4 which is able to send the results as a JSON object to any CouchDB server For our usage inside QA such a server has been setup a while ago and is also used by our Mozmill tests now It s publicly accessible which means that everyone can check and analyze our daily results If you are interested check out the summary page on brasstacks Click on any of the entries to see all the details of each test run For the moment the web interface is really simple and hackish but it gives us the chance to easily track failed tests Within the next weeks or months a couple of improvements have to be made on the client side but also for the web interface In general it covers Finalize the decision which application information has to be acquired by Mozmill and has to be send to brasstacks Make Mozmill more robust against failures The biggest problem we have are modal dialogs which can cause a hang of the complete test run The software update tests have to be fixed to send results for each test module Actually only for the first module results are available Complete new design views are needed to give an easy and structured access to all of the existent results That is probably the biggest chunk A separate blog post will follow once we start to work on that item Even with those tasks in the queue we are ready to run daily Mozmill tests continuously each day and use the same machine for our release testing work As usual we do not rest so expect more to hear about Mozmill testing in the near future automation couchdb firefox Mozilla mozmill Software testing Mozilla Firefox 3 6 and me January 22 2010 Henrik Skupin 1 Comment Yesterday the Mozilla Corporation has been released the brand new Firefox 3 6 which is the successor of Firefox 3 5 and has a couple of interesting new features and speed enhancements aboard Let s have a quick look at the release notes and checkout what makes it a shiny and brilliant new version With the Lightweight Themes support users will be able to skin their browser chrome without having to install Personas Browse through the list of the most popular Personas and hover the different themes to see a preview directly pinned onto your browser A click on Wear It will finally choose the skin The new outdated plug in protection checks the installed plug ins on your system and will warn you when a newer and safer version

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