HomeSoftware Testing

Software Testing and Manual Interview Questions and Answers – Part 5

Software Testing and Manual Interview Questions and Answers – Part 5

Software Testing and Manual Interview Questions and Answers – Part 5

1) When should we Stop Testing?

Testing can be stopped when one or more of the following conditions are met:

After test case execution:

Testing phase can be stopped when one complete cycle of test cases is executed after the last known bug fix with agreed upon value of pass-percentage.

Once the testing Deadline is met:

Testing can be stopped after deadlines get met with no high priority issues left in system.

Based on Mean Time Between failure (MTBF):

MTBF is the time interval between two inherent failures. Based on stakeholders decisions, if the MTBF is quite large one can stop the testing phase.

Based on Code Coverage Value:

Testing phase can be stopped when the automated code coverage reaches a specific threshold value with sufficient pass-percentage and no critical bug.

And based on many other factors.

2) What is Test Management Tool?

Test management tool are used to store information on how testing is to be done, Plan testing activities and report the status of quality assurance activities.

It allows to track all the activities list out:

  • Track the Requirement.
  • Write the Test case (or) Scripts.
  • Execute the Scripts.
  • Report issues to Developer.
  • Track the Issues.

The tools have different approaches to testing and thus have different sets of features.

3) What is Testing Process / Life Cycle?

The following are the different things which comprise together to form the Testing Process:

  • Write Test Plan.
  • Create Test Scenarios.
  • Create Test Cases.
  • Executing Test Cases.
  • Test Results.
  • Defect Reporting.
  • Defect Tracking.
  • Defect Closing.
  • Test Release.

4) What is Test Case?

It is a document prepared by the testing team based on the understanding towards the requirement specification. This document consists of line by line procedures/instruction’s to verify the functionality of an application.

5) What are the Various Test Case Design Techniques?

The various Test Case Design Techniques that can be used for generating the test cases are:

  • Equivalence Class Partitioning
  • Boundary Value Analysis
  • Decision Table
  • State Transition Diagram
  • Exploratory Testing
  • Error Guessing

6) What is Error Guessing Technique?

This is a Software Testing Technique which is used to guess invalid inputs/ negative inputs to crack the functionality of the application.

This testing is more (or) less similar to Ad-Hoc Testing performed by experienced Testers or domain experts who are very good at testing and has a skill of guessing defects in the different functionalities of the given application.

7) What is BVA (Boundary Value Analysis)?

Boundary Value Analysis is a software testing technique for designing test cases. It is also kind of Black-Box Test design technique and as the name itself implies, boundary indicates limits to something. Hence this involves designing test scenarios that only focus on the boundary values and validate how the application behaves. Therefore if the inputs are supplied within the boundary values then it is considered to be positive testing and inputs beyond the boundary values are considered to be a part of negative testing.

For example if a particular application accepts VLAN Ids ranging from 0 – 255. Hence here 0, 255 will form the boundary values. Any inputs going below 0 or above 255 will be considered invalid and hence will constitute negative testing.

Equivalence Partitioning and Boundary value analysis are linked to each other and can be used together at all levels of testing.

8) What is ECP (Equivalence Class Partition)?

In Equivalence partitioning, the test data are segregated into various partitions. These partitions are referred to as equivalence Data Classes. It is assumed that the various input data (data can be a condition) in each partition behave the same way. Hence only one particular condition or situation needs to be tested from each partition, as if one works then all the others in that partition is assumed to work. Similarly if one condition in a partition doesn’t work, then none of the others will work.

This Testing avoids Permutation & Combination of testing the application with “N” no of inputs.

Therefore it’s now very apparent that valid data classes (in the partitions) will comprise of positive testing whereas invalid data classes will comprise of negative testing.

Equivalence Partition/ Classes is sub divided into two types

  • Pressman Method
  • Practice Method.

In the same VLAN example above, the values can be divided into say two partitions.

So the two partitions here would be:

Values -255 to -1 in one partition

Values 0 to 255 in another partition.

9) Who can Review Test Cases?

Generally, the Test cases can be reviewed by the people as follows:

  • Senior Test Engineer
  • Team Lead
  • Sometimes Development Team
  • Rarely Customer.

10) How will you Start Reviewing a Test Case?

Initially, we will review the Header of the Test case followed by that the Body of the Test case. Finally, the Footer of the Test case.

Please leave your questions/comments/feedback below.

Happy Learning 🙂

About Me > Kashif Ahmed

Connect to me on Linked In (Click here)

On a mission to contribute to the Software Testing Community in all possible ways.

Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *