Test case Manual Testing Question and

Answers.
1. What is SDLC?
The Software Development Life Cycle (SDLC) is a step-by-step process
to design, develop, test, and deploy the software.
1. Planning
2. Requirement Analysis
3. Design
4. Development/Coding
5. Testing
6. Deployment
7. Maintenance
2. Explain Each phase of SDLC?
1. Planning: Setting goals, timelines, and resources for a project.
2. Requirement Analysis: Understanding and documenting what the system should
do.
3. Design: Creating the structure for the system based on requirements.
4. Development/Coding: Writing the actual code to build the software.
5. Testing: Checking the software for bugs and ensuring it works as expected.
6. Deployment: Releasing the software for users to use.
7. Maintenance: Ongoing support and updates after the software is deployed.
3. What are the different models of SDLC?
1. Waterfall model
2. V Model
3. Spiral Model
4. Write any two advantages and disadvantages of the Waterfall model.

Advantages of Waterfall Model

 Simple and easy to use.
 Initial investment is less since the testers are hired at the later stages.
Disadvantages of Waterfall Model
 Requirement changes are not allowed.
 Testing will start only after coding.
5. Write any two advantages and disadvantages of the V model.

Advantages of V model
 Testing is involved in every phase.
 Tester role will start in the requirement phase itself
Disadvantages of V model:
 Documentation is more. Requirement changes are not allowed.
  Initial investment is more. All people will be hired at the beginning level.

6. What is software testing? Why is it required?

Software testing is a process to check whether a product is developed as per requirements or
not.
Software Testing is
 Find Bugs: Testing helps us find errors or bugs so they can be fixed before the
software is used.
 Ensure Quality: It makes sure the software does what it's supposed to do and works
well.

7. What are errors, bugs/defects, and failures?

Error: A human mistake made during the design or coding of the software.
Defect: A mismatch between the actual behaviour of the software and the expected
behaviour, usually found during testing.
Failure: When the software does not perform a required function.

8. What is verification in software testing?

Verification: Checks whether we are building the correct application as per the
requirements.
9. What is validation in software testing
Validation: Checks whether we are built the correct application as per the requirements.

10. What are the different ways to perform static testing?

Static testing is done in three ways:
 Review
 Walkthrough
 Inspection

11. What are the different types of dynamic testing?

Dynamic testing is classified as follows.
i. White box testing
ii. Black box testing
iii. Gray box testing
12. What is white-box testing?

White-box testing is a type of software testing that focuses on testing the internal structure
(code) and workings of the software.

13. What is black-box testing?

Black-box testing: Testing that focuses on the functionality of the software without looking at
its internal code.

14. What is Gray-box testing?

It is a combination of both white-box and black-box testing, where the tester has partial
knowledge of the internal workings.

15. What are the different levels of testing?

 Levels of testing
1. Unit testing
2. Integration testing
3. System testing
4. UAT (User acceptance testing)
16. Explain Unit Testing
 Unit testing is conducted on a single program or single module.
 Unit testing is a white box testing technique.
 Unit testing is done by the developer.
 Example: White box testing
17. Explain Integration Testing
 Integration testing performed between two or more modules.
 Integration testing focuses on checking data communication between multiple
modules. Integration testing is a white box testing technique.
 Done by Developers and Testers.
 Example: Gray box testing

18. Explain System testing

 System testing is testing where we test entire application from starting to

end point.
 System Testing is a level of testing that validates the complete and fully
integrated software product. The purpose of a system test is to evaluate the
end-to-end system specifications.
 Example: Black box testing
 This kid of testing performed by tester.
System testing is divided in two types,
1. Functional Testing
2. Non-Functional Testing

19. Explain user acceptance testing

UAT (User Acceptance Testing) is when client test software to make sure it meets
their needs and works correctly.

20. What is Alpha and Beta Testing in UAT testing?

 Alpha Testing: This is the first stage of testing, done by the developers or a special
testing team to find bugs before real users see the software.
 Beta Testing: This is done after Alpha testing, by real users in a live environment, to
catch any remaining issues and ensure the software works well for everyone.

21. What is STLC? Mention it’s phases?

STLC stands for Software Testing Life Cycle, which is the process use to test the software.

STLC phases
There are following six major phases in every Software Testing Life Cycle Model (STLC
Model):
 1. Requirement Analysis: Understanding what the software should do by reviewing user
needs.
2. Test Plan: A document gives information about the strategy, scope, and schedule for
testing.
3. Test Designing: Creating test cases and scenarios based on the requirements.
4. Test Environment Setup: Preparing the hardware and software needed for testing.
5. Test Case Execution: Running the test cases to check the software.
6. Defect Reporting and Tracking: Identifying bugs and tracking their resolution.
7. Test Closure/Sign-off: Finalizing testing and confirming the software is ready for release.
22. What is Test Case and Test Scenario?

A Test Scenario is defined as any functionality that can be tested. Test Scenario concentrates
on what to be tested.

A Test Case is a Step-by-step action to be performed to check the functionality of an

application.

23. What are all the steps involved in writing a Testcase?

The following are the contents of test case document.
§ Test case ID.
§ Test case title/Test Scenario
§ Test case description.
§ Precondition
§ Steps/Actions
§ Test data.
§ Expected result.
§ Actual result
§ Status (Pass/fail)

24. What is defect and defect report?

A mismatch between the actual behaviour of the software and the expected
behaviour, usually found during testing.
Defect report is a document which contains list of defects with clear information.
25. What is a positive test case and negative test case?
A test case with valid input is called a positive testcase.
A test case with invalid input is called negative testcase.
26. What is test passed and test failed?
• Test passed means expected and actual results are equal i.e. same
• Test failed means expected and actual results are not equal i.e. different.

27. What is a defect report?

 A defect report is a document which contains a list of defects with clear information.
 Defect report is prepared by tester after executing testcases
28. What are the contents of the defect report?
The contents of the defect report are
1. Defect Id
2. Defect Description
 3. Version
4. Steps to reproduce
5. Date Raised
6. Reference
7. Detected by
8. Status
9. Fixed by
10. Date Closed
11. Severity

29. How do you report bug/defect? (or)

How will you inform the developers about the bugs?
▪ By preparing and sending bug report to the development team, the bug is reported.
30. Explain content of the defect report.
Bug report should contain the following details to reproduce the defect/bug
 Bug id - Unique identification number for the defect.
 Defect Description - Detailed description of the defect including information about the
module in which the defect was found.
 Version - Version of the application in which the defect was found.
 Steps - Detailed steps along with screenshots with which the developer can reproduce
the defects.
 Date raised - Date when the defect is raised.
 Detected by - Name/id of the tester who rai

31. What is a priority in defect report?

 Priority means “Importance of the defect with respect to customer requirement”.
 Priority states that the order in which a defect should be fixed.
 The values of priority could be low/medium/high based on the urgency.
32. What is the severity in defect report?
 Severity means “Seriousness of the defect with respect to functionality”.
 It indicates the degree of impact the defect has on the functionality.
 The different types of severity are blocker, Critical, Major, Minor.
 The values of severity could be low/medium/high based on the impact
33. Have you used any reporting tool to report defects?
No. I used to excel sheet to report
34. Do you know any defect reporting tools?
Yes.
Jira
Bugzilla
Click up

35. What are the black box testing design techniques?

• ECP (Equivalent Class Partitioning)
• BVA (Boundary Value Analysis)
• Decision Table Technique
• State Transition Technique
• Error Guessing
36. What are the types of System Testing?
 1. Functional Testing
2. Non-Functional Testing
3. GUI Testing
4. Usability Testin
37. What is Functional Testing?
− Functional testing checks if a software ‘s feature works as per requirement or not.
− In functional Testing, we test the following:
1. Object (GUI element) properties,
2. Database,
3. Error Handling,
4. calculations/Manipulations,
5. Links,
6. Cookies and sessions.
38. What is non-functional testing?
Non-functional testing checks how well a software works, such as its speed and ease of use.
39. What are the types of non-functional testing?
Various types of Non-Functional testing are:
1. Performance Testing
a. Load test,
b. Stress test,
c. Volume test
2. Security Testing
3. Recovery Testing
4. Compatibility Testing
5. Configuration Testing
6. Installation Testing
7. Sanitation/ Garbage Testing
40. What is performance testing?
Checking the performance of the application. How well the application responds to user
requests.
41. What are the different types of performance testing?
a. Load testing
b. Stress testing
c. Volume testing
42. What is Load Testing? Name the tool used for load testing?
By increasing the number of users, check how well the application responds and how the
speed is.
Tools which used to run load test by creating virtual user
• Ex. Load testing tool -- Load runner.
43. What is stress testing?
Stress testing checks how the application behaves when the number of users suddenly
increases and decreases.
44. What is volume testing?
Volume testing checks how much data can handle the application.
45. What is security testing?
Security testing checks if the application is safe from hackers and unwanted access.
Mainly focused on Authentication/Authorization/Access Control
• Authentication is checking whether the provided username and password
 are valid or not.
• Authorization → if the user is valid, he is allowed to do certain things. He
doesn’t have the right to do all.
• Access control →Verifying the permission of the valid user.
46. What is GUI testing?

GUI testing checks if the WebElements like buttons, menus, and other visual parts of
an application work correctly and look good.

47. What is Usability Testing

Checking how easily the end-user can understand and operate the
application is called usability testing.
− Example: whether application is comfortable with mouse and through
keyboard, is tested.
− Here, the developer is responsible for making software as user comfortable.
48. What is Regression testing?
Regression testing checks if anything that was working before is not working after a bug
fixing or new changes.
49. What is Retesting?

Retesting checks if a specific issue that was found before has been fixed properly.

50. What is difference between regression and retesting?

a. Regression testing checks many parts of the application to make sure that nothing
else is broken after fixing the defect.
b. Retesting only focuses on the specific part where the bug was found.

a. Regression testing is done after any change to check overall stability.

b. Retesting is done only after a bug fix to check if that specific issue is resolved.
51. When should we do retesting?
Once the bug is fixed by developer, retesting will be done by tester.
52. When should we test for regression?
Whenever there are changes in code like adding new features, fixing bug or updating a
current feature we should do regression testing.
53. What is a test case?
• It is the step by step actions (sequence of steps) to be performed to validated the
functionality of AUT.
• It contains testcase ID, test steps, expected result, actual result.
• It is prepared by test engineer.
• Here, concentrates on how to test the selected area.
• Using the test case a test engineer can compare expected and actual results to
determine whether a software product is functioning as per the requirements of the
customer.
54. Write a defect report for any defect.