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".
  • mozmill | hskupin.info | Page 2
    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 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 during week 27 and 28 Highlights Henrik continued his work on our QA specific PuppetAgain setup One of the blockers for us was bug 997721 which is the full proxy support on OS X and Linux By week 27 we were finally able to get this finished Further Henrik also got the manifest for installing Java done On TPS we also made progress So Cosmin got the Pulse listener script implemented for the Coversheet CI which triggers TPS tests whenever new nightly builds of Firefox have been made available Further a couple of fixes for Mozrunner were necessary given that the 6 0 release caused a couple of regressions for TPS As result we agreed on to pin Python package dependencies to specific versions of mozrunner and related packages One big thing for our team is also to assist people in the decision if automated tests are possible for certain Firefox features The questions mainly come up for tests which cannot be implemented for any of our developer driven test frameworks due to limitations on buildbot no network access allowed restart of the application and others To be more successful in the future Henrik started a discussion on the dev quality mailing list We hope to get the proposed process established for bug verification Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 27 and week 28 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 27 and week 28 automation ci firefox firefox automation mozmill mozqa Mozilla Firefox Automation report week 25 26 2014 July 17 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 25 and 26 Highlights June the 11th was actually the last Automation Training day for our team in Q3 About the results you can read here We will implement some changes for the next quarter when we most likely want to host 2 of them Henrik finally got the time to upgrade our Mozmill CI systems to the lastest LTS version of Jenkins There were a bit of changes necessary but in general all went fine this time and we can see some great improvements Especially the long delays when sending out job results seem

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

  • mozmill | hskupin.info | Page 10
    get results reported in the terminal Even with the integrated capability to send those reports to a server we don t have a web frontend to display those results We want to use Brastacks to visualize Mozmill results similar to the Fennec test results This work will be a joined effort with Testdev If anyone is interested in helping us to write or maintain Mozmill tests you can read more about it in the test creation tutorial or simply join us on IRC and get in contact with whimboo or aakashd But you can also send me a mail or comment on this blog post Thanks Mozilla mozmill QA Software testing Mozilla Software Mozmill meets L10n slides available October 6 2009 Henrik Skupin 3 Comments Over the last weekend Mozilla Camp Europe 2009 has been taken place in Prague About 150 people from l10n qa dev and advocacy were invited to join this conference which Mozilla Europe is organizing each year Given my project to get manual Litmus tests automated with Mozmill I have prepared some slides with a special focus on l10n But sadly I wasn t able to join the conference because of sickness I have to say a big thanks to my colleague Marcia Knous and also to one of our main contributors for Sunbird tests Merike Sell who both hold the session As informed at the end of the session via IRC the talk was a great success and a lot of questions were ask Due to the amount of sessions not everyone was able to join the Mozmill session Also given all the people who weren t be able to come I have uploaded my slides for all of you now Please check the embedded Slideshare content below Mozmill meets L10n View more documents from Henrik Skupin Feedback Because I haven t got any feedback from localizers so far I m anxious to hear what you think about the usefulness of Mozmill and testing with localized builds Given by the current number we have over 70 official locales available which are not tested by automated tests and require manual testing from localizers and contributors on a regular basis With all the 250 BFT and another 750 FFT tests enabled in Litmus manual testing is a time taking action Running all the tests with Mozmill will take much lesser time could be run more often and could cover all platforms which will result in a higher quality of Firefox and helps us to minimize any new regressions for our huge user base Please check the following questions I m interested in getting an answer How often does your l1on team run Litmus tests against your locale whether those are BFT FFT or the localizer test run Would you like to see much of those tests automated and are you interested in running those tests on your local machine for each major and stability release Are you interested to help QA in writing Mozmill tests so we

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

  • Mozmill 2.0 released! | hskupin.info
    it out soon But since then an amazing number of additional 276 changesets have been landed and another nearly 2 years passed by Amazing how your own schedule can be busted But there was no way around In the last couple of months our Automation Development team has fully taken over the project and promised to get it finished and released It was a kinda tricky and hard task especially with all the additional bugs we have identified which not only caused broken tests but also crashes and dataloss Thanks to the help of our awesome contributors who spend tons of hours to put a nice and polished version of Mozmill together We wouldn t have been here without your help A big big thanks One of the things we are most proud of is the backward compatibility of Mozmill 2 0 We made it that as a Mozmill 1 5 user you shouldn t see any difference Any method and property available in Mozmill 1 5 is still present in 2 0 but has been marked as deprecated With that you will be able to run all of your tests with both versions and you can transition over step by step There are indeed some new ways how to work with elements which are explained on our MDN Mozmill page One very impressive improvement we have seen a couple of days ago is the speed how Mozmill tests are getting executed Compared to Mozmill 1 5 we can see a drop of the duration by a factor of 2 5 That s two and a half times faster I think already because of that you should not miss to at least test Mozmill 2 0 As usual please give us feedback via email or on IRC about your own experiences and please report any bug you have discovered If you like hacking and want to help us with the implementation of new features or fixing broken behavior then have a look at our Mozmill repository on Github Soon I will come up with our plan for the future of Mozmill And what I can say as of now there is a lot to come automation automation development firefox mozmill Software testing Post navigation Previous Post Automation Development report week 38 2013 Next Post Double check to disable Firefox Sync when doing a regression test to not loose important profile data 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 9 Replies 1 Comment 7 Tweets 0 Facebook 0 Pingbacks Last reply was September 26 2013 Planet Ateam View September 25 2013 Henrik Skupin Mozmill 2 0 released http t co maKhPACp5b Reply planetmozilla View September 25 2013 Henrik Skupin Mozmill 2 0 released http t co MQLLQLysoS Reply William Lachance View September 25 2013 Great news Big congrats to all involved Reply MozillaZineFr View

    Original URL path: http://www.hskupin.info/2013/09/25/mozmill-2-0-released/ (2016-05-01)
    Open archived version from archive

  • Mozmill 1.5.22 and 2.0rc5 released | hskupin.info
    worth the time In all those weeks we fixed 32 bugs for Mozmill and 4 bugs for JSBridge The most important changes are JSBridge forced single and multiple conversions of strings to unicode where it was not necessary As result sent data was not correctly transmitted or completely dismissed That was a pain given that test results were inaccurate 761603 In some cases Mozmill failed to send data during the shutdown of the application via the bridge to the Python process As result we hit an assertion and with debug builds the application crashed due to an invalid access to an object in our socket implementation via NSPR 865690 Another problem in our socket implementation was the missing handling of failed send requests Before the patch has been landed JSBridge simply ignored that and we hit a dataloss issue when too much information had to be send through the bridge 764640 Our local HTTP server based on httpd js was instantiated once for each test This caused a lot of trouble and overhead Now it is created on startup of the application and keeps running until shutdown With that you will also be able to use it while Mozmill is in manual mode 881657 Various changes to the restart logic have been included With that we also got our state machine implemented for restart tests 895657 Specifically for Metro Firefox we landed support for new touch events 880426 Full details about the underlying changes in RC5 can be found in the changelog for Mozmill 2 0rc5 and JSBridge 3 0rc5 automation firefox mozmill Software testing Post navigation Previous Post Automation Development report week 34 2013 Next Post Mozdownload 1 9 released Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website

    Original URL path: http://www.hskupin.info/2013/08/28/mozmill-1-5-22-and-2-0rc5-released/ (2016-05-01)
    Open archived version from archive

  • MozInstall 1.0 released | hskupin.info
    able to adapt to it easily It was necessary before more and more projects rely on this package For any details please see the appropriate README file Otherwise here some examples CLI cd Volumes mozilla builds mozinstall firefox 13 0 en US dmg Volumes mozilla builds FirefoxAurora app Contents MacOS firefox mozuninstall firefox With those two commands the specified DMG image of Firefox 13 will be installed into a sub folder of the current working directory and removed right after The installer will print the location of the actual binary to stdout API import mozinstall path mozinstall install firefox 13 0 en US exe print mozinstall get binary path firefox mozinstall uninstall path This code is the equivalent to the CLI example above It installs Firefox into a sub folder of the current working directory and returns the path With the call to get binary and by specifying the type of application the actual binary will be returned Replace firefox with thunderbird if you want to install a Thunderbird build Finally the uninstaller expects the path Firefox has been installed into and removes the application automation firefox mozbase Software testing Post navigation Previous Post Mozmill 1 5 12 dropped support for Firefox 3 6 Next Post New in qa testsuite flag available for Mozilla QA driven test frameworks 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 June 2012 M T W T F S S May 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 Recent Posts Review of Firefox desktop

    Original URL path: http://www.hskupin.info/2012/06/11/mozinstall-1-0-released/ (2016-05-01)
    Open archived version from archive

  • mozbase | hskupin.info
    like the mozdownload one will be created Keep in mind that this release changes the API of several functions We are aware of that and hope that everyone of you will be able to adapt to it easily It was necessary before more and more projects rely on this package For any details please see the appropriate README file Otherwise here some examples CLI cd Volumes mozilla builds mozinstall firefox 13 0 en US dmg Volumes mozilla builds FirefoxAurora app Contents MacOS firefox mozuninstall firefox With those two commands the specified DMG image of Firefox 13 will be installed into a sub folder of the current working directory and removed right after The installer will print the location of the actual binary to stdout API import mozinstall path mozinstall install firefox 13 0 en US exe print mozinstall get binary path firefox mozinstall uninstall path This code is the equivalent to the CLI example above It installs Firefox into a sub folder of the current working directory and returns the path With the call to get binary and by specifying the type of application the actual binary will be returned Replace firefox with thunderbird if you want to install a Thunderbird build Finally the uninstaller expects the path Firefox has been installed into and removes the application automation firefox mozbase Software 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 up January

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

  • Mozmill 1.5.12 released | hskupin.info
    a good portion of my Saturday and Sunday evening to put together a patch which removed the broken code in waitForPageLoad and replaces it with the new API So by now we do no longer add a custom mozmillDocumentLoaded property to all windows but have a nice windowMap object that handles all the loaded states of each window on its own I think that s great and modifying the DOM of each window was even a bad idea since the beginning of the project Good to see that killed That means early today we got all patches landed and I was able to release Mozmill 1 5 12 to PyPI and even the uploaded extension on addons mozilla org has been approved in the meantime If you haven t updated yet and you make use of Nightly builds you should do it now Lets cross the fingers that no other unexpected issues will arise and force another 1 5 branch release firefox mozmill mozqa Software testing Post navigation Previous Post Nightly Tester Tools 3 3 released Next Post Automation Development Team and Q2 Goals 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 2 Comments 0 Tweets 0 Facebook 0 Pingbacks Last reply was May 8 2012 Mike Conley View May 7 2012 Henrik On behalf of the whole Thunderbird team thanks so much for your work this weekend Mike Reply Henrik Skupin View May 8 2012 You are welcome Important issues have to be fixed ASAP Good to see that I was able to bring tests for Thunderbird back to life again Reply Photostream May 2012 M T W T F S

    Original URL path: http://www.hskupin.info/2012/05/07/mozmill-1-5-12-released/ (2016-05-01)
    Open archived version from archive

  • MemChaser 0.3 is out | hskupin.info
    preferences to any folder you like To help new users of the extension to understand the entries in the widget tooltips have been added Those will inform you about the background of the individual values This was a request by a couple of users so we wanted to have this included too If you are interested in all the changes happened in the 0 3 release you can find the complete list as usual on our MemChaser issue tracker This version of MemChaser has still been built on top of the Add on SDK 1 5 because we wanted to get out all of those new features also to our Firefox 10 0 user base which is about 28 of all our users This was more important to us compared to fixes we would have benefit from the SDK 1 6 But at this time we want to announce that version 0 3 will be the last release which officially supports Firefox 10 With version 0 3 1 which will be released in the next one or two weeks a version bump to the SDK 1 6 will be done to fix the before mentioned issues like memory leaks If you are interested in helping us in the implementation of new features or fixing bugs please check our issue tracker for open issues and contact us on IRC in the automation channel addons firefox memory mozqa Software Post navigation Previous Post Nightly Tester Tools 3 2 2 released Next Post Mozmill 1 5 11 released 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 2 Comments 0 Tweets 0 Facebook 0 Pingbacks Last

    Original URL path: http://www.hskupin.info/2012/04/07/memchaser-0-3-is-out/ (2016-05-01)
    Open archived version from archive