1.What is Software Testing?

A. Testing involves operation of a system or application under controlled conditions and

evaluating the results,The controlled conditions should include both normal and
abnormal conditions.
Testing is a process of executing a program with the intend of finding the errors.

2. What is the Purpose of Testing?

A. The purpose of testing is
1· To uncover hidden errors
2· To achieve the maximum usability of the system
3· To Demonstrate expected performance of the system

3. What types of testing do testers perform?

A. Two types of testing
1.White Box Testing 2.Black Box Testing.

4. What is the Outcome of Testing?

A. The outcome of testing will be a stable application which meets the customer Req's.

5. What kind of testing have you done?

A. Usability,Functionality,System testing,regression testing,UAT
(it depends on the person).

6. What is the need for testing?

A. The Primary need is to match requirements get satisfied with the functionality
and also to answer two questions
1· Whether the system is doing what it supposes to do?
2· Whether the system is not performing what it is not suppose to do?

7. What are the entry criteria for Functionality and Performance testing?
A. Entry criteria for Functionality testing is Functional Specification /BRS (CRS)/User
Manual.An integrated application, Stable for testing.

Entry criteria for Performance testing is successfully of functional testing,once all the
requirements related to functional are covered and tested, and approved or validated.

8. Why do you go for White box testing, when Black box testing is available?
A. A benchmark that certifies Commercial (Business) aspects and also functional
(technical)aspects is objectives of black box testing. Here loops, structures, arrays,
conditions,files, etc are very micro level but they arc Basement for any application, So
White box takes these things in Macro level and test these things

Even though Black box testing is available,we should go for White box testing also,to
check the correctness of code and for integrating the modules.

9.What are the entry criteria for Automation testing?

A. Application should be stable. Clear Design and Flow of the application is needed.

10.When to start and Stop Testing?

A. This can be difficult to determine. Many modern software applications are so
complex,and run in such an interdependent environment, that complete testing can
never be done.
Common factors in deciding when to stop are:

Deadlines (release deadlines, testing deadlines, etc.)

Test cases completed with certain percentage passed

[email protected]
Test budget depleted
Coverage of code/functionality/requirements reaches a specified point
Bug rate falls below a certain level
Beta or alpha testing period ends

11.What is Quality?
A. It ensures that software is a Bug free,delivered in time,with in budget,meets customer
requirements and maintainable.Quality standards are different in various areas like
accounting department might define quality in terms of Profit.

12.What is Baseline document?

A. The review and approved document is called as baseline document (i.e)Test plan,SRS.

13.What is verification?
A. To check whether we are developing the right product according to the customer
requirements r not.It is a static process.

14.What is validation?
A. To check whether we have developed the product according to the customer
requirements r not.It is a Dynamic process.

15.What is quality assurance?

A. Quality Assurance measures the quality of processes used to create a quality product.
1.It is a system of management activities.
2.It is a preventive process.
3.It applies for entire life cycle.
4.Deals with Proces.

16.What is quality control?

A. Quality control measures the quality of a product
1.It is a specific part of the QA procedure.
2.It is a corrective process.
3.It applies for particular product.
4.Deals with the product.

17.What is SDLC and STLC?

A. Software development life cycle(SDLC) is life cycle of a project from starting to ending
of the project.
1.Requiremnts Specification. 2.Analysis
3.Design 4.Coding
5.Testing 6.User acceptance test(UAT)
7.Maintainance

Software Test Life Cycle(STLC) is a life cycle of the testing process.

1.Requiremnts Specification.
2.Planning
3.Test case Design
4.Execution
5.Bug Reporting.
6.Maintainance

18.What are the Qualities of a Tester?

A. Tester should have qualities like
1.ability to break 2.paitence 3.communication
4.Presentation 5.team work. 6.negative thinking with good judgment skills

19.What are the various levels of testing?

[email protected]
A. The various levels of testing like
1· Ad - Hoc testing
2. Sanity Test
3. Regression Testing
4. Functional testing
5· Web Testing

20.After completing testing, what would you deliver to the client?

A. It is depend upon what you have specified in the test plan document.
the contents delivers to the clients is nothing but Test Deliverables.
1.Test plan document 2.Master test case document 3.Test summary Report.
4.Defect Reports.

21.What is a Test Bed?

A. Test bed means under what test environment(Hardware,software set up) the
application will run smoothly.

22.Why do you go for Test Bed?

A. We will prepare test bed bcoz first we need to identify under which
environment (Hardware,software) the application will run smoothly,then
only we can run the application smoothly without any intereptions.

23.What is Severity and Priority and who will decide what?

A. Severity and priority will be assigned for a particular bug to know the importance of
the bug.
Severity:How sevierly the bug is effecting the application.
Priority:Informing to the developer which bug to be fix first.

24.Can Automation testing replace manual testing? If it so, how?

A. Yes,it can be done manually when the project is small,having more time.
we can test with minimum number of users.

25.What is a test case?

A. A test case is a document that describes an input, action, or event and an expected
response, to determine if a feature of an application is working correctly.

26.What is a test condition?

A. The condition required to test a feature.(pre condition)

27.What is the test script?

A. Test script is the script which is generated by an automation tool while recording a
application features.

28.What is the test data?

A. Test data means the input data(valid,invalid data) giving to check the feature
of an application is working correctly.

29.What is the difference between Re-testing and Regression testing?

A Re-testing:Executing the same test case by giving the no. of inputs on same build.
Regression testing:Executing the same test case on a modified build.

30.What are the different types of testing techniques?

A. 1.white Box testing 2.Black Box testing.

31.What are the different types of test case techniques?

A. 1.Equilance Partition. 2.Boundary Value Analysis. 3.Error guesing.

[email protected]
32.What ifs the difference between defect, error, bug?
A. Defect:While executing the test case if u found any mismatch,the u will report
it to the development team,that is called defect.

Bug:Once the developer accepts your defect,the it is called as a bug.

error:it may be program error or syntax error.

33.What is the difference between quality and testing?

A. QA is more a preventive thing, ensuring quality in the company and therefore
the product rather than just testing the product for software bugs?

TESTING means "quality control"

Quality control measures the quality of a product
Quality Assurance measures the quality of processes used to create a
quality product.

34.What is the difference between White & Black Box Testing?

A. White Box Testing:Based on the knowledge of the internal logic of an application's
code.Tests are based on coverage of code statements, branches, paths, conditions.

Black Box testing:- not based on any knowledge of internal design or code.
Tests are based on requirements and functionality.

35.What is the difference between Quality Assurance and Quality Control?

A.
Quality Assurance measures the quality of processes used to create a
quality product.
Quality control measures the quality of the product.

36.What is the difference between Testing and debugging?

A. The Purpose of testing is to show the program has bugs.
The Purpose of debugging is find the error/ misconception that led to failure and
implement program changes that correct the error.

37.What is the difference between bug and defect?

A. Defect:While executing the test case if u found any mismatch,the u will report
it to the development team,that is called defect.

Bug:Once the developer accepts your defect,the it is called as a bug.

38.What is the difference between unit testing and integration testing?

A. Unit Testing:It is a testing activity typically done by the developers not by testers,as it
requires detailed knowledge of the internal program design and code. Not always easily
done unless the application has a well-designed architecture with tight code.

integration testing:testing of combined parts of an application to determine if they

function together correctly. The 'parts' can be code modules, individual
applications,client and server applications on a network, etc. This type of testing is
especially relevant to client/server and distributed systems.

39. What is the diff between Volume & Load?

A. Load,stress testing comes under performance testing.
Load Testing:To test the performance of the application by gradually
increasing the user loads.

Stress Testing:TO test the performance of the application and to find the server break

[email protected]
down or where the server crashes.

Volume Testing:To test whether it can able to send max data according to client req's.

40. What is the Diff between Two Tier & Three tier Architecture?
A. Two Tier Architecture:It is nothing but client server Architecture,where client will hit
request directly to server and client will get response directly from server.

Three tier Architecture:It is nothing but Web Based application,here in between client
and server middle ware will be there,if client hits a request it will go to the middle ware
and middle ware will send to server and vise-versa.

41. What is the diff between Integration & System Testing?

A. integration testing:testing of combined parts of an application to determine if they
function together correctly. The 'parts' can be code modules, individual
applications,client and server applications on a network, etc. This type of testing is
especially relevant to client/server and distributed systems.

System Testing:system testing will conducted on the entire system to check whether
it is meeting the customer requirements r not.

42. What is the diff between walk through and inspection?

A. walk through:A 'walk through' is an informal meeting for evaluation or informational
purposes. Little or no preparation is usually required

inspection:Inspection is an formal meeting,here every thing discussed will be

documented such as a requirements spec or a test plan, and the purpose is to find
problems and see what's missing,The result of the inspection meeting should be a
written report.

43. What is the Diff between static and dynamic?

A. Static Testing:Test activities that are performed without running the software is called
Static Testing,it includes inspections,walk throughs and desk checks.

dynamic testing:Test activities that are performed by running the software is called
dynamic Testing.

44. What is the diff between alpha testing and beta testing?
A. Alpha Testing:alpha testing will be performed by client in our environment with
dummy data,In this phase some major bugs can be allowed,later which will be solved by
our development team.

beta testing:beta testing will be performed by client in his environment with real data,In
this phase no bugs can be allowed.

45.What is Recovery testing?

A.testing how well a system recovers from crashes, hardware failures, or other
catastrophic problems.

46. Sanity testing is done to prove the Application is functioning according to

specifications. This level of testing is a subset of regression testing. It Normally includes
a set of core tests of basic GUI Functionality

47. Smoke testing is done to test the most crucial functions of a program Work

[email protected]
48. What is the difference between client-server testing and web based
testing ?

Projects are broadly divided into two types of:

2 tier applications

3 tier applications

CLIENT / SERVER TESTING

[a] This type of testing usually done for 2 tier applications (usually developed for

LAN)Here we will be having front-end and backend.

The tests performed on these type of applications would be

- user interface testing

- manual support testing

- Functionality testing

- compatability testing & configuration testing

- intersystems testing

WEB TESTING

[b] This is done for 3 tier applications (developed for Internet / intranet / xtranet) Here

we will be having Browser, web server and DB server.

The tests performed on these type of applications would be

- user interface testing

- Functionality testing

- security testing

- browser compatability testing

- load / stress testing

- interoperability testing/intersystems testing

- storage and data volume testing

A web-application is a three tier application.

The types of tests which can be applied on this type of applications are:

1. User interface testing for validation & user friendliness

2. Functionality testing to validate behaviors, I/p, error handling, o/p, manipulations,

services levels, order of functionality, links, content of web page & backend coverage’s

3. Security testing

4. Browser compatibility

5. Load / stress testing

6. Interoperability testing

[email protected]
7. Storage & data volume testing

49. WHITE BOX TESTING

This method of testing checking the logical and structure of program keeping the
requirement specification in mind

50. Black Box Testing is testing without knowledge of the internal workings of the item
being tested.

51. How will you check that your test cases covered all the requirements?

By using traceabiltymatrix.
Traceability matrix means the matrix showing the relationship b/w the requirements &
testcases
52. Performance testing can be applied to understand the web site's scalability, or to
benchmark the performance in the environment of third party products such as servers
and middleware for potential purchase.

53. Usability testing is the process by which the human-computer interaction

characteristics of a system are measured, and weaknesses are identified for correction

54. Load testing is usually defined as the process of exercising the system under test
by feeding it the largest tasks it can operate with. Load testing is sometimes called
volume testing, or longevity/endurance testing

55. Stress testing is a form of testing that is used to determine the stability of a given
system or entity. This is designed to test the software with abnormal situations. Stress
testing attempts to find the limits at which the system will fail through abnormal
quantity or frequency of inputs.

56. Cross-browser Testing: - This testing some times called compatibility testing.
When we develop the pages in IE compatible, the same page is not working in Fairfox
or Netscape properly, because
most of the scripts are not supporting to other than IE. So that we need to test the
cross-browser Testing

57. What are the main key components in Web applications and client and
Server applications?(differences)

For Web Applications: Web application can be implemented using any kind of
technology like Java, .NET, VB, ASP, CGI& PERL. Based on the technology,We can
derive the components.

Let's take Java Web Application. It can be implemented in 3 tier architecture.

Presentation tier (jsp, html, dthml,servlets, struts). Busienss Tier (Java Beans, EJB,
JMS) Data Tier(Databases like Oracle, SQL Server etc., )

If you take .NET Application, Presentation (ASP, HTML, DHTML), Business Tier (DLL) &
Data Tier ( Database like Oracle, SQL Server etc.,)

Client Server Applications: It will have only 2 tiers. One is Presentation (Java, Swing)
and Data Tier (Oracle, SQL Server). If it is client Server architecture, the entire

[email protected]
application has to be installed on the client machine. When ever you do any changes in
your code, Again, It has to be installed on all the client machines. Where as in Web
Applications, Core Application will reside on the server and client can be thin
Client(browser). Whatever the changes you do, you have to install the application in the
server. NO need to worry about the clients. Because, You will not install any thing on
the client machine

58. What kind of test cases do you choose and execute for Regression Testing?
Old test cases are executed to check the stability and new functionality test cases are
executed to find the bugs.
In case we have a limited time then we could be executing only high priority test cases
from the old set.

59. Write a test case for Date field and time field?
For date should be vary between 1 to 31
Month should be vary between 1 to 12 year should be greater than 1900
Leap year checking
For Time Format 12 hours or 24 hours Length = 8 if format is 12 hours
Hours vary between >=1 to =<12 min vary between >=0 to =<60 sec vary between
>=0 to =<60
If format AM Display value hrs: min: sec AM
If format PM Display value hrs: min: sec PM
If Format is 24 hours
Hours vary between >=1 to =<24
Min vary between >=0 to =<60
sec vary between >=0 to =<60

60. How will you review test cases?

a) Using Test Case Review checklist
b) Test Case review against functionalities
c) Peer Review/Lead Review/BA Review.

61. What is the difference between positive and negative test cases?
Positive test case: - Perception to validate the functionality of the application.
Negative Test Case: - Perception to break the functionality of the application.

62. What is a GUI test case?

GUI test cases is to check the given application in all aspects like, look & feel, spelling
mistakes, the alignment & availability of all the objects, Consistency of the objects etc.

63. How to write Integration Test cases?

In integration testing you need to write test cases for the Interface between the
modules, for eg: if you are writing test cases for the integration of 3 modules M1, M2
and M3. You need to write the test cases for the individual behavior of M1, M2 and
M3.After that we have to write test cases to test the functional dependency and/or data
reflections between the integrated modules.

64. Explain Software metrics?

Measurement is fundamental to any engineering discipline

Why Metrics?

- We cannot control what we cannot measure!

- Metrics helps to measure quality

[email protected]
- Serves as dash-board

The main metrices are :size,shedule,defects.In this there are main sub metrices.

Test Coverage = Number of units (KLOC/FP) tested / total size of the system

Test cost (in %) = Cost of testing / total cost *100

Cost to locate defect = Cost of testing / the number of defects located

Defects detected in testing (in %) = Defects detected in testing / total system

defects*100

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria

65.What is the difference between Product-based Company and Projects-based

Company?
Product based company develops the applications for Global clients i.e. there is no
specific clients. Here requirements are gathered from market and analyzed with
experts.
Project based company develops the applications for the specific client. The
requirements are gathered from the client and analyzed with the client

66. 1. Functionality Testing

Functionality testing involves making Sure the features that most affect user
interactions work
properly. These include:
· forms
· searches
· pop-up windows
· shopping carts
· online payments

Usability Testing : Many users have low tolerance for anything that is difficult to use
or that does not work. A user's first impression of the site is important, and many
websites have become cluttered with an increasing number of features. For general-use
websites frustrated users can easily click over a competitor's site.

Usability testing involves following main steps

· identify the website's purpose;
· identify the indented users ;
· define tests and conduct the usability testing
· analyze the acquired information

Navigation Testing

Good Navigation is an essential part of a website, especially those that are complex and
provide a lot of information. Assessing navigation is a major part of usability Testing.

Forms Testing

Websites that use forms need tests to ensure that each field works properly and that
the forms posts all data as intended by the designer.

Page Content Testing

[email protected]
Each web page must be tested for correct content from the user perspective for correct
content from the user perspective. These tests fall into two categories: ensuring that
each component functions correctly and ensuring that the content of each is correct.

Configuration and Compatibility testing

A key challenge for web applications is ensuring that the user sees a web page as the
designer intended. The user can select different browser software and browser options,
use different network software and on-line service, and run other concurrent
applications. We execute the application under every browser/platform combination to
ensure the web sites work properly under various environments.

Reliability and Availability Testing

A key requirement o a website is that it Be available whenever the user requests it,
after 24-hours a day, every day. The number of users accessing web site
simultaneously may also affect the site's availability.

Performance Testing

Performance Testing, which evaluates System performance under normal and heavy
usage, is crucial to success of any web application. A system that takes for long to
respond may frustrate the user who can then quickly move to a competitor's site.
Given enough time, every page request will eventually be delivered. Performance
testing seeks to ensure that the website server responds to browser requests within
defined parameters.

Load Testing

The purpose of Load testing is to model real world experiences, typically by generating
many simultaneous users accessing the website. We use automation tools to increases
the ability to conduct a valid load test, because it emulates thousand of users by
sending simultaneous requests to the application or the server.

Stress Testing

Stress Testing consists of subjecting the system to varying and maximum loads to
evaluate the resulting performance. We use automated test tools to simulate loads on
website and execute the tests continuously for several hours or days.

Security Testing

Security is a primary concern when communicating and conducting business- especially

sensitive and business- critical transactions - over the internet. The user wants
assurance that personal and financial information is secure. Finding the vulnerabilities in
an application that would grant an unauthorized user access to the system is important.

67. WHAT IS RATIONAL UNIFIED PROCESS?

RUP is a Software Engineering Process. It is a disciplined approach to assigning tasks,

roles and responsibilities within a development environment.
RUP identifies the static and dynamic aspects of an SDLC. The static aspects are called
the Workflows and the dynamic aspects are called Phases.
The various Phases are Inception, Elaboration, Construction, and Transition.

[email protected]
The 9 Workflows defined by RUP are Business Modeling, Requirements, Analysis and
Design, Implementation, Test, Deployment,
Configuration and Change Management, Project Management, and Environment.

WHEN IS IT APPROPRIATE TO USE RUP?

The basic goal of RUP is to ensure productivity of high-quality software that meets the
needs of its end users within a predictable schedule and budget. Any project team that
aims at producing a software application that is not only meets the quality criteria but
also meets the schedule, budget and maintenance criteria.
ADVANTAGES OF RUP?

RUP, if implemented as per the guidelines by an organization, can result in producing an

application that meets the standards of QA. It contains several tools under its belt that
are easy to learn and apply.

DISADVANTAGES OF RUP?

Although RUP has all the benefits, it has its share of drawbacks. In order to implement
RUP in an organization
- a major re-engineering process of the existing development system has to be
performed
- Tools needed to implement RUP are extremely expensive and may not always be cost-
effective for mid-size to small
projects.
- Training the team members on RUP tools is expensive and time consuming.

68. WHAT IS TESTING?

Testing is a process of verifying the operation of a system or application under

controlled conditions and evaluating the results.

E.g., 'if the user is in interface A of the application while using hardware B, and does C,
then D should happen'.
The controlled conditions should include both normal and abnormal conditions.
Testing should intentionally attempt to make things go wrong to determine if things
happen when they shouldn't or things don't happen when they should. It is oriented to
'detection'.

69. DESCRIBE THE ENTIRE TESTING PROCESS?

Ideally Software Testing Process consists of three phases.

1. Pre-Testing Phase
2. Acceptance Testing Phase
3. Testing Phase
Pre-testing Phase:
Review the Requirement Document
Set up the Testing Environment, MR Tool, Testing Tools, Database, Web Browser, Web
Server etc.
Writing the Test Plan
Collecting the Test data
Writing the Test Cases
Acceptance Testing Phase:
Check the product test entrance criteria
Conducting the basic feature tests
Testing Phase:
Run the Test from Test plan
Use MR Tool to report and track Modifications, enhancements, and Defects

[email protected]
Resolve Defects
Perform regression Tests
Gather Test Metrics

69. WHAT IS A TEST PLAN?

A software project test plan is a document that describes the objectives, scope,
approach, and focus of a software testing effort. The process of preparing a test plan
is a useful way to think through the efforts needed to validate the acceptability of a
software product.

Test plan is used by the testing team and also by the people outside the testing group.
Test Plan also contains the hardware, software and testing tools that could be used in
the testing process.

It contains the test procedure that defined as to how the particular case should be
tested, and the data input (scenario specific).

It primarily contains: Title, Software Version, DB Requirement, Test Tools,

Requirement Number, Test Case, Test Pre-Condition, Test Procedures, Expected
Result, Actual Result, Defect ID, Remarks, Pass/Fail.

70. WHAT IS A TEST CASE?

A test case is a document that describes an input, action, or event and an expected
response, to determine if a feature of an application is working correctly. A test case
should contain particulars such as test case identifier, test case name, objective,
test conditions/setup, input data requirements, steps, and expected results

71. WHAT IS AUTOMATED TESTING?

Automated Testing is the kind of Software testing that is assisted with software tools
that require no operator input, analysis, or evaluation. This category of testing is
performed to reduce the repetitive actions or events in the testing process. Automation
helps in simulating a realistic environment to execute the application enabling the testing
process to be more efficient, effective, productive and synchronized (where required).

72. WHAT IS MANUAL TESTING?

Manual Testing is the part of software testing that requires human input, analysis, or
evaluation. Every test case is manually run following the series of steps described in the
test case description.
There is no automation tool to reduce the repetitive actions and executions. This
requires lot of resources, effort and time. The testers performing the manual testing
have to be innovative and creative in the process.

73.WHAT IS BLACK BOX TESTING?

Black Box testing is testing that is performed from a business/user perspective. It is not
based on any knowledge of internal design or code. Tests are based on requirements
and functionality.

74.WHAT IS WHITE BOX TESTING?

White Box Testing is based on knowledge of the internal logic of an application's code.
Tests are based on coverage of code statements, branches, paths, conditions. Tester is

[email protected]
required to have enough knowledge of the languages and other software used in
developing the software module under test.

75.WHAT IS UNIT TESTING?

It is the most 'micro' scale of testing; to test particular functions or code modules. This is
typically done by the programmer and not by testers, as it requires detailed knowledge
of the internal program design and code. Not always easily done unless the application
has a well-designed architecture with tight code; may require developing test driver
modules or test harnesses.

76.WHAT IS INCREMENTAL INTEGRATION TESTING?

Incremental Integration Testing is continuous testing of an application as new

functionality is added. This requires various aspects of an application's functionality to be
independent enough to work separately before all parts of the program are completed,
or that test drivers be developed as needed. This is done by programmers or by testers.

77.WHAT IS INTEGRATION TESTING?

Test of combined parts of an application to determine if they function together correctly.

The 'parts' can be code modules, individual applications, client and server applications on
a network, etc. This type of testing is especially relevant to client/server and distributed
systems.

78.WHAT IS POSITIVE TESTING

Positive Testing is testing the application against test data that would result in producing
the expected results.

79.WHAT IS NEGATIVE TESTING

Negative Testing is testing the application against all kinds of test input data that could
possibly be fed by a user of the system. It is to done to check if the system is
responding properly to wrong data.

80.WHAT IS SOAK TESTING?

Reveals the longevity characteristics of the system when exposed to extended durations
of high demand.

81.WHAT IS FUNCTIONAL TESTING?

Funtional Testing belongs to the black-box testing category. The goal of Black box
testing is test the functional requirements of an application. Its is usually the job of
testers.

82.WHAT IS SYSTEM TESTING?

System Testing also belongs to the category of Black-box testing and is based on overall
requirements specifications; covers all combined parts of a system.

83.WHAT IS END-TO-END TESTING?

End-to-End Testing is similar to system testing. This belongs to the 'macro' end of the
test scale. Involves testing of a complete application environment in a situation that
mimics real-world use, such as interacting with a database, using network

[email protected]
communications, or interacting with other hardware, applications, or systems if
appropriate.

84.WHAT IS SANITY/SMOKE TESTING?

Sanity Testing is typically an initial testing effort to determine if a new software version
is performing well enough to accept it for a major testing effort. For example, if the new
software is crashing systems every 5 minutes, bogging down systems to a crawl, or
destroying databases, the software may not be in a 'sane' enough condition to warrant
further testing in its current state.

85.WHAT IS REGRESSION TESTING?

Regression Testing can be defined as re-testing after fixes or modifications of the

software or its environment. It can be difficult to determine how much re-testing is
needed, especially near the end of the development cycle. Automated testing tools can
be especially useful for this type of testing.

86.WHAT IS USABILITY TESTING?

Usability Testing is testing for 'user-friendliness'. This will depend on the targeted end-
user or customer. User interviews, surveys, video recording of user sessions, and other
techniques can be used. Programmers and testers are usually not appropriate as
usability testers.

87.WHAT IS PERFORMANCE TESTING?

Performance Testing is identifying the time frame within which the system functions
are performed and checking if the values are within the acceptable limits.
Performance Testing is done on an application only after the functional requirements are
properly tested.
Performance Testing is done in a stand alone environment as well as in a multi-user
environment.
Performance Testing could be very tedious if performed in manual, as it could require lot
of manual resources, time and synchronization. Hence, Automation is preferred.

88.WHAT IS VOLUME TESTING?

Volume Testing is performed to check the response of the system upon flooding with
huge amount or large volumes of data. This is true even for fetching large amounts of
data.

89.WHAT IS STRESS TESTING?

Stress Testing can be defined as a test to determine the breaking point or an

unacceptable performance point of a system to reveal the maximum service level
the system can achieve.

90.WHAT IS LOAD TESTING?

Load Testing can be defined as a test to determine the response times of a system
with various workloads within the anticipated normal production range.
E.g.: Testing an application under heavy loads, such as testing of a web site under a
range of loads to determine at what point the system's response time degrades or fails.

91.WHAT IS SCALABILITY TESTING?

[email protected]
Testing performed to determine the behavior of a system with expanded workloads
simulating future production states such as added data and an increased amount
of users

92.WHAT IS SECURITY TESTING

Security testing is testing if the system is secure from authorized and unauthorized
users. It is a check for confidentiality, integrity, availability, and security from hackers. It
may require sophisticated testing techniques.
93.WHAT IS RECOVERY TESTING?

Testing to check if the system responds to errors and abnormal conditions such as
system crash, hardware failures, communication,power failure or any other catastrophic
problems. This is to check if the system recovers gracefully after crash without losing
useful/critical data and without producing redundant/duplicate/bad data.

94.WHAT IS MUTATION TESTING?

Mutation testing is a method for determining if a set of test data or test cases is useful
by deliberately introducing various code changes ('bugs') and retesting with the original
test data/cases to determine if the 'bugs' are detected. Proper implementation
requires large computational resources.

95.WHAT IS INSTALL/UNINSTALL TESTING?

Install/uninstall testing is performed to test full, partial, or upgrade install/uninstall

processes.

WHAT IS COMPATIBILITY TESTING?

Compatibility testing is done to check how well software performs in a particular

hardware/software/operating system/network/etc. environment.

96.WHAT IS EXPLORATORY TESTING?

Exploratory testing is often taken to mean a creative, informal software test that is not
based on formal test plans or test cases;testers may be learning the software as they
test it.

97.
WHAT IS AD-HOC TESTING?

Ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers
have significant understanding of the software before testing it.

98.WHAT IS ACCEPTANCE TESTING?

Acceptance Testing is the final testing based on specifications of the end-user or

customer, or based on use by end-users/customers over some limited period of time.

99.WHAT IS USER-ACCEPTANCE TESTING?

User Acceptance Testing is done to determine if the software is satisfactory to an end-

user or customer.

[email protected]
100.WHAT IS COMPARISON TESTING?

Comparison Testing is done to compare software weaknesses and strengths to

competing products.

101.WHAT IS ALPHA TESTING?

Alpha Testing is testing of an application when development is nearing completion. Minor

design changes may still be made as a result of such testing. Typically done by end-
users or others, not by programmers or testers.

102.WHAT IS BETA TESTING?

Beta Testing effort is done when development and testing are essentially completed and
final bugs and problems need to be found before final release. Typically done by end-
users or others, not by programmers or testers.

103.WHAT IS AN MR TOOL?

MR Tool is a Modification Request tool also called as a Defect Tracking tool. It is used by
the testing team to communicate with others and keep record of the history of the
defects. this can also be used by the management team to monitor the progress of
defects or modification requests, analyze the quality of the product which could help
make decisions about the release or schedule for the system.

104.HOW DO YOU TRACK DEFECTS USING MR TOOLS?

Each MR contains Severity, Due Date, Assigned to, Status, Release Version, Platform,
Module, Person responsible for the Resolution of the Request, Description of the Request.
This information can be used to track the Requests.

[email protected]