1)Web Application - How do you test?
1.Requirement Analysis
Understand what the application is supposed to do.
Example: If it’s a booking site, users should be able to search, book, and pay.
2.Functional Testing
Check if features work as expected.
Example test cases:
Login with valid and invalid credentials.
Submit a form with required fields missing.
Add items to cart and checkout.
3.UI/UX Testing
Verify layout, colors, fonts, and responsiveness.
Example: Does the site look good on mobile and desktop?
4.Compatibility Testing
Test on different browsers (Chrome, Firefox, Edge, Safari).
Example: Ensure buttons and forms behave the same everywhere.
5.Performance Testing
Check speed and load handling.
Example: Does the site still work if 100 users log in at once?
6.Security Testing
Ensure data is safe.
Example: Test SQL injection, XSS attacks, and secure login.
7.Database Testing
Verify data is stored and retrieved correctly.
Example: After booking, does the database show the correct record?
8.Regression Testing
Re-test old features after new updates.
Example: If payment gateway is updated, check login and booking still work.
Simple Interview Answer:
"To test a web application, I start with functional testing to check features like login and forms, then move to UI, compatibility, performance, and security testing. I also do regression testing after updates to ensure nothing breaks."
2)Installed Software - How do you test?
Installation Testing:
Verify the software installs correctly with no errors.
Example: Check if the installer runs, creates necessary files, and shortcuts appear.
Functional Testing:
Ensure features work as intended.
Example: If it’s a text editor, test creating, saving, and opening files.
Compatibility Testing:
Test on different operating systems, versions, and hardware.
Example: Does the software run on Windows 10, Windows 11, or macOS?
UI/UX Testing:
Check menus, buttons, and navigation.
Example: Is the interface user-friendly and consistent?
Performance Testing:
Measure speed, memory usage, and CPU consumption.
Example: Does the app slow down when handling large files?
Security Testing:
Ensure data protection and safe installation.
Example: Check if the software avoids unauthorized access or malware-like behavior.
Uninstallation Testing:
Verify the software can be removed cleanly.
Example: After uninstall, no leftover files or registry entries remain.
Regression Testing:
After updates or patches, recheck old features.
Example: If a bug fix is applied, confirm other features still work.
Simple Interview Answer:
"To test installed software, I start with installation and uninstallation checks, then verify functionality, compatibility across systems, UI, performance, and security. Finally, I do regression testing after updates to ensure stability."
3)Mobile App - How do you test?
1.Installation & Launch Testing
Verify the app installs correctly from the store or APK/IPA file.
Example: Check if the app icon appears and launches without crashing.
2.Functional Testing
Ensure all features work as intended.
Example test cases:
Login/signup with valid and invalid inputs.
Push notifications appear correctly.
In‑app purchases complete successfully.
3.UI/UX Testing
Check design consistency, navigation, and responsiveness.
Example: Buttons are clickable, text is readable, and layout adapts to screen sizes.
4.Compatibility Testing
Test on different devices, screen resolutions, and OS versions (Android/iOS).
Example: Does the app run smoothly on both Android 12 and iOS 16?
5.Performance Testing
Measure speed, battery usage, and memory consumption.
Example: Does the app lag when loading large images or data?
6.Network Testing
Check behavior under different network conditions (Wi‑Fi, 4G, 5G, offline).
Example: Does the app show an error message when offline?
7.Security Testing
Verify data protection and secure communication.
Example: Test for vulnerabilities like insecure login or data leaks.
8.Interrupt Testing
Check how the app behaves when interrupted.
Example: Incoming call, SMS, or switching apps while using it.
9.Uninstallation Testing
Ensure the app can be removed cleanly.
Example: No leftover files or settings remain after uninstall.
Simple Interview Answer:
"To test a mobile app, I check installation, functionality, UI/UX, compatibility across devices, performance, network behavior, security, and how it handles interruptions. I also verify clean uninstallation and do regression testing after updates."
4)Bug Reporting - Fields (Severity, Steps To Reproduce, Environment, etc)
Bug ID / Title
Short, clear name for the bug.
Example: "Login button not working on mobile."
Severity
How serious the bug is (e.g., Critical, Major, Minor, Trivial).
Example: Critical – prevents user from logging in.
Priority
How urgently it should be fixed (e.g., High, Medium, Low).
Example: High – affects all users.
Environment
Details about where the bug occurred.
Example: Android 12, Chrome browser v105, Wi‑Fi network.
Steps to Reproduce
Exact actions to recreate the bug.
Example:
Open app
Go to login page
Enter valid credentials
Click "Login"
→ Button does nothing
Expected Result
What should happen.
Example: User should be logged in and redirected to dashboard.
Actual Result
What actually happened.
Example: Login button is unresponsive.
Screenshots / Logs
Visual proof or error logs to help developers.
Example: Screenshot of blank screen after login click.
Reporter Details
Who found the bug and when.
Example: Reported by QA tester on 18 Aug 2026.
Simple Interview Answer:
"A bug report usually contains fields like Title, Severity, Priority, Environment, Steps to Reproduce, Expected vs Actual Result, and supporting evidence like screenshots or logs. This helps developers quickly understand and fix the issue."
5)Compatibility Testing - OS, Browser
Compatibility Testing ensures that your application works correctly across different Operating Systems (OS) and Browsers. Here’s how you can approach
6)Severity vs Priority
Examples:
High Severity, Low Priority:
A crash occurs in a rarely used feature.
Serious technically, but can be fixed later.
Low Severity, High Priority:
Company logo is misspelled on the homepage.
Functionality is fine, but business impact is huge → must fix quickly.
Top comments (0)