Tag Archives: training

Last Automation Training day for this quarter

Today we hold our last Automation Training day for this quarter. So if you want to learn something about test automation at Mozilla, feel free to join at any time during the day. We are around all day, waiting to answer your questions, and to get you started if you want to contribute to one of our projects.

Please have a look at our etherpad for the current status:
https://etherpad.mozilla.org/automation-training

I’m looking forward to see some of you!

Automation Training Day on May 21st

For anyone who is interested in Test Automation we offer again a full day of trainings. You will be able to learn more about Javascript and Python, which are the languages used a lot for projects in our Automation team.

All the details about this all day event you can read here.

Please spread the news around so that we will have a fruitful day with a lot of discussions, and small or larger tasks accomplished.

Firefox Automation report – week 11/12 2014

In this post you can find an overview about the work happened in the Firefox Automation team during week 11 and 12.

Highlights

After Henrik got started on updating the TPS test framework for Firefox Sync tests, he got it into a state that it is working with the new Firefox Accounts feature coming with Firefox 29.0. For details please see bug 966434. Fixing the backward compatibility for the old Sync authentication is his next step.

With the release of Mozmill 2.0.6 and the initial support of handling crashes, we found a major Adobe Flash crash on our Windows nodes when clearing cookies. We started to investigate and reported the problem appropriately, so that Adobe is aware of it.

For other crashes which are related to Firefox directly we would still have to retrieve and print the stack to the console. But we cannot do this until the crashreporter symbols are available for Nightly builds on ftp.mozilla.org. We will continue implementing this feature into Mozmill once the former bug has been fixed.

Given that the release of Firefox 28 was upcoming, Andreea has taken care of all the mozmill-tests related branch merges.

To be prepared for our first Automation Training days, Cosmin updated our Mozmill Crowd extension to ease the first steps for new contributors to our projects. Now the extension is working again for all the latest Firefox releases.

Even with the Firefox Metro projects seeing canceled, we want to finalize our nearly ready Mozmill tests for Firefox Metro and get them landed. That way we can pick up development, if necessary in the future. So Daniel was able to get additional 4 tests finished by this week.

In week 12 Henrik finished the basic implementation work for TPS in being able to switch between Firefox Accounts and the old Sync authentication. Both methods are working now and can be used for testing. As next step we have to investigate and fix all the remaining failing TPS tests.

Individual Updates

For more granular updates of each individual team member please visit our weekly team etherpad for week 11 and week 12.

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 11 and week 12.

Join our first Automation Training days on March 24/26

Building software is fun. Spending countless hours or even days on something to get it finally working. Helping someone who uses your software to speed-up the daily workflow. All that is fantastic and every developer loves that. But don’t let the dark side come up, when customers are pointing you to a lot of software defects. Are you still proud and will you continue the work as how you did it before?

Most likely not. Or well, lets say at least not when quality is what you want to ship. So you will start to think about how to test your application. You can do a lot of manual testing based on test plans or just do exploratory testing. That will work as long as your application is not complex enough, and can be done in a couple of minutes. But once you have to do the same kind of steps over and over again for each release, you will find it boring and loose the interest or concentration on it. Failures will happen so that issues slip through your testing, and bugs becoming part of the new release.

That’s indeed something you eventually want to kill in the future. But how? There is an easy answer to this question! Use test automation! Create tests for each feature you implement, or regression you got fixed. Over time the enlarged suite of tests will make you happy, given that you have to spend nearly no time on manual tests, and have results in a split of the time needed before. Releasing new versions of the application can be done much faster.

At some point, when your application is large enough, you might even not work alone anymore on that product. There will be other developers, or even software testers whose job is to plan and execute the testing strategy. Given that in the past there was not such a high demand on automation knowledge for them, the requirements for jobs have been changed in the past months. So lesser companies will hire engineers for quality assurance who do not have a coding background. This is hard for them, given that it can take ages to find a new position. Something has to change for them.

We, the Firefox Automation team at Mozilla want to help out here. Given our knowledge in automation for various Mozilla related projects, our goal is to support interested people in gaining their knowledge in software development and especially test automation. Therefor we are planning to have automation trainings on a regular basis. And all based on our own projects, so you will have the chance to practice all the new things, which you have learned. All that indeed depends on the acceptance for that offer, and the number of participants.

The first two training days will happen on March 24th and 26th, and will mainly take place in our #automation channel on IRC. Given that we have no idea how many of you will join us during that day, and what your knowledge is, we will start with the basics. That means we will guide you through courses of Javascript, Python, HTML, or CSS. We will collect your feedback and extend the etherpad for automation trainings to finally have a wonderful list of getting started tutorials.

For those of you who already have more experience, we will offer tasks to work on depending on your skills and directions. Please see the before mentioned etherpad for areas of work and appropriate mentors. We will guarantee that it will be fun!

We would love to see you next week, and if you have questions, don’t hesitate to ask here, or in the automation mailing list.