From 4b1a9203c547c019fc5398082ae19a3f3d4c3efe Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 14:41:15 -0500 Subject: initial commit --- files/bn/mozilla/qa/index.html | 232 +++++++++++++++++++++ .../bn/mozilla/qa/organizing_a_testday/index.html | 202 ++++++++++++++++++ .../qa/running_web_qa_automated_tests/index.html | 147 +++++++++++++ 3 files changed, 581 insertions(+) create mode 100644 files/bn/mozilla/qa/index.html create mode 100644 files/bn/mozilla/qa/organizing_a_testday/index.html create mode 100644 files/bn/mozilla/qa/running_web_qa_automated_tests/index.html (limited to 'files/bn/mozilla/qa') diff --git a/files/bn/mozilla/qa/index.html b/files/bn/mozilla/qa/index.html new file mode 100644 index 0000000000..5c51e735a3 --- /dev/null +++ b/files/bn/mozilla/qa/index.html @@ -0,0 +1,232 @@ +--- +title: 'QA: মোজিলায় মান নিশ্চিতকরণ' +slug: Mozilla/QA +tags: + - Bugzilla + - NeedsTranslation + - QA + - Testing +translation_of: Mozilla/QA +--- +

মজিলা কোয়ালিটি অ্যাসুরেন্স (QA) টিম মজিলার তৈরি করা সফটওয়্যার এর মান নিশ্চিতকরণ এর কাজ করে থাকে এবং বিভিন্ন ধরনের সফটওয়্যার সময়মত রিলিজের জন্য গুরুত্বপূর্ণ ভূমিকা পালন করে। মজিলার প্রত্যেকটি প্রজেক্টের ভিতরে, আমরা নতুন ফিচার পরীক্ষা করার জন্য কাজ করি, বিভিন্ন প্রকার ত্রুটি খুঁজে বের করি, এবং তা সমাধান করার জন্য রিপোর্ট করি, বিভিন্ন ধরনের টূল বিল্ড করি এবং তা রক্ষণাবেক্ষণ করি, তথ্য সংগ্রহ এবং পর্যালোচনা করি, এবং উন্মুক্ত ওয়েবকে সমর্থনকারী, আন্তর্জাতিক মান সম্পন্ন পন্যের রিলিজে সহায়তা প্রদান করি।

+ +

QA টিমে যোগ দিয়ে ফায়ারফক্স টেস্ট করার এবং প্রত্যেকটি রিলিজ যথেষ্ট মান সম্পন্ন করার জন্য এখানে আপনি সহায়ক নিবন্ধ ও টুলস পাবেন।

+ +

শুরু করা

+ + + +

বাগ/ত্রুটি

+ +
+
+

বাগ রিপোর্ট করা

+ +
+
বাগজিলা
+
সকল মজিলা প্রোজেক্ট বাগ ট্র্যাক করার জন্য বাগজিলা ব্যবহার করে। বাগ রিপোর্ট ও ট্রায়াজ করতে বাগজিলায় একটি নতুন অ্যাকাউন্ট তৈরী করতে হবে।
+
Bug writing guidelines
+
The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.
+
একটি বাগের জীবন চক্র
+
This tutorial will give an overview of what happens in the states that a bug will go through as well as how it will go from one to the next within its total life. It also explains the meaning of flags/keywords used in QA.
+
Filing Crash Bugs
+
This document lists guidelines and tips on how to file bug reports for crashes in a way that helps in debugging and fixing the reported issue.
+
+
+ +
+

Triaging bugs

+ +
+
Confirming unconfirmed bugs
+
Identify useful bug reports and close the rest.
+
Triaging Bugs for Firefox
+
Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproducing bugs.
+
Screening duplicate bugs
+
Help get bugs fixed faster by screening incoming reports for duplicates.
+
General Guidelines
+
What to do and what not to do in Bugzilla.
+
+
+
+ +
+

Test cases

+ +
+
+
+
Test Case Writing Primer
+
How to write proper test cases
+
+
+ +
+
+
MozTrap
+
Mozilla QA's test cases reside in MozTrap, an in-house tool. You will need a Persona ID in order to login and execute test cases. Learn how to work with MozTrap Documentation.
+
+
+
+ +
+

Test automation

+ +
+
+
+
Automated testing at Mozilla
+
Documentation about creating and using automated tests for Mozilla code.
+
Developing tests
+
Ensure that future changes to Mozilla don't break things that currently work correctly.
+
Avoiding intermittent test failures
+
Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.
+
+
+ +
+
+
Robocop
+
Robocop is the automated testing system used for Firefox for Android. Learn its code style guidelines
+
Mozmill
+
Get started with Mozmill
+
+
+
+
+ +
+

Firefox QE

+ +
+
+
+
Triaging Bugs for Firefox
+
Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproduce a bug.
+
+ +
+
Tips and Tricks
+
These tips and tricks will make your life easier when you are testing.
+
+Downloading Nightly or Trunk Builds + +
+
Every 24 hours, a "nightly" build is created that testers all over the world download and test, reporting as they go along on any bugs that hit them. 
+
+
+ +
+
+
Command Line Options
+
Command line options are used to specify various startup options for Firefox.
+
Reporting a Performance Problem
+
This article will guide you in reporting a performance problem using the Gecko Profiler extension.
+
Crash Reporting
+
Firefox ships with an open-source crash reporting system.
+
+
+
+ +
+

Firefox for Android

+ +
+
+
+
Mobile Firefox
+
Firefox for Android is the mobile version of Firefox with a native Android look and feel.
+
Compatibility Testing
+
Help us identify websites that do not work well in Firefox by reporting the specific issues that you find in your investigation.
+
+
+ +
+
+
Logging with the Android Debug Bridge and Logcat
+
This article will provide a walkthrough in downloading and setting up an environment to which one can gain access to and view Android system logs.
+
Enabling the Error Console
+
See the Mozilla Hacks article on Remote Debugging on Firefox for Android for web content. If you need to debug the Firefox browser itself use Android's adb logcat.
+
+
+
+ +
+

Firefox OS

+ +
+
+

Manual testing

+ +
+
Simulator vs Emulator vs Device
+
These are three basic options when it comes to getting a Firefox OS environment in order to work on, or developing for, Firefox OS.
+
Debugging
+
Discover the different tools at your disposal to debug your Firefox OS code.
+
Reporting Bugs
+
This article provides a guide to filing bugs against the Firefox OS project, including Gaia and B2G.
+
+
+ +
+

Platform (Gecko)

+ +
+
Automated Testing
+
Learn various aspects of testing Firefox OS, including running different tests, automation, and result reporting and tracking.
+
Gaia Performance Tests
+
This article provides information about running performance tests on Gaia, as well as how to create new tests.
+
Feature Support Chart
+
There are several different builds of Firefox OS you can download or build for yourself, and there are some differences between the types of features available on each device.
+
+
+
+ +
+

Web QA

+ +
+
+
+
Reducing testcases
+
Improve bug reports by turning broken web pages into simple testcases, which can help developers understand the bug and can also be used for creating automated tests.
+
Managing XFails
+
One of the ongoing tasks of the Web QA department is managing xfails. This document will explain what xfails are, and describe the steps one can take to investigate and update them.
+
+
+ +
+
+
Running Automated Tests
+
So you’re interested in contributing to Mozilla Web QA automation projects but don’t know where to start? This doc will help you get up and running a set of tests locally.
+
+
+
+ +
+

Glossary

+ +
+
+
Smoke Test
+
+
+
+ +

View all documents tagged QA

+ +

View all documents tagged QA:Tools

diff --git a/files/bn/mozilla/qa/organizing_a_testday/index.html b/files/bn/mozilla/qa/organizing_a_testday/index.html new file mode 100644 index 0000000000..d1cbff80a5 --- /dev/null +++ b/files/bn/mozilla/qa/organizing_a_testday/index.html @@ -0,0 +1,202 @@ +--- +title: একটি Testday আয়োজন +slug: Mozilla/QA/Organizing_a_Testday +translation_of: Mozilla/QA/Organizing_a_Testday +--- +

Please remember that the following is only a rough guideline. The more effort you put into preparing your testday, the more likely it is to be successful. Give yourself, and the community, ample time to prepare for the event. Above all else, experiment and have fun with your test day.

+ +

Planning Your Event

+ +
The following should be done no later than one week before your event:
+ +
 
+ +
    +
  1. Once you have a topic in mind, pick a day to schedule your event — check the calendar on QMO for availaility
    2. +
  2. Create a test plan to define success criteria, declare a designated spot for signups for mentors, set a schedule (e.g, past event test-plan)
    3. +
  3. Publicize and post the event on QMO (if need be, ask QA staff in IRC for assistance) — a valuable post must contain a request for mentorship sign-up and links to available documentation (e.g, see past event notice)
    4. +
  4. Broadcast your event — Follow our suggested communication list below to help broadcast and publicize the event
    5. +
  5. Enlist mentors to help facilitate and educate throughout the event — gather contact information to ensure that they're able to attend  during the event
    6. +
+ +

The Day Of

+ +
    +
  1. Make sure the IRC channel topic is updated to point people to your test plan
    2. +
  2. Be proactive in greeting people and removing barriers for them to contribute - ask questions and engage with people who join the channel
    3. +
  3. Recommend sign-up to dev-quality and mozillians to attendees for future event notice
    4. +
  4. Provide a feedback survey to participants, clone or copy this example document
    5. +
+ +

After the Event

+ +
    +
  1. Provide a followup post in your communication channels thanking those who attended
    2. +
  2. Plan a future event
    3. +
+ +

Tips for Success

+ +
The following is a list of tips which will hopefully make your event more successful.
+ +
 
+ + + +

Communication Channels

+ +

The following is a list of the various communication channels we should use to advertise. Choose as many or as few as you see fit.

+ +
Mailing Lists
+ + + +
Social Networks
+ + + +
Forums
+ + + +
Meeting Pages
+ + + +
Other Websites
+ + + +
+

Moderators

+ +

The following are some tips for moderators to make the testday a success.

+ + + +

Contributors

+ +

The following are some tips for contributors to make the testday a success.

+ + + +
+

Original document information

+ + +
+ +
+

QMO Event Page

+ +

The week before a testday we need to create a QMO event page.

+ + + +

This is an example of an excellent QMO Event page. Before posting make sure you:

+ + + +

QMO Blog Post

+ +

The day before the testday, simply create a post which reminds people that a testday is happening tomorrow.

+ + + +

This is a good example of a QMO Event Reminder. Your post should be syndicated to Planet within 30 minutes to an hour.

+ +

QMO Results Post

+ +

The day after a testday, create another post which highlights the results.

+ + + +

This is a good example of a QMO Results Post. Your post should be syndicated to Planet within 30 minutes to an hour.  

+ +
+

Original document information

+ + +
+ +

 

diff --git a/files/bn/mozilla/qa/running_web_qa_automated_tests/index.html b/files/bn/mozilla/qa/running_web_qa_automated_tests/index.html new file mode 100644 index 0000000000..41d0223852 --- /dev/null +++ b/files/bn/mozilla/qa/running_web_qa_automated_tests/index.html @@ -0,0 +1,147 @@ +--- +title: Web QA স্বয়ংক্রিয় পরীক্ষা চালানো +slug: Mozilla/QA/Running_Web_QA_automated_tests +translation_of: Mozilla/QA/Running_Web_QA_automated_tests +--- +
+

আপনি  Web QA পরীক্ষা চালাতে চান , কিন্তু জানেন না কোথা থেকে শুরু করতে হবে ? This doc will help you get up and running a set of tests locally.

+ +

We have a separate project for each web site that we test, so the first step is to choose a project. You can look at the list of our automation projects, or you could simply use the Addon-Tests project to start. Once you’ve decided which project you’d like to work on, follow this guide to run the existing tests.

+ +

You should join us on IRC at http://irc.mozilla.org, #mozwebqa and #qa. You can say hello there, and get help if you get stuck on these instructions.

+ +

All of our projects use Selenium/WebDriver and a fairly similar set of software requirements. However some projects may have specific requirements. If the any of these steps does not work as expected you may want to check out the README file in the project’s root to see if there’s anything special needed.

+ +

All of the following commands are performed from a terminal window (Linux/Mac) or shell (Windows).

+ +

Step 1: Install required software

+ +

In order to run and work on our tests you need both Git and Python installed. You will also needpip, which is a package manager for Python.

+ +

Excellent instructions for installing Git on all platforms can be found at Github.

+ +

Python can be downloaded from here. Select the appropriate version for your platform and run the installer, we recommend the highest version 2 package that is available.

+ +

You can verify that Python has been successfully installed by running the following command:

+ +
python --version
+ +

Windows only:
+ After installing Python, install SetupTools from here. Once that is done you’ll need to add the Python folder (e.g., C:\Python26) and the Python scripts folder (e.g., C:\Python26\Scripts) into your path via System Variables: System Properties->Environment Variables->System Variables-> Path.

+ +

Linux only:
+ If you are running on Ubuntu/Debian, after installing Python, install SetupTools via

+ +
sudo apt-get install python-setuptools
+ +

After Python is successfully installed, install pip by running the following command:

+ +
easy_install pip
+ +

You now have all of the software required to run Web QA tests!

+ +

Step 2: Clone the project

+ +

If you want to make any changes to tests, or add your own tests, you’ll need to fork the repository (repo) first, to obtain your own copy. To do this simply visit the repo page for one of the automation projects, and click the fork button which you’ll find near the upper right-hand corner of the page:
+ Screen Shot 2013-10-18 at 11.26.33 AM

+ +

You can then clone the repo (which means to create a working copy of all the code locally) to your machine. Switch to the folder on your machine in which you’d like to store the project, and issue the following command:

+ +
git clone --recursive git@github.com:[your username]/[project].git
+ +

For example:

+ +
git clone --recursive git@github.com:bobsilverberg/Addon-Tests.git
+ +

Pro tip: You can find the url to use to clone the project via the project’s Github page. Look for this area on the right-hand side of the page, and click on the little clipboard icon to copy the url to your clipboard:
+ Screen Shot 2013-10-18 at 11.29.15 AM If you don’t already have an SSH key set up to work with github, try clicking “https”, then copy the url for the repo to use in your git clone command.

+ +

Step 3: Install required Python packages

+ +

Each project has its own requirements.txt which lists Python packages needed for running the tests.
+ Install them using:

+ +
pip install -Ur requirements.txt
+ +

[Optional/Intermediate level]
+ While most of us have had some experience using virtual machines, virtualenv is something else entirely. It’s used to keep libraries that you install from clashing and messing up your local environment. After installing virtualenv, installing virtualenvwrapper will give you some nice commands to use with virtualenv.

+ +

For a more detailed discussion of virtualenv and virtualenvwrapper, check out our quickstart guide and also this blog post.

+ +

Step 4: Create a credentials file

+ +

Most of our projects include tests that need to log in to the web site. In order to do this we store the credentials for the site in a file called credentials.yaml. You can find a sample credentials.yaml file in the root of the project. In order to run tests that need to log in, you will need to update this file with some valid credentials. First you’ll need a username and password for the site in question, which you can generally obtain by registering for the site, then you can add that information to the credentials file on your machine.

+ +

If you do not see a sample credentials.yaml file in the root of the project then you can skip this step!

+ +

Pro tip: If you do not want Git to think that your credentials.yaml file has changed from the one in the project repo, create a new copy of the file in a different location and then point to it from the command line. For example, you can create a file in your home folder called “amo_credentials.yaml” and then point to that.

+ +

Step 5: Choose an execution environment

+ +

Most of the web sites we test have multiple environments, so before running the tests you need to choose where you want them to run. In general, a project will have one or more of the following environments available:

+ + + +

Pro tip: There is a file in the root of each project, called “mozwebqa.cfg” that contains some defaults for running the tests. It usually specifies a default environment for the tests using the “baseurl” setting. For example, mozwebqa.cfg in the addon-tests project contains the line:

+ +
baseurl = https://addons-dev.allizom.org
+ +

Step 6: Run the tests!

+ +

Once you have all the above in place, you are ready to start running some tests locally. Let’s give it a try: open a console and make sure you’re in the project’s directory.

+ +

To run all the tests:

+ +
py.test --driver=firefox
+ +

To run all the tests with a credentials file:

+ +
py.test --driver=firefox --credentials=/path/to/credentials.yaml
+ +

To run all of the tests in one file:

+ +
py.test --driver=firefox tests/test_file.py
+ +

To run one test in a file:

+ +
py.test --driver=firefox tests/test_file.py -k name_of_test_to_run
+ +

To run tests on an environment other than the default, specify the “–baseurl” option:

+ +
py.test --driver=firefox --baseurl=https://addons.allizom.org
+ +

If you are running tests on the development or staging environments and was to run tests that change data (hint: you ususally do), you will need to also specify the “–destructive” command line option. For example:

+ +
py.test --driver=firefox --baseurl=https://addons.allizom.org --destructive
+ +

The pytest-mozwebqa plugin has advanced command line options for reporting and using browsers. To see the options available, try running:

+ +
py.test --help
+ +

Also see the documentation on the plugin’s project page.

+ +

[Optional/Intermediate level]
+ A Selenium Grid can be used to run and Webdriver tests across many different browsers. The Web QA team also has a project which holds a Selenium Grid configuration for Windows and Mac OS.

+ +

Follow our quick start guide to get Selenium Grid up and running.

+ +

Now you’re ready to contribute!

+ +

If you’d like to learn more, the next post in this series is on Automated Tests: Analyzing Results.

+ +

Step 7: Get the Badge!

+ +

Once you have completed the steps above, you are eligible for the new Web QA badge! You can see the badge here:

+ +

https://badges.mozilla.org/en-US/badges/badge/Running–Web-QA-Automation

+ +

Log in using Persona to nominate yourself, or someone else who has Web QA tests up and running. Make sure to include your GitHub username or email in your profile. Congratulations!

+ +
 
+
+ +

 

-- cgit v1.2.3-54-g00ecf