Software Testing Questions

Functional testing is a type of testing that is done against the requirements of the business application. 

Examples of functional testing are Smoke testing, Sanity testing, Regression testing, Usability testing.

Impact Analysis is used in software testing to define all the risks associated with any kind of changes in a product being tested.

Impact Analysis is nothing but analyzing the impact of changes in the deployed product or application. It gives the information about the areas of the system that may be affected due to the change in the particular section or features of the application.

Why Impact Analysis is done :

1. It is done to understand the possible outcome of implementing the change. Inducing too much functionality into a product can reduce the overall performance of the product.

2. To identify all the files, documents and models that might have to be modified if team decides to implement the change in product

3. To estimate the effort needed behind implementing the change

4. To identify the task required to implement the change

5. It will list the dependencies on a specific element

The impact is analyzed on Requirements, Design & Architecture, impact on Test and impact on schedule.

Full binary tree loses its nature when operations of insertions and deletions are done. For incomplete binary trees, extra storage is required and overhead of NULL node checking takes place. So complete binary tree is the better one since the property of complete binary tree is maintained even after operations like additions and deletions are done on it.

BackTracking is used for solving N-Queens problem

Structural Testing is the other name for White Box Techniques.

While a test plan is being created, risks involved in testing the product are to be taken into consideration along with possibility of their occurrence and the damage they may cause along with solutions; if any. Detailed study of this is called as Risk Analysis.

Some of the risks could be:

New Hardware 

New Technology 

New Automation Tool 

Sequence of code delivery 

Availability of application test resources 

Identify and describe the risk magnitude indicators: High, Medium and Low

High magnitude means the effect of the risk would be very high and non-tolerable. Company may face severe loss and its reputation is at risk. Must be tested.

Medium: tolerable but not desirable. Company may suffer financially but there is limited liability or loss of reputation. Should be tested.

Low: tolerable. Little or no external exposure. Little or no financial loss. Company’s reputation unaffected. Might be tested.

Three perspectives of Risk Assessment: Effect, Cause and Likelihood.

To assess risk by Effect, identify a condition, event or action and try to determine its impact.

To asses risk by Cause is opposite of by Effect. Begin by stating an undesirable event or condition and identify the set of events that could have permitted the condition to exist.

To asses risk by Likelihood is to determine the probability that a requirement will not be satisfied.

The biggest concern is the cost incurred for test automation. Also, often s/w test automation requires skilled personnel and authentic test automation tools. Purchasing license of such tools is a costly affair.

Also the time required for test automation is more. Automation often requires recording the sequence of operations you need to perform in order to execute a particular test case and comparing the final o/p with the expected o/p. Functions/macros need also be written sometimes for some test cases. All this could be a time consuming job.