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 1.4.1 released | hskupin.info
    ons Therefore we have to make sure that the usage of Mozmill will be as easy as possible That s why the misleading plugin command line option has been changed to addons Make sure to use this option from now on Bug 548446 Mozmill had problems with installing some of the existing extensions because it was not able to find the extension id Thanks goes to Jonathan Bug 544896 If you have long test runs it was possible that the software update dialog came up and removed the focus from the window currently under test That s why the automatic update for the application has been disabled If you want to run tests against that feature make sure to enable the preference app update enabled before Bug 558404 and Bug 559152 Some controller functions have been updated which missed some details about failures Now we always have a stacktrace with full information available The new version of the add on can be found on addons mozilla org It s under review right now but can already be installed For all the others who are using the command line client of Mozmill you can simply run the easy install U mozmill command to update to the new 1 4 1 release If you have questions don t hesitate to send your feedback to the mozmill dev mailing list or directly contact us on IRC in the qa channel automation firefox Mozilla mozmill Software testing Post navigation Previous Post Phototour in the Napa Valley Next Post First relaxing biking tour 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 April 2010 M T W T F

    Original URL path: http://www.hskupin.info/2010/04/15/mozmill-1-4-1-released/ (2016-05-01)
    Open archived version from archive


  • Daily automated Mozmill test-runs in the QA Lab | hskupin.info
    run is given by Software Update tests With the software update tests we check that nightly updates can be downloaded and applied via the software update dialog Also we make sure to run the successive Mozmill tests against the most recent nightly build Normal tests Those tests cover most of our implemented tests for the Smoketests BFT 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 Post navigation Previous Post Mozmill 1 4 released Next Post Mozmill talk at FOSDEM 2010 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 4 Replies 4 Comments 0 Tweets 0 Facebook 0 Pingbacks Last reply was January 31 2010 Aaron Train View January 29 2010 Thanks for posting this I was curious as to how it was all coming together

    Original URL path: http://www.hskupin.info/2010/01/29/daily-automated-mozmill-test-runs-in-the-qa-lab/ (2016-05-01)
    Open archived version from archive

  • Mozmill 1.4 released | hskupin.info
    a lot For more information check out the complete list of fixes Mozmill 1 4 is still in the review queue on addons mozilla org It will take a bit until it is officially available there So for now grab a copy from Mikeal s repository and give it a try Mozilla mozmill Software testing Post navigation Previous Post Firefox 3 6 and me Next Post Daily automated Mozmill test runs in the QA Lab 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 5 Comments 0 Tweets 0 Facebook 0 Pingbacks Last reply was January 25 2010 Siddharth Agarwal View January 25 2010 1 The link to AMO is de please link to en US 2 There s still one dependency on pywin32 as harthur points out in the bug Reply Henrik Skupin View January 25 2010 Thanks for the notice I have updated the link on AMO For bullet point 2 I feel that it will not affect as many users Probably it only happens when using Mozrunner instead of Mozmill It should be handled as a separate bug and fixed for the next release Reply Siddharth Agarwal View January 25 2010 Well the commandline version of Mozmill uses Mozrunner to run Fx Tb right AFAIK that s the version of Mozmill which had the pywin32 dependency in the first place Reply Tony View January 25 2010 python callbacks and restart test reporting Woohoo Nice work to all those involved BTW typo in your last paragraph referencing addons mozilla org Reply Henrik Skupin View January 25 2010 Sid this is really strange We will track that issue in Bug 542000 Reply

    Original URL path: http://www.hskupin.info/2010/01/25/mozmill-1-4-released/ (2016-05-01)
    Open archived version from archive

  • couchdb | hskupin.info
    documentation up on MDC which helps to make the task as easy as possible To be able to share builds scripts and other stuff between the vms each of those has the shared folders feature enabled and a virtual drive connected to the data partition For the daily test runs against en US nightly builds of Firefox 3 6 x Namoroka and Firefox 3 5 x Shiretoko we decided to have OS X 10 5 Ubuntu 9 10 and Windows XP always open With the help of the crontab on Linux and OS X and the scheduled tasks on Windows we are able to start the tests at the same time each day Given by the availability of the update snippets we have chosen 8am PDT for now I m not sure if that will work every day due to some slightly time shifts but it s still something we have to improve To run all the available tests I have written a wrapper script in Python which runs each of the different tests sequentially This script will be used from any of the above mentioned vms The order how the tests are run is given by Software Update tests With the software update tests we check that nightly updates can be downloaded and applied via the software update dialog Also we make sure to run the successive Mozmill tests against the most recent nightly build Normal tests Those tests cover most of our implemented tests for the Smoketests BFT 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

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

  • Automated Software Update tests with Mozmill | hskupin.info
    channel tests the update snippets which have been pushed to our official download mirrors release Default channel for all Firefox installations to get the next version For each of those mentioned channels we offer partial and complete updates The former one will be used if the latest minor version of Firefox is in use e g a user wants to update from 3 5 4 to 3 5 5 while the latter one is for all other versions of the same branch If an update fails to apply which could happen due to different reasons like a download problem users will not get stuck on their installed version In such a case a fallback update will be downloaded which is identical to the complete update If that fails too the same process will be started again after a given time Until now these tests had to be done manually by us An example can be seen in the update section of the Firefox 3 5 5 test plan So we normally tests updates on all supported platforms for each update type minor major and make sure that fallback updates will pass With the new software update tests for Mozmill which I have finished two days ago we can easily automate this process now The only manual steps which have to be done is to prepare the tests by downloading the necessary builds for all the platforms and place them in their own folders Once that is done the automated test can be started It will use all builds within a given folder and runs tests updates for the specified channel The results are printed in wiki format to the console and only have to be copied to the appropriate Wiki page If you are interested in running those update tests you have to install Mozmill on your machine and clone our Mozmill test repository Detailed steps can be found in the Mozmill test creation tutorial on QMO This is a big step forward in a direction where we can run update checks against each localized build of Firefox and can make sure that updates are successfully applied and don t fail or cause any sort of failure And it will give QA more time to focus on other topics If you are interested and want to know more about Mozmill then join us in QA on IRC or subscribe to the Mozmill developer list automation Mozilla mozmill QA Software testing update Post navigation Previous Post Minimalism pictures are not interesting anymore create movies Next Post Mozmill 1 3 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 1 Reply 1 Comment 0 Tweets 0 Facebook 0 Pingbacks Last reply was November 18 2009 Nick Thomas View November 18 2009 To clarify the use of the channels beta all alpha and beta builds ship on

    Original URL path: http://www.hskupin.info/2009/11/18/automated-software-update-tests-with-mozmill/ (2016-05-01)
    Open archived version from archive

  • update | hskupin.info
    installations to get the next version For each of those mentioned channels we offer partial and complete updates The former one will be used if the latest minor version of Firefox is in use e g a user wants to update from 3 5 4 to 3 5 5 while the latter one is for all other versions of the same branch If an update fails to apply which could happen due to different reasons like a download problem users will not get stuck on their installed version In such a case a fallback update will be downloaded which is identical to the complete update If that fails too the same process will be started again after a given time Until now these tests had to be done manually by us An example can be seen in the update section of the Firefox 3 5 5 test plan So we normally tests updates on all supported platforms for each update type minor major and make sure that fallback updates will pass With the new software update tests for Mozmill which I have finished two days ago we can easily automate this process now The only manual steps which have to be done is to prepare the tests by downloading the necessary builds for all the platforms and place them in their own folders Once that is done the automated test can be started It will use all builds within a given folder and runs tests updates for the specified channel The results are printed in wiki format to the console and only have to be copied to the appropriate Wiki page If you are interested in running those update tests you have to install Mozmill on your machine and clone our Mozmill test repository Detailed steps can be found in

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

  • automation | hskupin.info | Page 9
    Tests for add ons crash Crash tests endurance Endurance tests functional Functional tests for Firefox restartTests Functional restart tests l10n l10n tests update Update tests templates Simple templates for starters As you can see sections are clearly defined and it s easy to find the code you are looking for It s the perfect base for our future work you will hear about in the next couple of weeks automation firefox mozmill mozqa testing Mozilla Mozmill 1 5 2 and changes for running Firefox tests February 28 2011 Henrik Skupin Leave a comment As Clint Talbert has already written on Friday last week Mozmill 1 5 2 has finally been released A lot of great new stuff is now part of Mozmill core and we are happy to use it in our tests and automation scripts in the next couple of weeks The following changes will have to be made With the nearly complete refactoring of the Mozmill Python modules our Mozmill wrapper used by the automation scripts is no longer necessary and needs to be removed For me it means I have to complete rewrite the automation scripts With those changes implemented we will no longer be backward compatible to former Mozmill releases Mozmill can now run a list of specified tests from the command line We want to use that feature to allow users of the Mozmill Crowd extension to run selected tests in a given order That means that the automation scripts will have to support this feature and I will take care about in the rewrite We have disabled the compatibility check for add ons in Firefox 4 That was necessary because lot of add ons aren t compatible yet and weren t correctly installed from the command line when specified via the addons option Now we also want to support it in our automation scripts Failures for fatal and non fatal assertions are now using the same structure which is important for our Mozmill Dashboard and especially for the l10n testrun results which mostly contain results of non fatal assertions I m looking forward to see all the mentioned enhancements active in March Those are a big step forward also for our users of the Mozmill Crowd extension automation firefox mozmill QA testing Mozilla Mozmill Crowd talk at FOSDEM 2011 February 14 2011 Henrik Skupin Leave a comment A week ago I had the pleasure to attend the FOSDEM Free and Open source Software Developers European Meeting in Brussels As every year Mozilla has been setup its own booth and also got assigned an own developer room for talks I have used this opportunity to spread the word about our crowd testing initiative with Mozmill Crowd Thanks to the committee my talk also got approved and I was able to demonstrate our latest activities in front of a couple of people If you weren t able to attend you can check my slides below or on Slideshare Mozmill Crowd View more presentations from Henrik Skupin I have to thank everyone for the amazing feedback A lot ideas have been collected during those 2 days which now need to be injected into our roadmap One of the most important items is definitely the way how we offer a testing solution for add ons Because of the Jetpack team already offers unit tests via the Addon SDK framework we should work together to get more add on authors to create tests for their add ons but also to being able to collect more test results from our testing community It s absolutely an item for me after Firefox 4 has been released and we have finished our refactoring of the shared modules used by our Mozmill tests So assume updates by next quarter Beside my own activities I was able to visit some other booth and finally got in contact with Bernhard Wiedemann from the openSUSE project who now also runs our Mozmill tests on a daily basis on their machines I m kinda inspired by some of the features they are using especially the creation of a video for the complete test run Features like those would have been already helped us a lot It s nothing more frustrating to not being able to reproduce an issue because of lack of information A big thanks goes also to the planning team of Mozilla who took care of anything related over this weekend Thanks for the accommodation the dinner and bowling party on Saturday and all the other small but necessary stuff As always it was great to get in contact with our and external communities Oh and some pictures have been uploaded to Flick automation crowd event firefox fosdem Mozilla mozmill mozqa testing Mozilla 1 Click Firefox functional testing with Mozmill Crowd January 18 2011 Henrik Skupin Leave a comment Firefox 4 the next major version of Mozilla s web browser will include hundreds of new features and enhancements A lot of those will happen in the background and will primarily not be visible at the front end A very good example for such a feature is the support for graphics hardware acceleration It will drastically improve the rendering of pages videos or the Firefox UI itself But noticeable it is only because it is that fast Alongside those back end features also the Firefox UI has been vastly changed Mainly you will notice the reduced amount of visible elements in the browsers chrome or the newly introduced Firefox button on Windows and Linux at the top left side of the window To ensure that those new features or landed changes work as expected Mozilla QA and all our testers have to constantly run manual tests for those areas which cannot be automatically tested by a Mochitest To make the life of all of us easier we have been actively working on getting even those areas populated with functional automated tests by using our own testing framework called Mozmill While all that testing with Mozmill is

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

  • Firefox Automation report – week 51/52 2014 | hskupin.info
    Mozmill test framework Henrik started to mass close existing bugs for Mozmill So only a hand full of bugs will remain open If there is something important you want to see fixed we would encourage you to start working on the appropriate bug For Mozmill CI we got the new Ubuntu 14 10 boxes up and running in our staging environment Once we can be sure they are stable enough they will also be enabled in production Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 51 and week 52 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 meeting of week 51 and week 52 automation ci firefox marionette mozmill mozqa testing Post navigation Previous Post Firefox Automation report week 49 50 2014 Next Post Firefox Automation report Q1 2015 Logging In Post a Reply to PlanetFeeds cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 3 Replies 0 Comments 3 Tweets 0 Facebook 0 Pingbacks Last reply was March 2 2015 PlanetFeeds View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 In this post you can find an overview about the wo http t co ZUibrCoHft Reply Planet Ateam View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 http t co 60S1TxfeTI Reply planetmozilla View March 2 2015 Henrik Skupin Firefox Automation report week 51 52 2014 http t co X2lkkFF1zk Reply Photostream March 2015 M T W T F S S Jan May 1

    Original URL path: http://www.hskupin.info/2015/03/02/firefox-automation-report-week-51-52-2014/?replytocom=47704 (2016-05-01)
    Open archived version from archive