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".
  • QA | hskupin.info | Page 2
    If you are interested in getting your fingers wet and to help us in making it a helpful and less buggy feature read through the test day documentation and join us next Friday on IRC firefox Mozilla QA testing Mozilla Testday for Testscripting your Add on with MozMill February 25 2010 Henrik Skupin 2 Comments Mozmill which is a framework for running functional tests can be used for any application which is built on top of the Mozilla platform This includes Firefox Thunderbird SeaMonkey and many others But it s not only possible to test the application itself Instead it can also be used to run any type of functional tests for installed add ons To stimulate add on authors to create their own Mozmill tests Mozilla QA is holding a testday on Friday March 5th which is fully devoted to Mozmill testscripting for your add on Learn how Mozmill tests will be written and how they can be run in Firefox The Mozmill team will be around the whole day to assist you wherever possible If you are interested in the testday you should read through the following documentation about the creation of testscripts for extensions You can also attend when you have general questions about Mozmill or when you want to help in creating Mozmill tests for Firefox Get ready and join us in testday next Friday addons event Mozilla mozmill QA testing Mozilla Mozmill talk of FOSDEM 2010 February 7 2010 Henrik Skupin Leave a comment Everyone who was not able to make it to my presentation during the FOSDEM 2010 you can dig into my slides on Slideshare Live demonstrations are not contained Mozilla Automated Mozmill Tests View more presentations from Henrik Skupin firefox fosdem Mozilla mozmill QA talk Mozilla Mozmill 1 3 released November 23 2009 Henrik Skupin Leave a comment Given the quick review on AMO many thanks to you guys that this happened under a week the Mozmill team can call out that Mozmill 1 3 has been released It s available for download on addons mozilla com This release is a big step forward by adding a couple of new features and fixing some important bugs which have been found by users and have been introduced by the last release A complete list can be found on Bugzilla Let s give a short overview and mention some of the fixes features Bug 509912 We have updated the maxVersion for all applications So Mozmill is not compatible up to Firefox 3 7a1pre Thunderbird 3 1a1pre and SeaMonkey 2 1a1 Bug 508643 From now on new profiles are created by Firefox itself Before that fix we have used the files from within the default profile folder of the default application That caused failures for localized builds because the profile has been initialized with wrong profile data Bug 516729 Tests failed by clicking on elements inside the content area if the window was too small Now with this fix elements will be scrolled into view

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

  • QA | hskupin.info | Page 3
    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 have most of them available as soon as possible Do you have further ideas how Mozmill can be used in the l10n area additionally to the points I have pointed out in my slides Thanks in advance for your feedback Mozilla mozmill QA Software testing Mozilla Getting hired by Mozilla January 15 2009 Henrik Skupin 8 Comments Actually this post should have been already written last Monday but there were too many things going on But lets start now It was an unbelievable Monday And definitely the best one ever in my life After 8 years of active contribution to the Mozilla project I was getting hired by Mozilla Means from now on I work as a full time QA engineer in the QA execution team And like any other remotely connected office less person I m working from home For now I m based in Karlsruhe which is located at the west side of Germany But after years away from my homeland I will move back and enjoy the

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

  • Firefox Automation report – week 37/38 2014 | hskupin.info
    for a specific build from out dashboard and outputs the failure rate per executed testrun We were totally happy to see that the failure rate for all Mozmill tests was around 0 027 During the merge process for the Firefox 32 release Andrei has seen some test inconsistencies between our named branches in the Mozmill Tests repository Some changes were never backported and only present on the default branch for a very long time He fixed that and also updated our documentation for branch merges Something else worth for highlighting is also bug 1046645 Here our Mozmill tests found a case when Firefox does not correctly show the SSL status of a website if you navigate quickly enough The fix for this regression caused by about newtab made it even into the release notes Last but not least Andreea started planning our Automation Training day for Q3 So she wrote a blog post about this event on QMO Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 37 and week 38 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 37 and week 38 automation firefox mozmill testing Post navigation Previous Post Firefox Automation report week 35 36 2014 Next Post Firefox Automation report week 39 40 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

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

  • Firefox Automation report – week 35/36 2014 | hskupin.info
    we have created an etherpad If you are interested in helping us with Mozmill tests you can now find a list of mentored and good first bugs on the bugsahoy web page Because of the app bundle changes on OS X which were necessary due to the v2 signing requirements we had to fix and enhance a couple of our automation tools Henrik updated mozversion mozmill and mozmill automation We were close to releasing Mozmill 2 0 7 Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 35 and week 36 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 35 and week 36 automation firefox firefox automation mac os x mozmill testing Post navigation Previous Post Erster offizieller Halbmarathon Next Post Firefox Automation report week 37 38 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 sharing information inside the Firefox Automation team November 23 2015

    Original URL path: http://www.hskupin.info/2014/11/06/firefox-automation-report-week-35-36-2014/ (2016-05-01)
    Open archived version from archive

  • mac os x | hskupin.info
    nearly immediately mac os x maemo mobile n900 Software Software Change Mac OS X Keybindings September 7 2009 Henrik Skupin Leave a comment The last days I searched for a way how to modify some of the default keybindings for my Mac OS X installation While searching the web I found the blog of Llew Mason who wrote a nice article about it some years ago keyboard mac os x navigation Software Mac Software Keychain forgets saved passwords or not November 26 2007 Henrik Skupin 7 Comments Yesterday I was really shocked After reactivating my MacBook from stand by mode I wanted to burn a DVD with exported pictures I copied all files into the burning folder and started the process From now on the whole system was curiously pretty slow I never had this before No idea if the burning process was responsible for that But anyway let us talk about the real problem I opened Adium to check if a friend is online But instead of getting my contact list a password dialog was shown Damn what s that Most of my passwords are stored within Keychain Why I have to enter a password now Afraid of the thing happened I started the Keychain application and I was taken my breath away No password certificate or notes were visible All entries were completely gone The only thing I saw was a bright and white background But that s not what I wanted to see I was ebbed between waiting to finish the burning process or executing a restart immediately Finally I decided to wait because there is no reason why it should getting worse While the burning process wasn t finished I restarted Keychain but without luck It seems that all my stored sensitive data was lost But stop Let s run a restart first After taken the DVD out of my drive I did a restart All the while I hold my fingers crossed Please please please give me back my data In such situations a restart takes a really long time I entered my password and opened Keychain after my profile was loaded The applications window was shown and what I saw made me really really happy All the entries were visible again and saved me from hacking them in again I still have no idea what s happened here and why they are back again But I m glad to have them back and I m still interested for an explanation Anyone of you who had a similar experience What was your result Did you get back your stored passwords apple mac os x security Software Mac Software Mac OS X 10 5 alias Leopard available October 27 2007 Henrik Skupin 2 Comments It was a long time for everyone who is interested in Mac OS X to wait for the upcoming 10 5 release alias Leopard Even after Apple Inc announced its brand new mobile phone iPhone and shifted the release forward further 6

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

  • testing | hskupin.info | Page 2
    appropriate reviewers for their patches more easily Henrik requested to setup default reviewers on Bugzilla The changes are now in place and the list points to Andreea Andrei and Henrik To follow our goals in educating more people about automation we also have to reach out more on Github to actually find interested people Therefore Henrik requested a Github mirror of our mozmill tests repository It s available at https github com mozilla qa mozmill tests now With the last release of Mozmill 2 0 6 we got the mozcrash packages included So far we aren t able to process stacktraces given that the necessary crashreporter symbols were not available for daily builds of Firefox on the FTP server This has been fixed now for all kinds of daily builds As seen for the last beta and final releases of Firefox we still have a good amount of broken configuration files for ondemand update tests in Mozmill CI Those are failures done by the person who runs those tests but also by broken behavior in the mciconf tool Given that we want to put more focus on the full automation stack for update tests now To get started we need appropriate notifications send out by Mozilla Pulse Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 17 and week 18 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 17 and week 18 automation ci contribution firefox automation mozmill testing Mozilla Firefox Automation report week 15 16 2014 June 3 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 15 and 16 Highlights To be able to support the new update path for Firefox Beta users via a final release candidate on the beta channel we had to update our update testruns with Mozmill in the mozmill automation repository Further we also had to add support for this update path in Mozmill CI Cosmin spend his time on those patches and finally we got those out and active That means from now on our software update tests can handle Firefox X 0b9 Firefox X 0RC Firefox X 1 0b1 updates More information can be found on bug 960781 We also pushed some other updates for Mozmill CI to our production system which includes timestamps for the log output of the pulse listener and the addition of the application name for the product to test The latter was necessary for MetroFirefox But even after we stopped support for it we wanted to see it landed given that we could add other products more easily in the future Also Henrik pushed a change for Mozmill CI which removed support for running localized versions of Firefox Nightly builds This was necessary so that our systems can be better utilized for those Aurora and Beta builds where actually most of the localization work is happening Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 15 and week 16 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 15 and week 16 automation ci firefox automation mozmill testing Mozilla Firefox Automation report week 13 14 2014 May 9 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 13 and 14 Highlights Finally we were able to upgrade our mozmill ci production system to Mozmill 2 0 6 The only caveat is that we had to disable one test for cleaning history to prevent the always occurring Flash crash on Windows This week Henrik was able to land the first fixes for broken TPS tests Together with Andrei we were able to fix 4 of them Also we had our first Automation Training days The first one on Monday was a huge success and we have seen lots of new faces Sadly the second one on the following Wednesday we haven t announced separately so lesser people joined our training In the future we will make sure to announce each Automation Training day separately Also there will be only a single one in a full week so it will allow people to do some homework until the next session In week 14 we released version 2 0 6 1 of our mozmill automation package It was necessary to allow QA to run the Mozmill update tests with overriding the update channel so update tests from a release candidate to the next beta build can be performed After we discovered even more Flash crashes of the same type we decided to use the debug version of Flash on our Windows systems Main reason is that those builds don t crash Sadly given that they would give us way more information But Adobe should at least know where the crash is happening Also given that we do not have any private data on our test machines we decided to actually upload a minidump from one of those crashes to Bugzilla This information actually helped Adobe a lot So we will continue doing that Last but not least Henrik was able to fix another 7 bugs for TPS Those were broken tests a broken behavior of the TPS test extension or enhancements Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 13 and week 14 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

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

  • testing | hskupin.info | Page 8
    subgroups and their prioritization can be found in the Feature Ownership document For us who are working on release testing software update tests have to be performed for the betatest beta releasetest and release channels Given the manual work which have to be performed here automation will help a lot I will finalize my software update tests so they can be run by everyone Running Mozmill tests you will 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

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

  • Firefox Desktop automation goals Q1 2016 | hskupin.info
    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 this goes More details about that can be found on bug 1237552 automation ci continuous integration firefox marionette QA Post navigation Previous Post Review of automation work Q4 2015 Next Post Review of Firefox desktop automation work Q1 2016 Logging In Post a Reply to Planet Ateam cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me

    Original URL path: http://www.hskupin.info/2016/02/02/firefox-desktop-automation-goals-q1-2016/?replytocom=60609 (2016-05-01)
    Open archived version from archive