Some Tricky Manual Testing Questions & Answers

Interviews play a major role in the life of any human. Mostly all of us aim to clear the interviews on the first attempt.

In this tutorial, you will learn some tricky manual testing questions and answers, along with examples to help you crack the interview easily.

These interview questions will be very useful for beginner, intermediate and experienced testers. These questions are quite tricky, hence you need to answer them carefully.

Let’s move on!!

Manual Testing Question and Answer

Manual Testing Tricky Interview Questions

Below mentioned are some of the most important terms that you must know before attending any manual testing interview.

Let’s learn more about each term, along with simple examples for your easy understanding.

  • Boundary Value Analysis
  • Equivalence Testing
  • Error Guessing
  • Desk Checking
  • Control Flow Analysis

Boundary Value Analysis

It is the process of selecting test cases/data by identifying the boundaries that separate valid and invalid conditions. Tests are constructed to test the inside and outside edges of these boundaries.

In addition to the actual boundary points or a selection technique, test data are chosen to lie along the “boundaries” of the input domain [or output range] classes, data structures, procedure parameters, etc.

Choices often include maximum, minimum, and trivial values or parameters.

For Example – Input data 1 to 10 (boundary value)
Test input data 0, 1, 2 to 9, 10, 11

Equivalence Testing

The input domain of the system is partitioned into classes of representative values so that the number of test cases can be limited to one-per-class, which indeed represents the minimum no. of test cases that must be executed.

For Example – valid data range: 1-10
Test set: 2; 5; 14

=> Click here to know more about Boundary Value Analysis and Equivalence Testing

Error Guessing

It is a test data selection technique. The selection criterion is to pick values that seem likely to cause errors. Error guessing is mostly based upon experience, with some assistance from other techniques, such as boundary value analysis.

Based on the experience, the test designer guesses the type of errors that could occur in a particular type of software and designs test cases to uncover them.

For Example, if any type of resource is allocated dynamically, then a good place to look for errors is in the de-allocation of resources.

Are all resources correctly de-allocated, or are some lost as the software executes?

Desk Checking

Desk checking is conducted by the developer of the system or program. The process involves reviewing the complete product to ensure that it is structurally sound and that the standards and requirements have been met.

This is the most traditional means of analyzing a system or program.

Control Flow Analysis

It is based upon a graphical representation of the program process. In control flow analysis, the program graphs have nodes that represent a statement or segment possibly ending in an unresolved branch.

The graph illustrates the flow of program control from one segment to another, as illustrated through branches.

The objective of control flow analysis is to determine the potential problems in logic branches that might result in a loop condition or improper processing.

We hope this tutorial will help you ace any Manual Testing interview.

Recommended Reading

15 thoughts on “Some Tricky Manual Testing Questions & Answers”

    • for equivalance class partioning the input has to be partioned into groups (valid and invalid)
      ex:if customer needs userID field with only alphabets(A-Z) then valid data is A-Z and invalid data is a-z,special characters,blank spaces…

      Reply
  1. Excellent topics coverd, I appreciate your knowledge. I suggest you if you give more typical examples for the above topics useful for viewres of this blog. Once again thanks for the above explanation.

    Reply
  2. hiii….i just done s/w testing course n m still confuse abt boundary value.I knw abt it bt m want tO knw simple thing that “what is boundary value”.plzzz give the definition

    Reply
    • Hi Akash,

      In simple word Boundary values means its the both edge values. And here we don’t need to check all the input data instead only the boundary values we will check.
      Lets say the valid inputs of a text field is 1-10.
      Here for checking this we can divide the data into some equivalent partitions such as:
      <1 i.e 0, 1-10, 11-99 etc.
      Here the boundary values are 0,1,10,11,99 etc. So assumption is if these boundary values will pass then overall it will pass. And if any particular boundary vakue is failed means that particular range will fail.

      Reply
  3. Hi vijay,

    In one of my interview I have been asked following question.

    If we are testing web application on mobile, so from the functionality point of view is it necessary to test all functionality in each platform (iPhone, Android, BlackBerry etc.) separately? or testing on one platform is enough?

    Reply
    • I think it depends on the scope of requirements and available resources. especially if, it is manual testing, testing on Android and IOS is sufficient.

      Reply
  4. when defect found in production then we called it as a “failure”…once we do all the testings we have to do testings like exploratory and regression testing ….by doing these testings it tests small part of the application….with that we increase product quality….

    Reply

Leave a Comment