Scribd
Upload
8 views3 pages

Manual Testing Question

The document outlines key concepts in manual testing, including the Bug Life Cycle, differences between various testing types, and the Software Testing Life Cycle (STLC). It discusses best practices for writing test cases, criteria for automation, and considerations for logging bugs. Additionally, it highlights the roles of Agile methodology and testing phases such as Alpha and Beta testing.

Uploaded by

Sai Sumanth Naidu Pasupuleti
Copyright
© © All Rights Reserved
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
8 views3 pages

Manual Testing Question

The document outlines key concepts in manual testing, including the Bug Life Cycle, differences between various testing types, and the Software Testing Life Cycle (STLC). It discusses best practices for writing test cases, criteria for automation, and considerations for logging bugs. Additionally, it highlights the roles of Agile methodology and testing phases such as Alpha and Beta testing.

Uploaded by

Sai Sumanth Naidu Pasupuleti
Copyright
© © All Rights Reserved
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

Manual TesTing QuesTiOns

3. What is Bug Life Cycle?

1. Have you worked in Agile methodology? The Bug Life Cycle refers to the stages a defect goes
Explain it. through from identification to closure:

Yes, Agile methodology is an iterative and 1. New: The bug is logged.


incremental approach to software development where 2. Assigned: Assigned to a developer for fixing.
requirements and solutions evolve through
collaboration between cross-functional teams. Agile 3. Open: Developer starts working on it.
promotes adaptive planning, evolutionary
4. Fixed: Developer fixes the issue.
development, early delivery, and continuous
improvement. It typically follows frameworks like 5. Retest: Tester verifies the fix.
Scrum or Kanban. Key ceremonies in Scrum include
6. Verified: If the fix works, the bug is marked as
sprint planning, daily stand-ups, sprint reviews, and
verified.
retrospectives.
7. Reopened: If the issue persists, it is reopened.
8. Closed: The bug is confirmed as fixed and no
2. Explain the points you consider while writing
longer exists.
good test cases.
- Clear and concise: Test cases should have a clear
objective and simple instructions. 4. Difference between Test Scenario vs Test Case
- Coverage: Ensure that all functional requirements - Test Scenario: A high-level concept of what to test
are covered. (e.g., Verify user login functionality).
- Traceability: Link test cases to specific - Test Case: A detailed step-by-step document with
requirements or user stories. inputs, execution conditions, and expected results for
a specific scenario.
- Data preparation: Include input data and
preconditions.
- Expected result: Define expected outcomes for 5. Difference between Functional vs Non-
validation. Functional Testing
- Reusability: Write test cases that can be reused for - Functional Testing: Validates the features and
regression testing. functions of the software system.
- Priority: Assign priority based on the criticality of - Examples: Unit testing, integration testing, system
the feature. testing.
- Non-Functional Testing: Tests the performance, - Alpha Testing: Conducted by the development team
usability, and reliability of the system. and QA in a controlled environment before release.
- Examples: Performance testing, load testing, - Beta Testing: Conducted by end users in a real
security testing. environment after Alpha testing to gather feedback.

6. Difference between Smoke and Sanity Testing 9. How many tests have you automated in a single
sprint?
- Smoke Testing: Initial testing to check whether the
major functionalities are working. Performed after a The number depends on the complexity and scope of
new build is deployed. the sprint, but typically ranges between 10 to 20
automated test cases per sprint.
- Sanity Testing: Focuses on verifying specific
functionalities after a minor code change to ensure
they work as expected.
10. How do you decide which test cases to
automate?
7. What is STLC in software testing? - Repeatability: Test cases that are executed
frequently.
STLC (Software Testing Life Cycle) refers to the
process followed during software testing: - High-risk areas: Test cases that cover critical
functionalities.
1. Requirement Analysis: Understanding the
requirements. - Data-driven tests: Tests that require multiple data
sets.
2. Test Planning: Creating a test strategy and plan.
- Regression tests: Test cases required for regression
3. Test Case Development: Writing test cases.
cycles.
4. Environment Setup: Preparing the testing
- Stable features: Tests for functionalities that are not
environment.
expected to change often.
5. Test Execution: Running test cases and logging
defects.
11. Which test cases would you not automate?
6. Test Closure: Ensuring all test objectives are met
and generating test closure reports. - Exploratory tests: Tests requiring human intuition.
- One-time execution tests: Tests executed only once.
8. Difference between Alpha and Beta Testing - UI tests with frequent changes: Tests for unstable or
frequently changing interfaces.
- Complex test scenarios: Tests that are too complex
to automate effectively.

12. Tell me, is 100% automation possible?


No, 100% automation is not practical. Some test
cases require manual testing due to their complexity,
exploratory nature, or need for human judgment.

13. What are important things you would


consider when logging a bug?
- Title: A concise and meaningful summary.
- Steps to reproduce: Clear steps to replicate the
issue.
- Actual result: What is currently happening.
- Expected result: What should happen.
- Severity and priority: Impact and urgency of the
bug.
- Attachments: Screenshots, logs, or videos.
- Environment details: Browser, OS, or application
version.

14. Where do you write your test cases? In Excel


or some other tool?
Test cases are often written in tools like JIRA,
TestRail, or Zephyr. Excel can also be used for
smaller projects or when specialized tools are
unavailable.

You might also like