Manual Testing Interview Questions for Freshers

Introduction

For newcomers, diving into the world of manual testing can be both thrilling and difficult. It’s important to educate yourself with frequent questions that evaluate your grasp of testing ideas and methodologies as you get ready for your manual testing interview. To help you shine throughout the hiring process, we’ll go over some of the most important manual testing interview questions specifically designed for new hires in this article.

Recruiters are looking for evidence that you can handle the physical scrutiny of manual testing. In this answer, we will introduce you to the fundamental concepts of manual testing, the most frequently asked manual testing interview questions and answers, and some manual testing MCQs that will help impress recruiters in your interview. A wide range of skill levels is represented in the questions, so it’s suitable for both beginners and experts. The manual testing interview will be easier if you prepare and evaluate your answers beforehand.

Now let’s take a look at some frequently asked manual testing interview questions:

1. What is Manual Testing?

Manual testing, which is sometimes regarded as the cornerstone of quality assurance, entails the systematic, practical assessment of software programs to determine whether they adhere to predetermined standards. As a manual tester, you are responsible for carefully carrying out test cases without using automation tools. You will rely on your knowledge to find errors and make sure the program works as intended.

2. What is “use case testing”?

In order to identify and execute the functional requirement of an application from start to finish “use case” is used and the techniques used to do this is known as “Use Case Testing.”

3. What is white box testing and list the types of white box testing?

White box testing technique involves selection of test cases based on an analysis of the internal structure (Code coverage, branches coverage, paths coverage, condition coverage, etc.) of a component or system. It is also known as Code-Based testing or Structural testing. Different types of white box testing are

• Statement Coverage
• Decision Coverage

4. In white box testing, what do you verify?

In white box testing following steps are verified.

• Verify the security holes in the code
• Verify the incomplete or broken paths in the code
• Verify the flow of structure according to the document specification
• Verify the expected outputs
• Verify all conditional loops in the code to check the complete functionality of the application
• Verify the line by line coding and cover 100% testing

5. What is black box testing? What are the different black box testing techniques?

Black box testing is the software testing method which is used to test the software without knowing the internal structure of code or program. This testing is usually done to check the functionality of an application. The different black box testing techniques are

• Equivalence Partitioning
• Boundary value analysis
• Cause-effect graphing

6. What is the difference between UAT (User Acceptance Testing) and System testing?

System Testing: System testing is finding defects when the system undergoes testing as a whole; it is also known as end-to-end testing. In such type of testing, the application suffers from beginning till the end.
UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product will meet the needs of its users.

7. Mention the difference between Data Driven Testing and Retesting?

Retesting: It is a process of checking bugs that are actioned by the development team to verify that they are fixed.
Data Driven Testing (DDT): In data driven testing process, the application is tested with multiple test data. The application is tested with a different set of values.

8. What are the valuable steps to resolve issues while testing?

• Record: Log and handle any problems which have happened
• Report: Report the issues to higher level manager
• Control: Define the issue management process

9. What is the difference between test scenarios, test cases, and test script?

Difference between test scenarios and test cases is that
Test Scenarios: A Test Scenario is any functionality that can be tested. It is also called Test Condition or Test Possibility.
Test Cases: It is a document that contains the steps that have to be executed; it has been planned earlier.
Test Script: It is written in a programming language and it’s a short program used to test part of the functionality of the software system. In other words a written set of steps that should be performed manually.

10. What is Latent defect?

Latent defect: This defect is an existing defect in the system which does not cause any failure as the exact set of conditions has never been met

11. What are the two parameters which can be useful to know the quality of test execution?

To know the quality of test execution, we can use two parameters

• Defect reject ratio
• Defect leakage ratio

12. What is the function of the software testing tool “phantom”?

Phantom is a freeware and is used for windows GUI automation scripting language. It allows us to take control of windows and functions automatically. It can simulate any combination of keystrokes and mouse clicks as well as menus, lists and more.

13. Explain what Test Deliverables is?

Test Deliverables are a set of documents, tools and other components that have to be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development lifecycle

• Before Testing
• During Testing
• After the Testing

14. What is mutation testing?

Mutation testing is a technique to identify if a set of test data or test case is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.

15. What all things you should consider before selecting automation tools for the AUT?

• Technical Feasibility
• Complexity level
• Application stability
• Test data
• Application size
• Re-usability of automated scripts
• Execution across environment

16. How will you conduct Risk Analysis?

For the risk analysis following steps need to be implemented

• Finding the score of the risk
• Making a profile for the risk
• Changing the risk properties
• Deploy the resources of that test risk
• Making a database of risk

17. What are the categories of debugging?

Categories for debugging

• Brute force debugging
• Backtracking
• Cause elimination
• Program Slicing
• Fault tree analysis

18. What are the benefits and drawbacks associated with manual testing?

Advantages of Manual Testing

• Preferable for products with a short life cycle.
• Saves time, money, and resources.
• Ensure the error-free product.
• Usable for exploratory testing, ad hoc testing, and usability testing.
• No need to change the entire code to make minor changes.
• Get accurate user interface feedback.
• Ability to handle difficult use case situations in a better way.
• GUI testing can be done accurately.
• Highly reliable.
• Make user-friendliness better.
• Easy to learn for new testers.
  Disadvantages of Manual Testing
• Not suitable for time-bounded projects and large organizations
• More prone to human errors and mistakes
• Less efficient as the choice of recording the testing process is not available
• Less Reliable
• Regression testing is time-consuming
• Does not cover all the aspects of testing
• Load testing and performance testing can be performed manually
• More expensive in the long run process

19. Who is a manual tester? Write its roles and responsibilities.

The manual tester is a professional who conducts quality checks on software applications without using automation tools or scripting. In essence, the specialty involves manually checking software for errors and fixing them. Manual testers must have the appropriate skills and be able to meet the company’s requirements.
Manual Tester Roles and Responsibilities

• Analyzing client requirements.
• Reviewing written code for compliance with project specifications.
• Creating a test environment for executing test cases.
• Establishing quality assurance strategies and organizing phased testing.
• Organizing and conducting review meetings.
• Executing and analyzing test cases.
• Detecting and fixing bugs.
• Monitor system errors and discuss them with colleagues.
• Keeping in touch with the test manager, etc.

20. Describe the manual testing process.

Among the steps involved in manual testing are:
Requirement analysis

• Test plan creation
• Design test scenarios and test cases
• Test execution and defect reporting
• Evaluating exit criteria and reporting
• Test closure activities

21. Can you tell me what the different levels of manual testing are?

Different levels of testing can be carried out during the development process. Multilevel testing facilitates the identification of bugs early in the development process. The four levels of testing are as follows:

• Unit testing: Essentially, it is a way of testing logically isolated pieces of code within a system called units. Mainly, it focuses on the standalone module’s functional accuracy.
• Integration Testing: Software testing at this level involves combining and testing individual units to see if they work together as they should. This test focuses on the interface between modules.
• System Testing: It involves testing all components of the product as a whole to ensure that overall product requirements are met. The types of system testing include regression testing, usability testing, and functional testing.
  
• User Acceptance Testing: Acceptance testing, also known as UAT (User Acceptance Testing), is the final step in the software testing process. This test determines if the software is ready for release.

22. In order to perform manual testing, what skills are required?

The following are the important manual testing skills to acquire:

• Detail-oriented and able to report test results in a professional manner.
• A strong analytical ability.
• Ability to perform technical testing.
• Familiarity with Agile methodologies.
• Plan and track the testing process.
• Knowledge of SDLC, STLC, SQL, and manual concepts.
• An understanding of test management tools, test tracking tools, and testing techniques.

23. What is test coverage?

Test coverage is a metric that indicates how much of the source code is covered by the tests, allowing the tester to verify the quality of their testing. Testers can use it to determine whether they’re testing everything they’re supposed to. Depending on the way people approach testing, test coverage can mean different things to different people.

• Product: It means looking at test coverage to answer the question: Which features or areas of the software do your tests cover?
• Requirements: The software might work well, but it’s not useful to the customer if it doesn’t satisfy their needs. Requirements coverage indicates how many of the requirements are tested.
• Source Code: This is usually a developer’s domain and is a white-box testing technique. The developer can check how much of their source code is covered by the unit tests.

24.Name some methods that can be used in code coverage.

Code coverage is a software testing metric that measures how many blocks, lines, or arcs of code are executed when a test suite runs. Code coverage can be determined by several methods, including:

• Statement Coverage.
• Decision Coverage.
• Branch Coverage.
• Toggle Coverage.

25.Name some attributes of the test case.

There are various attributes of test cases that make them more reliable, clear, and concise, avoiding any sort of redundancy. Some of them are given below:

• Test Case Id: Unique identifier of the test case.
• Test Summary: One-liner summary of the test case.
• Description: Detailed description of the test case.
• Prerequisite or pre-condition: Set of conditions to be followed before implementing the test steps.
• Test Steps: Detailed steps for performing test cases.
• Test Data: Test data value used in the test case.
• Expected Result: Estimated result to pass the test.
• Actual Result: Actual result after executing the test steps.
• Test Result: Status of the test execution (Pass or Fail).
  Automation Status: Identifier for automation.
• Date: Test execution date.
• Executed By: Person name executing the test case.

Conclusion

If freshers want to start a successful career in quality assurance, they must become proficient in answering manual testing interview questions. During interviews, showcasing your command of the principles of manual testing, the SDLC, test case design, and regression testing can help you stand out and lead to new chances in the software testing field.