Software Testing Interview Questions And Answers for freshers and experienced

Capability maturity model and testing maturity model

A Effort estimation consists in predict how many hours of work and how many workers are needed to develop a project. The effort invested in a software project is probably one of the most important and most analysed variables in recent years in the process of project management. The determination of the value of this variable when initiating software projects allows us to plan adequately any forthcoming activities. As far as estimation and prediction is concerned there is still a number of unsolved problems and errors. To obtain good results it is essential to take into consideration any previous projects. Estimating the effort with a high grade of reliability is a problem which has not yet been solved and even the project manager has to deal with it since the beginning.

There are currently seven different Agile methodologies that I am aware of:
1) Extreme Programming (XP)
2) Scrum
3) Lean Software Development
4) Feature-Driven Development
5) Agile Unified Process
6) Crystal
7) Dynamic Systems Development Model (DSDM)

The Butterfly Model focuses on verification and validation of software products and is therefore a good fit for software testing tasks that are incorporated into the V-model of software development. This model provides a graphic picture of the complexity of test tasks using the outline of a butterfly. The areas occupied by the wings and body are approximately related to the level of effort afforded to each of the activities included in the model. In addition to this the reference of the butterfly stems from Chaos theory which states that a small disturbance in part of a system can have huge consequences in some other part of the system. The development of a software system has certain similarities. Small modifications or errors in code may result in significant degradations in an application's performance. The model establishes three general areas of test activities that are illustrated by the butterfly's graphic outline. They are:
Test Analysis (butterfly’s left wing)
Test Design (right wing)
Test Execution (butterfly’s body)
.

Cyclomatic complexity is likely the most widely used complexity metric in software engineering. It describes the complexity of a procedure by measuring the linearly independent paths through its source code. .

1) Corresponding Search Window should be opened & hold corresponding field names in that.
2) Search Operation should be shown correct result while valid data.
3) Search Operation should be shown warning message while enter invalid data.
4) Search Operation should be shown output for all the condition in valid inputs.

1)project name
2)module name
3)defect detected on
4)defect detected by
5)defect id
6)defect name
7)snapshort of the defect(if the defect is in the non reproducible environment)
8)priority,severity,status
9)defect resolved by
10)defect resolved on.

Suppose after completion of an application or module, if another module is to be added, then we need to test the new module as well as the impacted area which is affected by adding a new module.
Impact Analysis will be done to find the impact area of the application by adding a new module. Generally team lead will take the initiate for this.
Team lead will send a mail to client asking for the impact area (if developer is new to domain), also send a mail to development team and testing team asking for the impacted area. After getting the response of all three, team lead will do the consolidated report of all the mails. This consolidated mail will be given to the Test Engineer saying this is the Impact Analysis Report and these are the impact areas.

Closed defects can be reopened due to some of the following reason:
1)Fix given for some other issue may reopen closed defects.
2)Deployment not properly done at the time of fixing new defects.
3)Build issue.
And hence to prevent such defects to reopen, regression testing should be performed on the main flow, scenarios before each testing phase is completed.
And also if time permits quick sanity testing could be carried out to ensure that there is no impact to the application or system before moving on to the next testing phase.

1. Go for Manual Testing in the following cases: Unstable Software. To explore New Software. No Automation suite available. Adhoc testing (unplanned test cases). Not critical project & only one time testing & the effort required is less than the effort required for automation.
2. Go for Automation in the following cases: Stable Software. Any application with a High degree of risk associated with the failure is a good candidate for test automation. (Aircrafts, Patient monitor,) Testing needs to be repeated.
3. Advantages of Automation: Accelerate releases (reduces regression effort) With repeatable tests ensure consistency across multiple supported platforms Greater Application Coverage. Can test more often & more completely Convenient test reports for analysis

We need to check whether Expected Result coresponding to Test case mentioned in Test Case Document is same as Actual Result.If they are same then Test Case passes and if they are not same then we have to see what is different and why it different. After narrowing down we need to raise a defect and map that defect to a Test case.

Soak Testing: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear

In project management trend analysis is a mathematical technique that uses historical results to predict future outcome. This is achieved by tracking variances in cost and schedule performance. In this context it is a project management quality control tool.

Integration testing is actually composed of different types of tests, but its objective is to ensure that the interaction of two or more components produces results taht satisfy functional testing requirements. For Example: Let A and B be two components in which A calls B.    Let Ta be the component level tests of A    Let Tb be the component level tests of B    Tab The tests in A's suite that cause A to call B.    Tbsa The tests in B's suite for which it is possible to sensitize A            -- the inputs are to A, not B.    Tbsa + Tab == the integration test suite (+ = union).

Interoperatability:-To check if the software can co exist with other supporting softwares in the system

Compatibility:-To check if the software runs on different types of operating systems according to customer requirements.

This is one of the SDLC process generally we are following. Its like in fish model thats why it got the name like that.

Need knowledge of SQL query

Varification: it is the process of confirming that s/w "meets its specification".It involves reviews and meetings to evaluate documents,plans,code,requirement and specification.This can be done with checklist,issues lists amd walkthroughs.
It is the examination of the process and checks r we building the product right
Validation: It is the process of confirming that it "meets the user's requirements".Validation typically involves actual testing and take place after varification are

Regression testing means it is the type of testing in which one will conduct testing on an already tested functionality again and again. Regression testing will be conducted in two situations.
1. If the test engineer find any defect on one functionality then after the rectification of that defect from the development department again testing on that defected functionality and retesting the related functionalities of that defected functionality.
2. If the new features are added to that application testing on that new feature functionality and also the related functionality of that new features to be tested.

By word quality we may be more generalized towards our target. but being a quality contious a "quality matix" should have; 1. logical parameterization of our parameters i.e. first we should confirm that is parameter "a" has logical connection with parameter "b"
2. Matrix should be result oriented. we can extract/deduce some logical results from each matrix
3. Every matrix should be complete in its domain it should not further dependant on other parameters other than selected
4. Every matrix should work in boundries of your requirements

Which testing method is used to check the software in abnormal condition?
1) Stress testing
2) Security testing
3) Recovery testing
4) Beta testing