Bugs Finding in Software Testing

Task - 1

qe-at-cgi-fi.github.io

bugs in task - 1
toodo spelling bug
placeholder bug
no. of items bug
clear not properly working bug

mandatory steps to do in bugs finding:

1. Browser Compatibility Testing
2. Responsive Design: UI - Laptop, Tab, Mobile
3. Cosmetic Bugs
4. URL Check
5. Data Validation: Username, password
6. Checking all links
7. Home Page
8. Orphan Page
9. Customer: Devices, OS, Browsers
10. Windows 11, Windows 9, mac, iOS, Android -->
11. OS Compatibility Testing
12. Browser Compatibility Testing: Chrome, Firefox, Edge
13. Safari
14. Localization Testing:Vernacular Languages
15. iNTERNATIONALIZATIOn --> i18n Testing
16. Dark / Light Themes

w3c validator used to check the links:

validator.w3.org

80:20 Principle:
80% problems are really caused by 20% of issues.

task - 2

demo.applitools.com

bugs in task - 2:
Data Validation bug
Broken Links
Cosmetic Bugs
OS Compatibility
Browser Compatibility

Installed Software testing:
example - LibreOffice:
1) Installation Testing:
C:\Program Files --> Default Location, Non-default
2) Uninstallation Testing
3) Upgrade Testing:
- Default Location
- Non-default location
OS Installation Testing
Virtual Machines: Simulators: Emulators

Defect Clustering:

• Defect clustering is a core principle in software testing stating that a small number of modules or components contain the majority of all bugs.
• Following the 80/20 Pareto rule, about 80% of operational failures stem from roughly 20% of the program's code, meaning bugs do not spread evenly.

functional bug:

• A functional bug is an error in a software program that stops a feature from working the way it should.
• It happens when an app or website does not do what the rules or user guide say it will do.

Functional testing:

• Functional testing is a type of black-box software testing that verifies whether an application's features work exactly as specified by the project requirements.
• It focuses purely on "what" the system does rather than how it handles its internal logic, performance, or source code.

Non-functional testing:

• Non-functional testing is a type of software testing that evaluates how well a system operates under specific conditions, rather than what functions it performs.
• Instead of checking specific features or user actions, it validates critical quality attributes like performance, security, usability, and scalability to ensure a seamless real-world user experience.

difference between functional and non functionality testing

Web Crawlers:

• Web crawlers (or spiders) are automated software programs that systematically browse the internet to discover, download, and index content from web pages.
• They are primarily used by search engines like Google and Bing to build massive databases so users can find relevant search results quickly.

Difference between priority and severity:

examples:

Bug Reporting - Fields

Severity
Environment: Hardware, Software details:Linux Mint 23, Chrome 105
Steps To Reproduce:

1. Select Build 2 in the drop down.
2. Now give any number in number1, number2 fields
3. Select any arithmetic operation eg. Add
4. Click 'Calculate' button
5. Check Results Expected:5 + 5 = 10 Actual: 55 Attachments: Log Reports, Screenshots

Authorization Testing:
Admin
Super user
user
guest
Authentication Testing - Login - Username, Password

difference between authentication and authorization:

sitemap in website:
to know the structure or map of the web.

Task - 3

bugeater.web.app

bugs in task - 3

References:

Examples of high Severity, Priority, and low Severity, Priority defects in your Current Project? | H2K Infosys Blog

Learn real-world examples of high severity and priority defects in software testing, including low-severity issues and how QA teams prioritize bug fixes.

h2kinfosys.com

Authentication vs Authorization: Definitions, Types, and Differences

This article explains the concepts of authentication and authorization and highlights the differences between the two processes.

heimdalsecurity.com