QA Tasks

The document outlines tasks for QA testing including finding bugs on websites, identifying duplicate pages, and completing a bug finding exercise. It provides steps to navigate to a bug finding site, review bug types, locate and document issues found.

Uploaded by

Gamer boy

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

15 views3 pages

QA Tasks

Uploaded by

Gamer boy

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 3

QA Tasks

Task 1
1. Go through https://mulearn.org/team find the bugs. Submitting format
https://github.com/gtech-mulearn/mulearn → Click on Issues →New Issue → Issue Title
- InternTask1_[YourName]_IssueNumber

Task 2
2. Check the website https://learn.mulearn.org/challenges find bugs and also find duplicate
pages of the same. Submitting format https://github.com/gtech-mulearn/mulearn →
Click on Issues →New Issue → Issue Title - InternTask2_[YourName]_IssueNumber

Task 3
3. Step 1: Open the link in a browser (https://academybugs.com/find-bugs/)
This is the starting point of the bug-finding exercise. You're instructing the user to
navigate to a specific webpage using their web browser.

Step 2: When you open this link, there are 25 bugs on the page
Upon opening the provided link, the user will encounter a webpage that contains 25
identified bugs. These bugs could be any kind of issues or problems on the website.

Step 3: Before finding the bug just go through the “Types of bugs” on this page
Before starting the bug-finding process, it's important for the user to familiarize
themselves with the different categories or types of bugs that might be present on the
webpage. This information is likely provided on the webpage itself.

Step 4: Identify and understand the types of bugs

In this step, the user is encouraged to study and comprehend the various types of bugs listed on
the webpage. This knowledge will help them recognize and categorize the bugs they encounter.

Step 5: Click on “Find bugs” and start to find the bug

After gaining an understanding of the different types of bugs, the user is instructed to click on a
button or link named "Find bugs" to begin the actual bug-finding process. This likely triggers a
script or function that highlights or identifies bugs on the webpage.
Step 6: When you find the bug, it shows details about that issue or bug

Once a bug is discovered, the system provides detailed information about the specific issue.
This could include a description of the problem, its location on the webpage, and potentially
steps to reproduce it. Find minimum 15 bugs
Eg : image

Step 7: Please note the issue in the following format…

Here, the user is asked to document the details of the bug they found in a specific format. This
format might include fields like Bug ID, Bug Type, Description, Location, and Steps to
Reproduce.
Overall, this process guides users through the steps of finding and documenting bugs on the
specified website. It combines both theoretical understanding (types of bugs) and practical
application (finding and documenting bugs).

All the details are available when the bug will found