Software Testing Interview Question & Answer

When we find out the bug, we will put into the “open” status. After fixing the bug developer change the status as “fixed”. Again we will test the fixed part, if there is no bug, change the bug status as “Closed” other wise change the bug status as “Reopen”.

The first scenario to be tested is the GUI. The page layout and the design elements used on the website have to be uniform throughout the website. The next part to be tested are the different links provided inside the website. Along with the links, it will also have to be tested, whether internal navigation is smooth and also check if it is complex. The next important aspect to be checked, is the response time of the website. This will also have to checked, when there is heavy load on the system.

The test case formats will vary depending on whether the website is a static website or a dynamic website. The static website will have the front end test cases, navigation test cases. On the other hand, if the website is a dynamic website, then the test cases will be broadly divided under front end test cases, back end test cases, field validations test cases, database test cases, security test cases, etc.

Some of the HTTP Response Objects are write, flush, tell, etc. The subclasses of HTTP Response are HttpResponseRedirect, HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc

The most important factor that needs consideration is the hardware platform, while some may use the Mac platform, some may use Linux, while others may use Microsoft platform. The next comes the browsers and their versions into the picture. Along with the browser versions, the different Plug-Ins also have to be taken into consideration. The resolution of the monitor also with color depth and text size are some of the other configurations.

The browsers that are commonly used are Mozilla Firefox, Google Chrome, Internet Explorer and Opera. Therefore, a web application must be tested on these browsers as well.

Automation is the integration of testing tools into the test environment in such a manner that the test execution, logging, and comparison of results are done with little human intervention. A testing tool is a software application which helps automate the testing process. But the testing tool is not the complete answer for automation. One of the huge mistakes done in testing automation is automating the wrong things during development. Many testers learn the hard way that everything cannot be automated. The best components to automate are repetitive tasks. So some companies first start with manual testing and then see which tests are the most repetitive ones and only those are then automated.

Boundary value analysis is the technique of making sure that behavior of system is predictable for the input and output boundary conditions. Reason why boundary conditions are very important for testing is because defects could be introduced at the boundaries very easily. For example, if you were to write code to simulate following condition -

"Input should be greater than equal to 10 and less than 50"

input >10 AND input Input value 10 in invalid now.
input <=10 AND input Input value 9 is valid now.
input >=10 AND input Input value 50 is valid now
input >=10 AND input >50 -----> Input value 49 is invalid now

Because it is very easy to introduce defects at boundaries, boundary values are important. So for the above example, at the minimum we should have following test cases for boundaries

9, 10, 11 and 48, 49, 50

As a general rule, if you have any input field it should be tested with following set of data at the minimum.

lower_boundary - 1, lower_boundary, lower_boundary + 1 and upper_boundary - 1, upper_boundary, upper_boundary + 1

Lets look into Equivalence Partitioning & Boundary Value Analysis testing techniques .
Equivalence Partitioning - is a block box technique which can be applied to all levels of testing like unit , integration , system etc.
A black box technique where the code is not visible to the tester.
In Equivalence Partitioning , you divide set of test conditions into partitions that can be considered the same.
To understand this better , lets consider the behavior of tickets in the Flight reservation application , while booking a new flight. Ticket values 1 to 10 are considered valid & ticket is booked.
Values 11 to 99 are considered invalid and a error message "Only ten tickets may be ordered at one time" is shown
On entering values 100 and above , the ticket # number defaults to a two digit number
On entering values 0 and below , the ticket # defaults to 1
We can not test all the possible values , because if done , number of test cases will be more than 100 .To address this problem we use equivalence partitioning where we divide the possible values of tickets into groups or sets where the system behavior can be considered the same.
The divided sets are called Equivalence Partitions or Equivalence Classes. Then we pick only one value from each partition for testing.
The hypothesis behind this technique is that if one condition/value in a partition passes all others will also pass. Likewise , if one condition in a partition fails , all other conditions in that partition will fail.
In Boundary Value Analysis , you test boundaries between equivalence partitions
In our earlier example instead of checking, one value from each partition you will check the values at the partitions like 0,1,10,11 and so on
As you may observe, you test values at both valid and invalid boundaries
Boundary Value Analysis is also called range checking.
Equivalence partitioning and boundary value analysis are closely related and can be used together at all levels of testing.

BVT is boundary value testing.
The test data for this testing will always be : 
min-1, min, max, max+1.

It is done by testers.

Top down integration testing we have 3 modules A,
B and C. say A and B are ready but C. But A and B calls
functions from C. In this case, to proceed with the testing
a dummy code is written to work as C. This function/code is
called a Stub.

Same way in Bottom up testing Say A, B are ready but C is
not. And C has to return value to A and B. For this a dummy
code is written to return a vale. This is called Driver.

WinRunner might fail to recognize an object in a GUI in following cases:

- If it is not a standard windows object

- If the browser used is not compatible with the version of WinRunner in use.

GUI Map Editor may not be able to learn the objects in these cases.

Checkpoints help to compare the behavior of current application to its previous version. There are four types of checkpoints in Winrunner:

a.) Text – reads and displays the text contents of GUI objects and bit map and in bitmaps

b.) Bitmap – compares application window or area snapshots to earlier versions of the same window or area

c.) GUI – validates GUI object information (i.e. whether a button is enabled, an item is selected in a list, etc.)

d.) Database – verifies the contents and size of a set of results (based on a database query)

1. Bad requirements - these requirements are unclear, incomplete, too general, or not testable. They cause problems.

2. Unrealistic schedule - Expecting too much result in too less time.

3. Inadequate testing - lack of testing causes problem as no one knows if the system will behave as expected.

4. Adding new features - after development; quite common.

5.Poor communication within the team or with the customer.

- Drivers and stubs are a part of incremental testing.

- The two approaches used in incremental testing are: the top down and the bottom up methods.

- Drivers are used for the bottom up approach.

- Drivers are the modules that run the components that are being tested.

- A stub is used for the top down approach.

- It is a replacement of sorts for a component which is used to test a component that it calls.

Inspection is deserving method with careful consideration of an organization, which concerns about the quality of the product. The process is being done by the quality control department.

Inspection is a disciplined practice for correcting defects in software artifacts.

A walk through is an evaluation process which is an informal meeting, which does not require preparation.

The product is described by the produced and queries for the comments of participants. The results are the information to the participants about the product instead of correcting it.

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.

Pilot testing involves having a group of end users try the system prior to its full deployment in order to give feedback on its performance.

Beta testing is testing of the product in the user environment.

From the definitions, its is evident that beta testing comes at last in development cycle; whereas pilot testing takes place before deployment of the system. Also, beta testing takes place in real time user environment and pilot testing in development environment. A selected group of users do pilot testing whereas beta testing is carried by all users.

severity describes seriousness of the defect with respect to functionality where priority describes importance of defect to solve with respect to customer.
Example:

Suppose we identify two bugs

-The client logo is not appearing on the web site but the site is working fine... in this case the severity is low but the priority is high because from company's reputation it is most imp to resolve. After all the reputation wins more clients and projects and hence increases revinue

Automation is chosen when

-A same set of tests need to be repeated again and again

-When a single test needs to be repeated for a large number of data

-When stable modules needs to be regressed frequently.

Subscribe to: Posts (Atom)