Weeks of Contribution 2016 - QA - Firefox Nightly

June 21, 2016

What is Quality Assurance ?

Quality assurance is an important part in the lifecycle of any software. This area include the following processes - Bug testing, bug filling, and bug triaging. The Mozilla QA team drives software quality assurance activities across Mozilla and plays a key role in releasing a diverse range of software products on schedule.

How will it help Mozilla Community?

With millions of users to their products, the Mozilla community must ensure that the end users should not face any problems while using their products. Through the continuous process of QA, in which volunteers from all over the world participate, the products will be made bugless.

Contribution Areas:

  • Using nightly and aurora builds - These are the unstable versions of firefox for android and Desktop. These versions generally have bugs. Using them will lead to discovering of bugs in them.

  • Filling Bugs in Bugzilla - Bugzilla is a tool used by Mozilla to track bugs. The contributors must follow certain rules while filling a bug.

  • Bug Confirmation and Triaging - Repeating the filled bugs to confirm its existence and Classifying the filled bugs into components.

What the contributors going to Learn?

As We will be working with bugs of firefox nightly, The contributors will be learning about:

  • Bugzilla (http://bugzilla.mozilla.org/)
  • You will understand the lifcycle of a bug (a program bug :-P)
  • Satisfaction in making an impact on millions of users through your contribution.

Our Target?

  • To file atleast one unique bug per contributor
  • To confirm/triage maximum number of bugs possible.

Prerequisite?

Bugzilla Account- to access bugs.

How it will help when they want to be in professional way ?

The Software testing is a major field in IT industry. This may be an intial step for becoming a successful Quality Assurance Engineer.

Training Date

For Trainers : 4 August 2016

For New Contributors : Trainers can work with their team by teaching them the tools discussed, and the projects that has been assigned to their team between 5 August 2016 to 12 August 2016.

Comments

comments powered by Disqus