diff options
Diffstat (limited to 'files/bn/mozilla/qa')
| -rw-r--r-- | files/bn/mozilla/qa/index.html | 232 | ||||
| -rw-r--r-- | files/bn/mozilla/qa/organizing_a_testday/index.html | 202 | ||||
| -rw-r--r-- | files/bn/mozilla/qa/running_web_qa_automated_tests/index.html | 147 |
3 files changed, 581 insertions, 0 deletions
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 +--- +<p>মজিলা কোয়ালিটি অ্যাসুরেন্স (QA) টিম মজিলার তৈরি করা সফটওয়্যার এর মান নিশ্চিতকরণ এর কাজ করে থাকে এবং বিভিন্ন ধরনের সফটওয়্যার সময়মত রিলিজের জন্য গুরুত্বপূর্ণ ভূমিকা পালন করে। মজিলার প্রত্যেকটি প্রজেক্টের ভিতরে, আমরা নতুন ফিচার পরীক্ষা করার জন্য কাজ করি, বিভিন্ন প্রকার ত্রুটি খুঁজে বের করি, এবং তা সমাধান করার জন্য রিপোর্ট করি, বিভিন্ন ধরনের টূল বিল্ড করি এবং তা রক্ষণাবেক্ষণ করি, তথ্য সংগ্রহ এবং পর্যালোচনা করি, এবং উন্মুক্ত ওয়েবকে সমর্থনকারী, আন্তর্জাতিক মান সম্পন্ন পন্যের রিলিজে সহায়তা প্রদান করি।</p> + +<p><span class="seoSummary">QA টিমে যোগ দিয়ে ফায়ারফক্স টেস্ট করার এবং প্রত্যেকটি রিলিজ যথেষ্ট মান সম্পন্ন করার জন্য এখানে আপনি সহায়ক নিবন্ধ ও টুলস পাবেন।</span></p> + +<h2 id="শুরু_করা">শুরু করা</h2> + +<ul class="card-grid"> + <li><span>আমি কিভাবে টেস্ট করতে সাহায্য করতে পারি?</span> + + <p>মজিলা কোয়ালিটি টিমের একজন <a href="/en-US/docs/Mozilla/QA/How_can_I_help_test_">কমিউনিটি কন্ট্রিবিউটর</a> হওয়ার জন্য অনেক উপায় রয়েছে।</p> + </li> + <li><span>বাগ/ত্রুটি</span> + <p>সকল মজিলা প্রোজেক্ট বাগ ট্র্যাক করার জন্য <a href="https://bugzilla.mozilla.org/">বাগজিলা</a> ব্যবহার করে। কিভাবে <a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">একটি বাগ রিপোর্ট</a> করতে হয় শিখুন এবং <a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">বাগজিলায় কি করতে পারেন</a> তা জানুন।</p> + </li> + <li><span>ইভেন্ট</span> + <p>আমাদের সাপ্তাহিক <a href="/en-US/docs/Mozilla/QA/Bug_Verification_Day">বাগ ভেরিফিকেশন ডে</a> অথবা <a href="/en-US/docs/Mozilla/QA/Bug_Triage_Day">বাগ ট্রায়াজ ডে</a> তে অংশগ্রহন করুন। এমনকি আপনি আপনার লোকাল কমিউনিটির জন্য <a href="/en-US/docs/Mozilla/QA/Organizing_a_Testday">একটি টেস্ট ডে আয়োজন</a> করতে পারেন!</p> + </li> + <li><span>আইআরসি (IRC)</span> + <p><a href="/en-US/docs/Mozilla/QA/Getting_Started_with_IRC">IRC এর সাথে পরিচিত হন</a>, এটি মজিলা কমিউনিটির সাথে যোগাযোগের প্রধান মাধ্যম।</p> + </li> +</ul> + +<h2 id="বাগত্রুটি">বাগ/ত্রুটি</h2> + +<div class="row topicpage-table"> +<div class="section"> +<h3 id="বাগ_রিপোর্ট_করা">বাগ রিপোর্ট করা</h3> + +<dl> + <dt><a href="/en-US/docs/Mozilla/Bugzilla">বাগজিলা</a></dt> + <dd><span style="background-color: rgba(234, 239, 242, 0.498039);">সকল মজিলা প্রোজেক্ট বাগ ট্র্যাক করার জন্য </span><a href="https://bugzilla.mozilla.org/" style="background-color: rgba(234, 239, 242, 0.498039);">বাগজিলা</a><span style="background-color: rgba(234, 239, 242, 0.498039);"> ব্যবহার করে।</span> বাগ রিপোর্ট ও ট্রায়াজ করতে <a href="https://bugzilla.mozilla.org/createaccount.cgi">বাগজিলায় একটি নতুন অ্যাকাউন্ট</a> তৈরী করতে হবে।</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">Bug writing guidelines</a></dt> + <dd>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.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/A_Bugs_Life" title="/en-US/docs/Mozilla/QA/A_Bugs_Life">একটি বাগের জীবন চক্র</a></dt> + <dd>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.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Filing_Crash_Bugs">Filing Crash Bugs</a></dt> + <dd>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.</dd> +</dl> +</div> + +<div class="section"> +<h3 id="Triaging_bugs">Triaging bugs</h3> + +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Confirming_unconfirmed_bugs" title="en-US/docs/Confirming unconfirmed bugs">Confirming unconfirmed bugs</a></dt> + <dd>Identify useful bug reports and close the rest.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt> + <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproducing bugs.</dd> + <dt><a href="/en-US/docs/Screening_duplicate_bugs">Screening duplicate bugs</a></dt> + <dd>Help get bugs fixed faster by screening incoming reports for duplicates.</dd> + <dt><a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">General Guidelines</a></dt> + <dd>What to do and what not to do in Bugzilla.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Test_cases">Test cases</h2> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Test_Case_Writing_Primer">Test Case Writing Primer</a></dt> + <dd>How to write proper test cases</dd> +</dl> +</div> + +<div class="section"> +<dl> + <dt><a href="https://moztrap.mozilla.org/">MozTrap</a></dt> + <dd>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 <a href="https://moztrap.readthedocs.org">MozTrap Documentation</a>.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Test_automation">Test automation</h2> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Automated_testing" title="/en-US/docs/Mozilla/QA/Automated_testing">Automated testing at Mozilla</a></dt> + <dd>Documentation about creating and using automated tests for Mozilla code.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Developing_tests" title="en-US/docs/Developing_Tests">Developing tests</a></dt> + <dd>Ensure that future changes to Mozilla don't break things that currently work correctly.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Avoiding_intermittent_oranges" title="en-US/docs/QA/Avoiding intermittent oranges">Avoiding intermittent test failures</a></dt> + <dd>Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.</dd> +</dl> +</div> + +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Robocop" title="/en-US/docs/Mozilla/QA/Robocop">Robocop</a></dt> + <dd>Robocop is the automated testing system used for Firefox for Android. Learn its <a href="/en-US/docs/Mozilla/QA/Robocop/Code_style_guidelines">code style guidelines</a></dd> + <dt><a href="/en-US/docs/Mozilla/QA/Mozmill_tests">Mozmill</a></dt> + <dd>Get started with Mozmill</dd> + <dd></dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Firefox_QE">Firefox QE</h2> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt> + <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproduce a bug.</dd> +</dl> + +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Tips_and_Tricks">Tips and Tricks</a></dt> + <dd>These tips and tricks will make your life easier when you are testing.</dd> +</dl> +<a href="/en-US/docs/Downloading_Nightly_or_Trunk_Builds">Downloading Nightly or Trunk Builds</a> + +<dl> + <dd>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. </dd> +</dl> +</div> + +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/Command_Line_Options">Command Line Options</a></dt> + <dd>Command line options are used to specify various startup options for Firefox.</dd> + <dt><a href="/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem">Reporting a Performance Problem</a></dt> + <dd>This article will guide you in reporting a performance problem using the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler">Gecko Profiler extension</a>.</dd> + <dt><a href="/en-US/docs/Crash_reporting">Crash Reporting</a></dt> + <dd>Firefox ships with an open-source crash reporting system.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Firefox_for_Android">Firefox for Android</h2> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Mobile_Firefox">Mobile Firefox</a></dt> + <dd>Firefox for Android is the mobile version of Firefox with a native Android look and feel.</dd> + <dt><a href="/en-US/Firefox_for_Android/Compatibility_Testing">Compatibility Testing</a></dt> + <dd>Help us identify websites that do not work well in Firefox by reporting the specific issues that you find in your investigation.</dd> +</dl> +</div> + +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Fennec_Android:_Logging_with_the_Android_Debug_and_Logcat">Logging with the Android Debug Bridge and Logcat</a></dt> + <dd>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.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Firefox_Mobile:_Enabling_the_Error_Console">Enabling the Error Console</a></dt> + <dd>See the Mozilla Hacks article on <a class="external external-icon" href="https://hacks.mozilla.org/2012/08/remote-debugging-on-firefox-for-android/">Remote Debugging on Firefox for Android</a> for web content. If you need to debug the Firefox browser itself use Android's <a class="external external-icon" href="http://developer.android.com/tools/help/logcat.html">adb logcat</a>.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Firefox_OS">Firefox OS</h2> + +<div class="row topicpage-table"> +<div class="section"> +<h3 id="Manual_testing">Manual testing</h3> + +<dl> + <dt><a href="/en-US/Firefox_OS/Simulator_vs_Emulator_vs_Device">Simulator vs Emulator vs Device</a></dt> + <dd>These are three basic options when it comes to getting a Firefox OS environment in order to work on, or developing for, Firefox OS.</dd> + <dt><a href="/en-US/Firefox_OS/Debugging">Debugging</a></dt> + <dd>Discover the different tools at your disposal to debug your Firefox OS code.</dd> + <dt><a href="/en-US/Firefox_OS/Developing_Firefox_OS/Filing_bugs_against_Firefox_OS">Reporting Bugs</a></dt> + <dd>This article provides a guide to filing bugs against the Firefox OS project, including Gaia and B2G.</dd> +</dl> +</div> + +<div class="section"> +<h3 id="Platform_(Gecko)">Platform (Gecko)</h3> + +<dl> + <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing">Automated Testing</a></dt> + <dd>Learn various aspects of testing Firefox OS, including running different tests, automation, and result reporting and tracking.</dd> + <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing/Gaia_performance_tests">Gaia Performance Tests</a></dt> + <dd>This article provides information about running performance tests on Gaia, as well as how to create new tests.</dd> + <dt><a href="/en-US/Firefox_OS/Platform/Feature_support_chart">Feature Support Chart</a></dt> + <dd>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.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Web_QA">Web QA</h2> + +<div class="row topicpage-table"> +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Reducing_testcases" title="en-US/docs/Reducing testcases">Reducing testcases</a></dt> + <dd>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.</dd> + <dt><a href="/en-US/docs/Mozilla/QA/Managing_Web_QA_XFails">Managing XFails</a></dt> + <dd>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.</dd> +</dl> +</div> + +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Mozilla/QA/Running_Web_QA_automated_tests">Running Automated Tests</a></dt> + <dd>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.</dd> +</dl> +</div> +</div> + +<hr> +<h2 id="Glossary">Glossary</h2> + +<div class="section"> +<dl> + <dt><a href="/en-US/docs/Glossary/Smoke_Test">Smoke Test</a></dt> + <dd></dd> +</dl> +</div> + +<p><span class="alllinks"><a href="/en-US/docs/tag/QA" title="en-US/docs/tag/QA">View all documents tagged QA</a></span></p> + +<p><span class="alllinks"><a href="/en-US/docs/tag/QA:Tools" title="en-US/docs/tag/QA:Tools">View all documents tagged QA:Tools</a></span></p> 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 +--- +<p>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.</p> + +<h4 id="Planning_Your_Event">Planning Your Event</h4> + +<div>The following should be done no later than one week before your event:</div> + +<div> </div> + +<ol> + <li>Once you have a topic in mind, pick a day to schedule your event — check the <a href="https://quality.mozilla.org/events/">calendar on QMO</a> for availaility</li> + <li>Create a test plan to define success criteria, declare a designated spot for signups for mentors, set a schedule (e.g, <a href="https://etherpad.mozilla.org/testday-20141024">past event test-plan</a>)</li> + <li>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, <a href="https://quality.mozilla.org/2014/09/volunteers-needed-for-testdays-relaunch-initiative/">see past event notice</a>)</li> + <li>Broadcast your event — Follow our suggested communication list below to help broadcast and publicize the event</li> + <li>Enlist mentors to help facilitate and educate throughout the event — gather contact information to ensure that they're able to attend during the event</li> +</ol> + +<h4 id="The_Day_Of">The Day Of</h4> + +<ol> + <li>Make sure the IRC channel topic is updated to point people to your test plan</li> + <li>Be proactive in greeting people and removing barriers for them to contribute - ask questions and engage with people who join the channel</li> + <li>Recommend sign-up to dev-quality and mozillians to attendees for future event notice</li> + <li>Provide a feedback survey to participants, <a href="https://docs.google.com/forms/d/1ZPa-0g_jqfRQdhBLOJFLms9VudvjLjVGKOHeHpJNLyk/viewform">clone or copy this example document</a></li> +</ol> + +<h4 id="After_the_Event">After the Event</h4> + +<ol> + <li>Provide a followup post in your communication channels thanking those who attended</li> + <li>Plan a future event</li> +</ol> + +<h4 id="Tips_for_Success">Tips for Success</h4> + +<div>The following is a list of tips which will hopefully make your event more successful.</div> + +<div> </div> + +<ul> + <li>Make sure you have enough mentors committed to your event, otherwise it might come off as disorganized</li> + <li>Make sure your project is ready for testers; remember that most testers are just Firefox users</li> + <li>The more you advertise the greater your audience</li> + <li>Give yourself enough time to prepare the material</li> + <li>Give your audience enough time to familiarize themselves with any material needed as a prerequisite before the event</li> + <li>Have a peer review your event material and attempt an activity to test the ease of your ramp-up path</li> + <li>Don’t be afraid to reach out to external communities (especially true for development related testdays)</li> +</ul> + +<h4 id="Communication_Channels">Communication Channels</h4> + +<p>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.</p> + +<h5 id="Mailing_Lists">Mailing Lists</h5> + +<ul> + <li>dev-quality: the primary public mailing for Mozilla QA</li> + <li>events: use if your event incorporates physical meetup</li> +</ul> + +<h5 id="Social_Networks">Social Networks</h5> + +<ul> + <li>Twitter: @MozillaQA is our Twitter account</li> + <li>Facebook: MozillaQA is our Facebook account. Note that QMO Event posts are automatically syndincated to Facebook</li> + <li>Yammer</li> + <li>Google Plus</li> +</ul> + +<h5 id="Forums">Forums</h5> + +<ul> + <li>Reddit: <a href="http://reddit.com/r/firefox">http://reddit.com/r/firefox</a> — active Firefox community</li> + <li>Discourse: <a href="/en-US/docs/">https://discourse.mozilla-community.org/c/quality-assurance</a></li> +</ul> + +<h5 id="Meeting_Pages">Meeting Pages</h5> + +<ul> + <li>Mozilla Project Weekly Update, <a href="https://wiki.mozilla.org/WeeklyUpdates">meeting details here</a></li> + <li>QA Team: public QA meeting, <a href="https://wiki.mozilla.org/QA/Team_Meeting">meeting details here</a></li> +</ul> + +<h5 id="Other_Websites">Other Websites</h5> + +<ul> + <li><a href="http://forum.xda-developers.com/">XDA Forums</a></li> + <li><a href="http://www.softwaretestingclub.com/">Software Testing Club</a></li> +</ul> + +<hr> +<h2 id="Moderators">Moderators</h2> + +<p>The following are some tips for moderators to make the testday a success.</p> + +<ul> + <li>Greet people as soon as they join the channel</li> + <li>Ask them to sign up for Mozillians.org</li> + <li>Ask them to download the test build</li> + <li>Ask them about their interest and give them a specific task to perform</li> + <li>Offer to answer questions</li> + <li>Touch base with your testers if you haven't heard from them in the last 20 minutes or so</li> + <li>Thank and encourage your testers when they are completing tasks</li> + <li>Thank and encourage your testers before when they indicate they are leaving</li> + <li>Tell people in other channels about your testday (#qa, #firefox, etc)</li> +</ul> + +<h2 id="Contributors">Contributors</h2> + +<p>The following are some tips for contributors to make the testday a success.</p> + +<ul> + <li>Ask questions, any and all questions you have are valid</li> + <li>Don't be afraid to stumble, hopefully you will learn something new</li> + <li>Read over the testplan and provided documentation</li> + <li>Get a build and start testing; just dive right in</li> + <li>Offer to help other testers and answer questions once you've learned the ropes</li> + <li>Sign up for <a href="https://mozillians.org">Mozillians.org</a> so we can keep in touch</li> + <li><strong>Missed the testday?</strong> Reach out to the organizer and see how you can help out after the fact</li> +</ul> + +<div class="originaldocinfo"> +<h2 id="Original_document_information">Original document information</h2> + +<ul> + <li>Author(s): Anthony Hughes</li> + <li>Date last modified: February 3, 2012 at 10:54 pm PST</li> +</ul> +</div> + +<hr> +<h3 id="QMO_Event_Page"><a name="event"></a>QMO Event Page</h3> + +<p>The week before a testday we need to create a QMO event page.</p> + +<ul> + <li>Once you are logged in (yes you need to be authenticated) simply click on the left to add a <a href="https://quality.mozilla.org/wp-admin/post-new.php">new post</a></li> + <li>Your title should indicate the topic and date (ie. Firefox Aurora Bugday May 6th)</li> + <li>Start out by giving a small summary of the topic, goals, and when the event takes place.</li> + <li>Give some context as to why this event/activity is necessary and valuable.</li> + <li>Give some encouragement for people who have absolutely no experience to attend.</li> + <li>Frame the language of your post with "making Firefox better", show them what benefit their contributions provide (no matter how big or small).</li> + <li>Provide a link to your testplan etherpad and a mibbit URL so people without IRC clients can join easily.</li> + <li>Be sure to thank them in advance for attending.</li> +</ul> + +<p>This is an example of an excellent <a href="http://quality.mozilla.org/events/2011/02/28/add-ons-compatibility-and-add-ons-manager-testday-march-4th/">QMO Event</a> page. <strong>Before posting make sure you:</strong></p> + +<ul> + <li>"Is this post an event?" is set to "Yes" below</li> + <li>"All day event?" is unchecked and the date/times are properly set (all times in PDT)</li> + <li>All other event details can be left blank</li> + <li>On the right under "Categories", check "Events", "QMO News" and any appropriate "Teams"</li> + <li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong> (if you have to, get someone else to review)</li> +</ul> + +<h3 id="QMO_Blog_Post"><a name="blog"></a>QMO Blog Post</h3> + +<p>The day before the testday, simply create a post which reminds people that a testday is happening <em>tomorrow</em>.</p> + +<ul> + <li>The title should be similar to "REMINDER: Firefox Aurora Testday Tomorrow!"</li> + <li>The message should summarize the activity, time, a mibbit URL to the channel, and a link to the QMO Event page for more information</li> + <li>Be sure to thank them ahead of time for attending</li> + <li>Be sure the "Categories" on the right are set to "QMO News"</li> + <li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong></li> +</ul> + +<p>This is a good example of a <a href="http://quality.mozilla.org/qmo-news/2011/03/24/testday-reminder-mozmill-crowd-and-endurance-testing/">QMO Event Reminder</a>. Your post should be syndicated to Planet within 30 minutes to an hour.</p> + +<h3 id="QMO_Results_Post"><a name="results"></a>QMO Results Post</h3> + +<p>The day after a testday, create another post which highlights the results.</p> + +<ul> + <li>The title should be similar to "Results of the Firefox Aurora Testday"</li> + <li>The message should summarize the activity and the value it provided</li> + <li>Highlight some of the results (number of bugs filed, number of bugs confirmed/verified, number of testers, etc)</li> + <li>Identify and thank the top tester</li> + <li>Identify and thank some of the people who were runners up for the top-tester</li> + <li>Give general thanks to everyone who helped</li> + <li>Provide a link to the next testday (should it be available) and ask people to come back to help</li> + <li>Be sure the "Categories" on the right are set to "QMO News"<strong> </strong></li> + <li><strong>Make sure you SAVE DRAFT and PREVIEW before publishing</strong></li> +</ul> + +<p>This is a good example of a <a href="http://quality.mozilla.org/qmo-news/2011/04/26/results-of-the-aurora-422-testday/">QMO Results Post</a>. Your post should be syndicated to Planet within 30 minutes to an hour. </p> + +<div class="originaldocinfo"> +<h2 id="Original_document_information_2">Original document information</h2> + +<ul> + <li>Author(s): Anthony Hughes</li> + <li>Date last modified: October 25, 2011 at 11:16 am PST</li> +</ul> +</div> + +<p> </p> 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 +--- +<div class="entry-content" style="word-wrap: break-word; margin-bottom: 1em; font-family: Georgia, Times, serif; font-size: 12.7272720336914px; line-height: 18.176362991333px;"> +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">আপনি <a href="https://wiki.mozilla.org/QA/Execution/Web_Testing" style="color: rgb(227, 114, 14); font-weight: bold;">Web QA</a> পরীক্ষা চালাতে চান , কিন্তু জানেন না কোথা থেকে শুরু করতে হবে ? This doc will help you get up and running a set of tests locally.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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 <a href="https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation#Web_QA_Projects" style="color: rgb(227, 114, 14); font-weight: bold;">automation projects</a>, or you could simply use the <a href="https://github.com/mozilla/Addon-Tests" style="color: rgb(227, 114, 14); font-weight: bold;">Addon-Tests</a> project to start. Once you’ve decided which project you’d like to work on, follow this guide to run the existing tests.</p> + +<p style="margin-bottom: 1.4em;"><font color="#333333">You should join us on IRC</font><font color="#333333"> at <a href="/en-US/docs/">http://irc.mozilla.org</a>, #mozwebqa and #qa. You can say hello there, and get help if you get stuck on these instructions.</font></p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">All of the following commands are performed from a terminal window (Linux/Mac) or shell (Windows).</p> + +<h2 id="Step_1_Install_required_software" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 1: Install required software</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">In order to run and work on our tests you need both <strong>Git</strong> and <strong>Python</strong> installed. You will also need<strong>pip</strong>, which is a package manager for Python.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Excellent instructions for installing Git on all platforms can be found at <a href="https://help.github.com/articles/set-up-git" style="color: rgb(227, 114, 14); font-weight: bold;">Github</a>.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Python can be downloaded from <a href="https://www.python.org/downloads/" style="color: rgb(227, 114, 14); font-weight: bold;">here</a>. Select the appropriate version for your platform and run the installer, we recommend the highest version 2 package that is available.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">You can verify that Python has been successfully installed by running the following command:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">python --version</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><strong>Windows only:</strong><br> + After installing Python, install SetupTools from <a href="http://pypi.python.org/pypi/setuptools" style="color: rgb(227, 114, 14); font-weight: bold;">here</a>. 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: <em>System Properties->Environment Variables->System Variables-> Path</em>.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><strong>Linux only:</strong><br> + If you are running on Ubuntu/Debian, after installing Python, install SetupTools via</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">sudo apt-get install python-setuptools</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">After Python is successfully installed, install pip by running the following command:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">easy_install pip</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">You now have all of the software required to run Web QA tests!</p> + +<h2 id="Step_2_Clone_the_project" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 2: Clone the project</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">If you want to make any changes to tests, or add your own tests, you’ll need to <em>fork</em> the repository (repo) first, to obtain your own copy. To do this simply visit the repo page for <a href="https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation#Web_QA_Projects" style="color: rgb(227, 114, 14); font-weight: bold;">one of the automation projects</a>, and click the fork button which you’ll find near the upper right-hand corner of the page:<br> + <img alt="Screen Shot 2013-10-18 at 11.26.33 AM" class="alignnone size-full wp-image-46129" src="https://quality.mozilla.org/qmo_content/uploads/Screen-Shot-2013-10-18-at-11.26.33-AM.png" style="height: 40px; width: 113px;"></p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">You can then <em>clone</em> 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:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">git clone --recursive git@github.com:[your username]/[project].git</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">For example:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">git clone --recursive git@github.com:bobsilverberg/Addon-Tests.git</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><em>Pro tip</em>: 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:<br> + <img alt="Screen Shot 2013-10-18 at 11.29.15 AM" class="alignnone size-full wp-image-46130" src="https://quality.mozilla.org/qmo_content/uploads/Screen-Shot-2013-10-18-at-11.29.15-AM.png" style="height: 112px; width: 209px;"> 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.</p> + +<h2 id="Step_3_Install_required_Python_packages" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 3: Install required Python packages</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Each project has its own requirements.txt which lists Python packages needed for running the tests.<br> + Install them using:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">pip install -Ur requirements.txt</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><strong>[Optional/Intermediate level]</strong><br> + While most of us have had some experience using virtual machines, <a href="http://pypi.python.org/pypi/virtualenv" style="color: rgb(227, 114, 14); font-weight: bold;">virtualenv</a> 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 <a href="http://www.doughellmann.com/projects/virtualenvwrapper/" style="color: rgb(227, 114, 14); font-weight: bold;">virtualenvwrapper</a> will give you some nice commands to use with virtualenv.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">For a more detailed discussion of virtualenv and virtualenvwrapper, check out <a href="https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Virtual_Environments" style="color: rgb(227, 114, 14); font-weight: bold;">our quickstart guide</a> and also <a href="http://www.silverwareconsulting.com/index.cfm/2012/7/24/Getting-Started-with-virtualenv-and-virtualenvwrapper-in-Python" style="color: rgb(227, 114, 14); font-weight: bold;">this blog post</a>.</p> + +<h2 id="Step_4_Create_a_credentials_file" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 4: Create a credentials file</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">If you do not see a sample credentials.yaml file in the root of the project then you can skip this step!</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><em>Pro tip</em>: 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.</p> + +<h2 id="Step_5_Choose_an_execution_environment" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 5: Choose an execution environment</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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:</p> + +<ul style="color: rgb(51, 51, 51); margin-bottom: 1.4em; margin-left: 1.6em; padding-left: 0px;"> + <li style="margin-bottom: 0.25em; padding-bottom: 0px;">Production – this is the “live” environment, the site which is actually visited by the site’s users. The url generally contains “mozilla.org” in it. For example, for addons it would be<a href="https://addons.mozilla.org/" style="color: rgb(227, 114, 14); font-weight: bold;">https://addons.mozilla.org</a>.</li> + <li style="margin-bottom: 0.25em; padding-bottom: 0px;">Staging – this is an environment where code lives after it has graduated from development but before going to production. The url generally contains “allizom.org” in it. For example, for addons it would be <a href="https://addons.allizom.org/" style="color: rgb(227, 114, 14); font-weight: bold;">https://addons.allizom.org</a>.</li> + <li style="margin-bottom: 0.25em; padding-bottom: 0px;">Development – this is the environment that developers use to test their code. The url generally contains “dev-” in it. For example, for addons it would be <a href="https://addons.allizom.org/" style="color: rgb(227, 114, 14); font-weight: bold;">https://dev-addons.allizom.org</a>.</li> +</ul> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><em>Pro tip</em>: 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:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">baseurl = https://addons-dev.allizom.org</pre> + +<h2 id="Step_6_Run_the_tests!" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 6: Run the tests!</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">To run all the tests:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">To run all the tests with a credentials file:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox --credentials=/path/to/credentials.yaml</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">To run all of the tests in one file:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox tests/test_file.py</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">To run one test in a file:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox tests/test_file.py -k name_of_test_to_run</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">To run tests on an environment other than the default, specify the “–baseurl” option:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox --baseurl=https://addons.allizom.org</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --driver=firefox --baseurl=https://addons.allizom.org --destructive</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">The pytest-mozwebqa plugin has advanced command line options for reporting and using browsers. To see the options available, try running:</p> + +<pre style="color: rgb(51, 51, 51); margin-bottom: 1.4em; padding: 0px;">py.test --help</pre> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Also see the documentation on <a href="https://github.com/davehunt/pytest-mozwebqa" style="color: rgb(227, 114, 14); font-weight: bold;">the plugin’s project page</a>.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><strong>[Optional/Intermediate level]</strong><br> + 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.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Follow our <a href="https://github.com/mozilla/moz-grid-config/wiki/Quick-Start" style="color: rgb(227, 114, 14); font-weight: bold;">quick start guide</a> to get Selenium Grid up and running.</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Now you’re ready to contribute!</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">If you’d like to learn more, the next post in this series is on <a href="https://quality.mozilla.org/2014/03/automated-testing-analyzing-results/" style="color: rgb(227, 114, 14); font-weight: bold;">Automated Tests: Analyzing Results.</a></p> + +<h2 id="Step_7_Get_the_Badge!" style="color: rgb(42, 126, 0); margin-bottom: 0.5em; font-weight: normal; line-height: 1.2; font-size: 1.69em;">Step 7: Get the Badge!</h2> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">Once you have completed the steps above, you are eligible for the new Web QA badge! You can see the badge here:</p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;"><a href="https://badges.mozilla.org/en-US/badges/badge/Running--Web-QA-Automation" style="color: rgb(227, 114, 14); font-weight: bold;">https://badges.mozilla.org/en-US/badges/badge/Running–Web-QA-Automation</a></p> + +<p style="color: rgb(51, 51, 51); margin-bottom: 1.4em;">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!</p> + +<div style="color: rgb(51, 51, 51);"> </div> +</div> + +<p> </p> |