“I Am Mozilla Web QA” – meet Madalin Cotetiu
What do you do at Mozilla? Currently I’m part of the Web QA team where I work on the Marketplace and the Add-ons websites as a manual tester. What … Read more
What do you do at Mozilla? Currently I’m part of the Web QA team where I work on the Marketplace and the Add-ons websites as a manual tester. What … Read more
For the final day of our week of team meetings we travelled up to San Francisco. Unfortunately this meant that Rebecca couldn’t attend, but it did mean that Krupa could! … Read more
On the fourth day of our team gathering we revisited the mission statement we started on the first day. Our final mission statement is: Our mission is to provide data, … Read more
The third day of our team sprint started with a visit to the external device lab used for Firefox OS front end functional UI testing. This is something the Web … Read more
In the second day of our team sprint we had more great sessions. We started with our automation project documentation, which we all agreed needs attention and have come up … Read more
This week we’ve gathered the Web QA team in Mountain View, California to discuss and hack together on a number of things that are difficult to make rapid progress on … Read more
What do you do at Mozilla? Officially, I am a QA Engineer with the Web QA department, which means that I spend a lot of time writing and maintaining automated … Read more
We’re pleased to announce that the weekly Web QA team meetings are now being recorded and made available via Air Mozilla. This means that if you’re unable to join us … Read more
What do you do at Mozilla? I do what I love, which is automation. When I started at Mozilla I helped to transform the existing automated checks for several web … Read more
I am delighted to announce that Web QA has migrated to a new continuous integration server instance that is publicly accessible! This means you can see all of our test … Read more
Starting a new year often makes me think about reviewing and reorganising, which is exactly what we’ve recently done with our GitHub teams. Until now we had two teams: one … Read more