What are SDLC and STLC?

2. When will you start the testing process?

3. What is Test Plan and Test Case?
4. What is the difference between Integration Testing and System Testing?
5. If an ATM machine is given to you, how will you approach to test it and also check
that correct information is updated in the database or not?
6. If a screen is given to you and the enter data in that screen is getting updated into one
table. What all kinds of test case you will write and how will u check in the database
whether the enter data is updated correctly or not?
7. What are Performance Testing, Stress Testing and Load Testing?
8. What is the most difficult test case you have written?
9. What is the top priority bug you have found out in your previous career?
10. What is functional testing?
11. Testing Methodologies.
1. What is diff. between CMMI and CMM levels?
A: - CMM: - this is applicable only for software industry. KPAs -18
CMMI: - This is applicable for software, out sourcing and all other industries. KPA - 25
2. What is the scalability testing?
1. Scalabilty is nothing but how many users that the application should handle
2. Scalability is nothing but maximum no of users that the system can handle
3. Scalability testing is a subtype of performance test where performance requirements
for response time, throughput, and/or utilization are tested as load on the SUT is
increased over time.
4. As a part of scalability testing we test the expandability of the application. In
scalability we test 1.Applicaation scalability, 2.Performance scalability
Application scalability: to test the possibility of implementing new features in the system
or updating the existing features of the system. With the help of design doc we do this
testing
Performance scalability: To test how the s/w perform when it is subjected to varying
loads to measure and to evaluate the
Performance behavior and the ability for the s/w to continue to function properly under
different workloads.
> To check the comfort level of an application in terms of user load. And user
experience and system tolerance levels
> The point within an application that when subjected to increasing workload begin to
degrade in terms of end user experience and system tolerance
> Response time
Execution time
System resource utilization
Network delays

 stress testing
3. What is status of defect when you are performing regression testing?
A:-Fixed Status
4. What is the first test in software testing process?
A) Monkey testing
B) Unit Testing
c) Static analysis
d) None of the above
A: - Unit testing is the first test in testing process, though it is done by developers after
the completion of coding it is correct one.
4. When will the testing starts? a) Once the requirements are Complete b) In
requirement phase?
A: - Once the requirements are complete.
This is Static testing. Here, u r supposed to read the documents (requirements) and it is
quite a common issue in S/w industry that many requirements contradict with other
requirements. These are also can be reported as bugs. However, they will be reviewed
before reporting them as bugs (defects).
5. What is the part of Qa and QC in refinement v model?
A: V model is a kind of SDLC. QC (Quality Control) team tests the developed product
for quality. It deals only with product, both in static and dynamic testing. QA (Quality
Assurance) team works on the process and manages for better quality in the process. It
deals with (reviews) everything right from collecting requirements to delivery.
6. What are the bugs we cannot find in black box?
A: If there r any bugs in security settings of the pages or any other internal mistake
made in coding cannot be found in black box testing.
7. What are Microsoft 6 rules?
A: As far as my knowledge these rules are used at user Interface test.
These are also called Microsoft windows standards. They are
. GUI objects are aligned in windows
All defined text is visible on a GUI object
Labels on GUI objects are capitalized
Each label includes an underlined letter (mnemonics)
Each window includes an OK button, a Cancel button, and a System menu
8. What are the steps to test any software through automation tools?
A: First, you need to segregate the test cases that can be automated. Then, prepare test

data as per the requirements of those test cases. Write reusable functions which are used
frequently in those test cases. Now, prepare the test scripts using those reusable functions
and by applying loops and conditions where ever necessary. However, Automation
framework that is followed in the organization
should strictly follow through out the process.
9. What is Defect removable efficiency?
A: - The DRE is the percentage of defects that have been removed
during an activity, computed with the equation below. The DRE can also be computed for
each software development activity and plotted on a bar graph to show the relative defect
removal efficiencies for each activity. Or, the DRE may be computed for a specific task
or technique (e.g. design inspection, code walkthrough, unit test, 6 month operation, etc.)
Number Defects Removed
DRE = * 100
Number Defects at Start of Process
DRE=A/A+B = 0.8
A = Testing Team (Defects by testing team)
B = customer ( customer )
If dre <=0.8 then good product otherwise not.
10. Example for bug not reproducible?
A: Difference in environment
11. During alpha testing why customer people r invited?
A: becaz alpha testing related to acceptance testing, so,
accepting testing is done in front of client or customer for
there acceptance
12. Difference between adhoc testing and error guessing?
A: Adhoc testing: without test data r any documents performing testing.
Error Guessing: This is a Test data selection technique. The selection criterion is to pick
values that seem likely to cause errors.
13. Diff between test plan and test strategy?
A: Test plan: After completion of SRS learning and business requirement gathering
test management concentrate on test planning, this is done by Test lead, or Project lead.
Test Strategy: Depends on corresponding testing policy quality analyst finalizes test
Responsibility Matrix. This is done by QA. But both r Documents.
14. What is V-n-V Model? Why is it called as V& why not U? Also tell at
what Stage Testing should be best to stared?
A: It is called V coz it looks like V. the detailed V model is shown below.

SRS

Acceptance testing
/
/
System testing

\
HLD (High Level Design)
\
/
\
/
LLD (Low level
Integration testing
Design)
/
\
/
\
Unit Testing
\
/
\
/
Coding

There is no such stage for which you wait to start testing.

Testing starts as soon as SRS document is ready. You can raise defects that are present in
the document. Its called verification.
15. What is difference in between Operating System 2000 and OS XP?
A; Windows 2000 and Windows XP are essentially the same operating system (known
internally as Windows NT 5.0 and Windows NT 5.1, respectively.) Here are some
considerations if youre trying to decide which version to use:
Windows 2000 benefits:
1) Windows 2000 has lower system requirements, and has a simpler interface (no
Styles to mess with).
2) Windows 2000 is slightly less expensive, and has no product activation.
3) Windows 2000 has been out for a while, and most of the common problems and
security holes have been uncovered and fixed.
4) Third-party software and hardware products that arent yet XP-compatible may be
compatible with Windows 2000; check the manufacturers of your devices and
applications for XP support before you upgrade.
Windows XP benefits:
1) Windows XP is somewhat faster than Windows 2000, assuming you have a fast
processor and tons of memory (although it will run fine with a 300 MHz Pentium II and
128MB of RAM).
2) The new Windows XP interface is more cheerful and colorful than earlier versions,
although the less- cartoon Classic interface can still be used if desired.
3 Windows XP has more bells and whistles, such as the Windows Movie Maker, built-in
CD writer support, the Internet Connection Firewall, and Remote Desktop Connection.
4) Windows XP has better support for games and comes with more games than Windows
2000.
5) Manufacturers of existing hardware and software products are more likely to add
Windows XP compatibility now than Windows 2000 compatibility.

16. What is bug life cycle?

A: New: when tester reports a defect
Open: when developer accepts that it is a bug or if the developer rejects the defect, then
the status is turned into Rejected
Fixed: when developer make changes to the code to rectify the bug
Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned
into Closed and if the problem resists again, its Reopen
17. What is deferred status in defect life cycle?
A: Deferred status means the developer accepted the bus, but it is scheduled to rectify
in the next build
18. What is smoke test?
A; Testing the application whether its performing its basic functionality properly or
not, so that the test team can go ahead with the application
19. Do you use any automation tool for smoke testing?
A: - Definitely can use.
20. What is Verification and validation?
A: Verification is static. No code is executed. Say, analysis of requirements etc.
Validation is dynamic. Code is executed with scenarios present in test cases.
21. What is test plan and explain its contents?
A: Test plan is a document which contains the scope for testing the application and
what to be tested, when to be tested and who to test.
22. Advantages of automation over manual testing?
A: Time, resource and Money
23. What is ADhoc testing?
A: AdHoc means doing something which is not planned.
24. What is mean by release notes?
A: Its a document released along with the product which explains about the product.
It also contains about the bugs that are in deferred status.
25. Scalability testing comes under in which tool?
A: Scalability testing comes under performance testing. Load testing, scalability
testing both r same.
26. What is the difference between Bug and Defect?
A: Bug: Deviation from the expected result. Defect: Problem in algorithm leads to
failure.
A Mistake in code is called Error.

Due to Error in coding, test engineers are getting mismatches in application is called
defect.
If defect accepted by development team to solve is called Bug.
27. What is hot fix?
A: A hot fix is a single, cumulative package that includes one or more files that are
used to address a problem in a software product. Typically, hot fixes are made to address
a specific customer situation and may not be distributed outside the customer
organization.
Bug found at the customer place which has high priority.
28. What is the difference between functional test cases and compatibility test cases?
A: There are no Test Cases for Compatibility Testing; in Compatibility Testing we are
Testing an application in different Hardware and software. If it is wrong plz let me know.
29. What is Acid Testing??
A: ACID Means:
ACID testing is related to testing a transaction.
A-Atomicity
C-Consistent
I-Isolation
D-Durable
Mostly this will be done database testing.
30. What is the main use of preparing a traceability matrix?
A: To Cross verify the prepared test cases and test scripts with user requirements.
To monitor the changes, enhance occurred during the development of the project.
Traceability matrix is prepared in order to cross check the test cases designed against
each requirement, hence giving an opportunity to verify that all the requirements are
covered in testing the application.
31. If we have no SRS, BRS but we have test cases does u execute the test cases
blindly or do u follow any other process?
A: Test case would have detail steps of what the application is supposed to do. SO
1) Functionality of application is known.
2) In addition you can refer to Backend, I mean look into the Database. To gain more
knowledge of the application
32. How to execute test case?
A: There are two ways:

1. Manual Runner Tool for manual execution and updating of test status.
2. Automated test case execution by specifying Host name and other automation
pertaining details.
33. Difference between re testing and regression testing?
A: Retesting:
Re-execution of test cases on same application build with different input values is
retesting.
Regression Testing:
Re-execution of test cases on modifies form of build is called regression testing
34. What is the difference between bug log and defect tracking?
A; Bug log is a document which maintains the information of the bug where as bug
tracking is the process.
35. Who will change the Bug Status as Differed?
A: Bug will be in open status while developer is working on it Fixed after developer
completes his work if it is not fixed properly the tester puts it in reopen After fixing the
bug properly it is in closed state.
Developer
36. wht is smoke testing and user interface testing ? ST:
Smoke testing is non-exhaustive software testing, as pertaining that the most crucial
functions of a program work, but not bothering with finer details. The term comes to
software testing from a similarly basic type of hardware testing.
UIT:
I did a bit or R n D on this. some says its nothing but Usability testing. Testing to
determine the ease with which a user can learn to operate, input, and interpret outputs of a
system or component.
Smoke testing is nothing but to check whether basic functionality of the build is stable or
not?
I.e. if it possesses 70% of the functionality we say build is stable.
User interface testing: We check all the fields whether they are existing or not as per the
format we check spelling graphic font sizes everything in the window present or not|
37. what is bug, deffect, issue, error?
A: Bug: Bug is identified by the tester.
Defect: Whenever the project is received for the analysis phase ,may be some

requirement miss to get or understand most of the time Defect itself come with the
project (when it comes).
Issue: Client site error most of the time.
Error: When anything is happened wrong in the project from the development side i.e.
called as the error, most of the time this knows by the developer.
Bug: a fault or defect in a system or machine
Defect: an imperfection in a device or machine;
Issue: An issue is a major problem that will impede the progress of the project and cannot
be resolved by the project manager and project team without outside help
Error:
Error is the deviation of a measurement, observation, or calculation from the truth
38. What is the diff b/w functional testing and integration testing?
A: functional testing is testing the whole functionality of the system or the application
whether it is meeting the functional specifications
Integration testing means testing the functionality of integrated module when two
individual modules are integrated for this we use top-down approach and bottom up
approach
39. what type of testing u perform in organization while u do System Testing, give
clearly?
Functional testing
User interface testing
Usability testing
Compatibility testing
Model based testing
Error exit testing
User help testing
Security testing
Capacity testing
Performance testing
Sanity testing
Regression testing
Reliability testing
Recovery testing
Installation testing
Maintenance testing
Accessibility testing, including compliance with:
Americans with Disabilities Act of 1990
Section 508 Amendment to the Rehabilitation Act of 1973

Web Accessibility Initiative (WAI) of the World Wide Web

Consortium (W3C)
40. What is the main use of preparing Traceability matrix and explain the real time
usage? A traceability matrix is created by associating requirements with the work
products that satisfy them. Tests are associated with the requirements on which they are
based and the product tested to meet the requirement.
A traceability matrix is a report from the requirements database or repository.
41. How can u do the following 1) Usability testing 2) scalability Testing
UT:
Testing the ease with which users can learn and use a product.
ST:
Its a Web Testing defn.allows web site capability improvement.
PT:
Testing to determine whether the system/software meets the specified portability
requirements.
42. What does u mean by Positive and Negative testing & what is the diffs between
them. Can anyone explain with an example?
A: Positive Testing: Testing the application functionality with valid inputs and
verifying that output is correct
Negative testing: Testing the application functionality with invalid inputs and verifying
the output.
Difference is nothing but how the application behaves when we enter some invalid inputs
suppose if it accepts invalid input the application
Functionality is wrong
Positive test: testing aimed to show that s/w work i.e. with valid inputs. This is also called
as test to pass
Negative testing: testing aimed at showing s/w doesnt work. Which is also know as test
to fail BVA is the best example of -ve testing.
43. what is change request, how u use it?
A: Change Request is a attribute or part of Defect Life Cycle.
Now when u as a tester finds a defect n report to ur DLhe in turn informs the
Development Team.
The DT says its not a defect its an extra implementation or says not part of reqment. Its
newscast has to pay.

Here the status in ur defect report would be Change Request

I think change request controlled by change request control board (CCB). If any changes
required by client after we start the project, it has to come thru that CCB and they have to
approve it. CCB got full rights to accept or reject based on the project schedule and cost.
44. What is risk analysis, what type of risk analysis u did in u r project?
A: Risk Analysis:
A systematic use of available information to determine how often specified events and
unspecified events may occur and the magnitude of their likely consequences
OR
procedure to identify threats & vulnerabilities, analyze them to ascertain the exposures,
and highlight how the impact can be eliminated or reduced
Types :
1.QUANTITATIVE RISK ANALYSIS
2.QUALITATIVE RISK ANALYSIS
45. What is API ?
A: Application program interface

46. High severity, low priority bug?

A: A page is rarely accessed, or some activity is performed rarely but that thing
outputs some important Data incorrectly, or corrupts the data, this will be a bug of H
severity L priority
47. If project wants to release in 3months what type of Risk analysis u do in Test
plan?
A: Use risk analysis to determine where testing should be focused. Since its rarely
possible to test every possible aspect of an application, every possible combination of
events, every dependency, or everything that could go wrong, risk analysis is appropriate
to most software development projects. This requires judgment skills, common sense, and
experience. (If warranted, formal methods are also available.) Considerations can
include:
Which functionality is most important to the projects intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?
What kinds of problems would cause the worst publicity?
What kinds of problems would cause the most customer service complaints?
What kinds of tests could easily cover multiple functionalities?
Which tests will have the best high-risk-coverage to time-required ratio
48. Test cases for IE 6.0 ?
A: Test cases for IE 6.0 i.e Internet Explorer 6.0:
1)First I go for the Installation side, means that
+ is it working with all versions of Windows ,Netscape or other softwares in other words
we can say that IE must check with all hardware and software parts.
2) Secondly go for the Text Part means that all the Text part appears in frequent and
smooth manner.
3) Thirdly go for the Images Part means that all the Images appears in frequent and
smooth manner.
4) URL must run in a better way.
5) Suppose Some other language used on it then URL take the Other Characters, Other

than Normal Characters.

6)Is it working with Cookies frequently or not.
7) Is it Concerning with different script like JScript and VBScript.
HTML Code work on that or not.
9) Troubleshooting works or not.
10) All the Tool bars are work with it or not.
11) If Page has Some Links, than how much is the Max and Min Limit for that.
12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled .
13) Is it working with the Uninstallation Process.
14) Last but not the least test for the Security System for the IE 6.0
49. Where you involve in testing life cycle ,what type of test you perform ?
A: Generally test engineers involved from entire test life cycle i.e, test plan, test case
preparation, execution, reporting. Generally system testing, regression testing, adhoc
testing
etc.
50. what is Testing environment in your company ,means hwo testing process start ?
A: testing process is going as follows
quality assurance unit
quality assurance manager
testlead
test engineer
51. who prepares the use cases?
A: In Any company except the small company Business analyst prepares the use cases
But in small company Business analyst prepares along with team lead
52. What methodologies have you used to develop test cases?
A: generally test engineers uses 4 types of methodologies
1. Boundary value analysis
2.Equivalence partition
3.Error guessing
4.cause effect graphing
53. Why we call it as a regression test nor retest?
A: If we test whether defect is closed or not i.e Retesting But here we are checking the
impact also regression means repeated times
54. Is automated testing better than manual testing. If so, why?

A: Automated testing and manual testing have advantages as well as disadvantages

Advantages: It increase the efficiency of testing process speed in process
reliable
Flexible
disadvantages
Tools should have compatibility with our development or deployment tools needs lot of
time initially If the requirements are changing continuously Automation is not suitable
Manual: If the requirements are changing continuously Manual is suitable Once the build
is stable with manual testing then only we go 4 automation
Disadvantages:
It needs lot of time
We can not do some type of testing manually
E.g Performances
55. what is the exact difference between a product and a project.give an example ?
A: Project Developed for particular client requirements are defined by client Product
developed for market Requirements are defined by company itself by conducting market
survey
Example
Project: the shirt which we are interested stitching with tailor as per our specifications is
project
Product: Example is Ready made Shirt where the particular company will imagine
particular measurements they made the product
Mainframes is a product
Product has many mo of versions
but project has fewer versions i.e depends upon change request and enhancements
56. Define Brain Stromming and Cause Effect Graphing? With Eg?
A: BS:
A learning technique involving open group discussion intended to expand the range of
available ideas
OR
A meeting to generate creative ideas. At PEPSI Advertising, daily, weekly and bi-monthly
brainstorming sessions are held by various work groups within the firm. Our monthly IPower brainstorming meeting is attended by the entire agency staff.
OR
Brainstorming is a highly structured process to help generate ideas. It is based on the
principle that you cannot generate and evaluate ideas at the same time. To use
brainstorming, you must first gain agreement from the group to try brainstorming for a
fixed interval (eg six minutes).
CEG :
A testing technique that aids in selecting, in a systematic way, a high-yield set of test

cases that logically relates causes to effects to produce test cases. It has a beneficial side
effect in pointing out incompleteness and ambiguities in specifications.
57. Actually by using severity u should know which one u need to solve so what is
the need of priority?
A: I guess severity reflects the seriousness of the bug where as priority refers to which
bug should rectify first. of course if the severity is high the same case is with priority in
normal.
severity decided by the tester where as priority decided by developers. which one need to
solve first knows through priority not with severity. how serious of the bug knows
through
severity.
severity is nothing impact of that bug on the application. Priority is nothing but
importance to resolve the bug yeah of course by looking severity we can judge but
sometimes high severity bug doesnt have high priority At the same time High priority
bug dont have high severity
So we need both severity and priority
58. What do u do if the bug that u found is not accepted by the developer and he is
saying its not reproducible. Note:The developer is in the on site location ?
A: once again we will check that condition with all reasons. then we will attach screen
shots with strong reasons. then we will explain to the project manager and also explain to
the client when they contact us
Sometimes bug is not reproducible it is because of different environment suppose
development team using other environment and you are using different environment at
this situation there is chance of bug not reproducing. At this situation please check the
environment in the base line documents that is functional documents if the environment
which we r using is correct we will raise it as defect We will take screen shots and sends
them with test procedure also
59. what is the difference between three tier and two tier application?
A: Client server is a 2-tier application. In this, front end or client is connected to
Data base server through Data Source Name,front end is the monitoring level.
Web based architecture is a 3-tier application. In this, browser is connected to web server
through TCP/IP and web server is connected to Data base server,browser is the
monitoring level. In general, Black box testers are concentrating on monitoring level of
any type of application.

All the client server applications are 2 tier architectures.

Here in these architecture, all the Business Logic is stored in clients and Data is
stored in Servers. So if user request anything, business logic will b performed at client,
and the data is retrieved from Server(DB Server). Here the problem is, if any business
logic changes, then we
need to change the logic at each any every client. The best ex: is take a super market, i
have branches in the city. At each branch i have clients, so business logic is stored in
clients, but the actual data is store in servers.If assume i want to give some discount on
some items, so i
need to change the business logic. For this i need to goto each branch and need to change
the business logic at each client. This the disadvantage of Client/Server architecture.
So 3-tier architecture came into picture:
Here Business Logic is stored in one Server, and all the clients are dumb terminals. If
user requests anything the request first sent to server, the server will bring the data from
DB Sever and send it to clients. This is the flow for 3-tier architecture.
Assume for the above. Ex. if i want to give some discount, all my business logic is there
in Server. So i need to change at one place, not at each client. This is the main advantage
of 3-tier architecture.
60. What is Impact analysis? How to do impact analysis in yr project?
A: Impact analysis means when we r doing regressing testing at that time we r
checking that the bug fixes r working properly, and by fixing these bug other components
are working as per their requirements r they got disturbed.
61. HOW TO TEST A WEBSITE BY MANUAL TESTING?
A: Web Testing
During testing the websites the following scenarios should be considered.
Functionality
Performance
Usability
Server side interface
Client side compatibility
Security
Functionality:
In testing the functionality of the web sites the following should be tested.
Links
Internal links
External links
Mail links
Broken links

Forms
Field validation
Functional chart
Error message for wrong input
Optional and mandatory fields
Database
Testing will be done on the database integrity.
Cookies
Testing will be done on the client system side, on the temporary internet files.
Performance:
Performance testing can be applied to understand the web sites scalability, or to
benchmark the performance in the environment of third party products such as servers
and middle ware for potential purchase.
Connection speed:
Tested over various Networks like Dial up, ISDN etc
Load
What is the no. of users per time?
Check for peak loads & how system behaves.
Large amount of data accessed by user.
Stress
Continuous load
Performance of memory, cpu, file handling etc.
Usability :
Usability testing is the process by which the human-computer interaction characteristics
of a system are measured, and weaknesses are identified for correction. Usability can be
defined as the degree to which a given piece of software assists the person sitting at the
keyboard to accomplish a task, as opposed to becoming an additional impediment to such
accomplishment. The broad goal of usable systems is often assessed using several
Criteria:
Ease of learning
Navigation
Subjective user satisfaction
General appearance
Server side interface:
In web testing the server side interface should be tested.
This is done by Verify that communication is done properly.
Compatibility of server with software, hardware, network and database should be tested.
The client side compatibility is also tested in various platforms, using various browsers
etc.

Security:
The primary reason for testing the security of an web is to identify potential
vulnerabilities and subsequently repair them.
The following types of testing are described in this section:
Network Scanning
Vulnerability Scanning
Password Cracking
Log Review
Integrity Checkers
Virus Detection
Performance Testing
Performance testing is a rigorous usability evaluation of a working system under realistic
conditions to identify usability problems and to compare measures such as success
rate, task time and user satisfaction with requirements. The goal of performance testing is
not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression
testing.
To conduct performance testing is to engage in a carefully controlled process of
measurement and analysis. Ideally, the software under test is already stable enough so
that this process can proceed smoothly. A clearly defined set of expectations is essential
for meaningful performance testing.
For example, for a Web application, you need to know at least two things:
expected load in terms of concurrent users or HTTP connections
acceptable response time
Load testing:
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
Examples of volume testing:
testing a word processor by editing a very large document
testing a printer by sending it a very large job
testing a mail server with thousands of users mailboxes
Examples of longevity/endurance testing:
testing a client-server application by running the client in a loop against the server over
an extended period of time
Goals of load testing:
Expose bugs that do not surface in cursory testing, such as memory management bugs,
memory leaks, buffer overflows, etc. Ensure that the application meets the performance
baseline established during Performance testing. This is done by running regression tests
against the application at a specified maximum load.
Although performance testing and load testing can seen similar, their goals are different.
On one hand, performance testing uses load testing techniques and tools for measurement
and benchmarking purposes and uses various load levels whereas load testing operates at

a predefined load level, the highest load that the system can accept while still functioning
properly.
Stress testing:
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.
Stress testing tries to break the system under test by overwhelming its resources or by
taking resources away from it (in which case it is sometimes called negative testing).
The main purpose behind this madness is to make sure that the system fails and recovers
gracefully this quality is known as recoverability.
Stress testing does not break the system but instead it allows observing how the system
reacts to failure. Stress testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail gracefully?
Is it able to recover from the last good state on restart?
Etc.
Compatability Testing
A Testing to ensure compatibility of an application or Web site with different browsers,
OS and hardware platforms. Different versions, configurations, display resolutions, and
Internet connect speeds all can impact the behavior of the product and introduce costly
and embarrassing bugs. We test for compatibility using real test environments. That is
testing how will the system performs in the particular software, hardware or network
environment. Compatibility testing can be performed manually or can be driven by an
automated functional or reg The purpose of compatibility testing is to reveal issues
related to the product& interaction session test suite.with other software as well as
hardware. The product compatibility is evaluated by first identifying the
hardware/software/browser components that the product is designed to support. Then a
hardware/software/browser matrix is designed that indicates the configurations on which
the product will be tested. Then, with input from the client, a testing script is designed
that will be sufficient to evaluate compatibility between the product and the
hardware/software/browser matrix. Finally, the script is executed against the matrix,and
any anomalies are investigated to determine exactly where the incompatibility lies.
Some typical compatibility tests include testing your application:
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip drives, USBs, etc.)

66. After insert the record in front-end, How will u check the back end by manually?
Please explain?
Back end Checking is what we call DATABASE TESTING have to know the queries
very well. With out queries we will not able to test data base testing. But as a tester we
will responsible for test and see the data whether it is stored in back end or not. We dont
have permission to do any thing. So what I am coming to tell means select * from
condition queries is enough for testing the back end.
67. Do write a separate test case for Regression Testing? If it is Yes, Explain How to
write the Test case?
Well we are not going to right separate test cases for regression testing. We execute the
same test cases on newly modified build which ever failed in previous.
OR
We are not going to write new test cases. We will select the some of the test cases from
test case document, and execute the test cases to check for the bug fixes. Here we
selecting the test cases such way that, all the basic functionality test cases, and affected
bug test cases.
68. How to do the performance testing manually? Does u have a test case for that?
We can test it manually but we dont get accurate result. We dont have separate test cases
exactly we will do it with tool i.e. Load runner, Act, Web load.
69. What is the difference between Functional testing and Functionality testing?
Functional Testing:
The portion of security testing in which the advertised features of a system are tested for
correct operation.
OR
Quality assurance that a web site performs properly. All aspects of the user interface,
navigation between pages and off-site, multilingual navigation, etc. are tested. Testing is
required in all the current browsers and on the major operating systems and platforms.
OR
Functional testing is nothing but whether the given function is working or not as per the
specifications
Ex: field validation, Navigation etc.

Functionality Testing is nothing but to check whether our application is equal to customer
requirements or not
Here we will do lot more tests
Ex: Inter system Testing
Error handling testing
70. What is Middleware? Can anybody explain me?
In the computer industry, middleware is a general term for any programming that serves
to glue together or mediate between two separate and often already existing programs.
A common application of middleware is to allow programs written for access to a
particular database to access other databases. The systematic tying together of disparate
applications, often through the use of middleware, is known as enterprise application
integration.
Or
Software that mediates between an applications program and a network. It manages the
interaction between disparate applications across the heterogeneous computing platforms.
The Object Request Broker (ORB), software that manages communication between
objects, is an example of a
middleware program
71. Suppose u and your team member is there.your team member (friend) has raised
one bug..u dont no about application as well as that functionality of that
application.your TL give the task u have to give the Severity & Priority..how can u
give the Severity & Priority?
I am using Adhoc testing for this type of bugs depends upon past experience i am try to
execute the testcase and write the severity and priority of that big.
72. what is JOINTS & REGISTRY in SQL?
Joints : Using SQL Joints, you can retrieve data more than one table or view using the
keys etc to define an inequality condition
Registry : A Windows repository that stores configuration information for a computer.
For all the terms on SQL Plz Visit
http://www.utexas.edu/its/unix/reference/oracledocs/v92/B105
01_01/win.920/a95490/glossary.htm

73. suppose u have raised one bug.u have posted to that concerned developer..he
cant accept that is a bug.what will u do in the next stage?
If the developer wont accept our sent bug, then we show it to our team leader or we can
show it to our superior person. so he/she will go and discuss with developer or else they
will conduct one meeting on that.
or
Sometimes bug not reproducible in Dev Environment at that situation dev doesnt accept
we will give him screen shots.If still debate occurs we raise the issue in bug triage
meeting
74. Role of Software Test Engineer in Software Company?
The role of a software test engineer in company is to find the defect. He/She should have
test-to-break attitude. He/She has to test the application taking the customer into mind.
He should work hard for quality.
75. Suppose you testing Calculator application and you got problems like 1/1=2,
2/2=1, 3/3=6, 4/4=1, 5/5=10. Now how will you describe the bug title as well as give
the bug description?
Bug title : Calculation Errors
Description: Unable to do the calculations of this application.like the output is giving an
undefined/Unstructured format.
Here the examples :
1/1=2
Severity : Critical
Priority: High/Medium(depends on your Requirement to solve)
Bug Title:calculator_functionality_Division
Description:Division function is not working properly when the values are(both) same
and even.
76. Explain equivalence partitioning with an example?
When We have an requirement which has a large class of data split the large class into its
subsets
For Ex:
Sal 10000-45000
Here this is the large class of data equivalence partitioning >take inputs from the below
sub

classes such as
less than 10000 (invalid)
between 10000 and 45000 (valid)
greater than 45000 (invalid)
Instead of choosing values from the large set of information split the inputs into both
valid & negative inputs that becomes a subset. this technique is equivalence partitioning
77. Explain traceability matrix with an example?
Traceability matrix is table which maps each requirement to its functionality in FDS, its
internal design in IDS, its code and its test cases.
Format is
<! /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-styleparent:"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; fontsize:12.0pt; font-family:Times New Roman; mso-fareast-font-family:Times New
Roman;} pre {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; fontsize:10.0pt; font-family:Courier New; mso-fareast-font-family:Times New Roman;}
@page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-headermargin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1
{page:Section1;} >
Requirement--Functionality--Internal design--coding--T.c's
R1
P3 in FDS
P6 in IDS
P4
T13,T14
-

78. What is the difference between Integration Testing and System Testing?
Integration testing will do the completion of unit or module level Testing.
System testing is nothing but the application meets the Required specifications or not
Or
In integration testing individual components are combined with other components to
make sure the necessary communications, links and data sharing occur properly.
It is not system testing because the components are not implemented in the operating
environment.
System testing begins one the modules are integrated enough to perform tests in whole
system environment.System testing can occur in parallel with integration test, especially
with the top-down method.
79. How Could u Present Test Strategy for the Product Testing?

Test strategy means that it is a document prepared by quality analyst/project manager. it

specifies how to approach to testing team depends upon requirement gatherings, risks
involved in our company and customer requirements
80. You may undergone many projects. Do all the projects match up with customers
expectations?
Any project never matches with 100% requirements. We consider only when it reaches to
certain extent
81. On what basis you are fixing up the time for project completion?
Test strategy; Based on the test strategy and testing Approach
82. How u r breaking down the project among team members? It can be depend on
these following cases1) Number of modules
2) Number of team members
3) Complexity of the Project
4) Time Duration of the project
5) Team members experience
etc
83. Usually customers wont give all the requirements. How will u manage & collect
all the necessary information?
Sometimes customer may not produce all the requirements. At this situation Business
analyst and project manager will use their experience which they handles this type of
projects otherwise we will go through some reference sites where we will observe the
functionality and they will prepare use cases and requirements.
or
I am agree with the above answer.
If we really face such a problem then it is better to get information from development
team so that we can know the exact info Or else use Ad-hoc testing for the required job.
84. what are the Qualities needed by a software tester?
A software tester must have intent of showing the product is not working as specified.
Software tester have the basic attitude of showing the presence of errors. He must have
perspective of customers i.e he has to use the system as he is the client of the system. He
has to strive for the quality.
Or

Software Tester must has these qualities

1)He/she must observe the problem from both the side say user and programmer.
2)Must has good under standing with other team members .
3)Able to understand programmers view.
4)Once start testing, do not put it remain.
5)First test requirements of the user.
6)Before start testing first analysis the project like ;
technology using in project, all the flow etc
85. Did you write test cases of design phase?
Yes We can write test cases at the design phase
At the time of designing we should be ready with test cases
86. In Testing 10 cases you found 20 bugs then how will you know which bug is for
which test case?
Each Bug Will Have a Unique Bug-ID which would be related to that particular Test
Case. We also make use of the Matrix to keep track of bugs and test cases.
87. what is the path for test director,where the test cases are stored ?
c:\TDcomdir\TD_projectname\tests\test no
Usually test cases are stored in Test Plan in Test director
88. what is mean by test suite?
Test suit is set of test cases Group of test cases is nothing but functional(+ve & -ve)
and GUI
89. What is the diff. b/w Baseline and Traceability matrix?
Baseline : The point at which some deliverable produced during the software engineering
process is put under formal change control
Traceability : Is used to check if some of the test cases are left out or not in Manual and
automated testing.
Baseline is nothing but a software specification or functionality that is reviewed or
accepted for development. Once the functionality is baseline, we can start developing of
the functionality.
Where as a Traceability Matrix lists all the functionality or features and the test cases for
each feature. By using the traceability matrix we can measure, when to stop testing of the

project or application.
Generally Traceability Matrix contains:
1. UseCaseID(Functionality/Feature).
2. Description of the Feature.
3. Priority for the Feature.
4. TestCaseIDs for this Feature. (Once if the mapped testcases for each Feature meets
Success criteria, then we can stop testing of the project)
5. In which phase is the Feature (Unit,Component,Integration,System)
90. what methodologies you are following?
Methodologies are considered in 2 accounts.
1) There are a few methodologies like : v-model,spiral (most common), waterfall, hybrid,
prototype, etc depends on the company.
2) Depends on the clients and the requirements.
No. 2 is def related to no 1
Methodology means the way we are following while writing test cases . there are
different ways like
1. Functional Test cases
2. Equivalence Partitioning Test cases
3. Boundary value analysis
4. Cause Effect Graphing and Decision table
91. Can u test a website or a web application manually without using any
automation tool?
As per my idea we can test a web application manually without using automation but its
time consuming and might have error so to make our task easy and error free we use
automatons tool like Qtp. As for as Manual is concerned we can test Usability,
Functionality, Security testing but whereas
performance is concerned we cant do it manually accurate
92. What tools are used in Manual testing for bug tracking and reporting?
For bug tracking and reporting there are many tools like
Rational clear quest.
PVCS
Bugzilla
93. At what stage in the SDLC testing should be started?

Testing Starts from the starting sate of SDLC that is requirement stage where we prepare
SRS Or URS DOC.
94. What is mean by designing the application and coding the application?
Designing and Testing are two different phases in a software development
process(SDLC).
1. Information Gathering
2. Analysis
3. Designing
4. Coding
5. Testing
6. Implementation and Maintenance.
If u want answer in Testing terms means STLC, designing test includes preparing Test
Strategy, Test Plan and Test Case documents, and testing means executing the test cases
and generating Test Reports.
Designing the application as per the requirements Designing the application is nothing
but deriving the
functional flow , alternative flow,How many modules that we are handling, data flow etc
Two types of designs are there
HLD:
In this designing team will prepare functional architecture i.e Functional flow
LLD:
In this designing team will divide the total application into modules and they will derive
logic for each
module Coding:writing the course code as per the LLD to meet customer requirements
95. what is mean by client and server?
96. I. A code inspection is held for new code. II. A code inspection is held for reused
code. III. A code inspection is held after the first compilation. IV. A code inspection is
held after the first error-free compilation. Which of the statements above are true of
code inspections?
1. I and IV 2. I, II, and IV 3. I, II, and III 4. II and IV 5. II and III?
1. I and IV
96. What is the best way to choose automation tool?

We use automation only for version wised projects, means if the project comes up with
different versions. Once we write the scripts for one version, we can use these scripts
with multiple versions with minor changes. So the main advantage of automation is:
1. Saves the time.
2. Saves money.
97. What is the point of reference by which something can be measured?
1. Benchmark 2. Baseline 3. Metric 4. Measure 5. Indicator
Baseline
98. what is Concurrency Testing?
Multi-user testing geared towards determining the effects of accessing the same
application code, module or database records. Identifies and measures the level of
locking, deadlocking and use of single-threaded code and locking semaphores.
99. When does metrics validation occur? 1. Throughout the life cycle 2. During the
test 3. After the test 4. During requirements definition 5. After the final software
release Justify your answer with simple explanation.?
Throughout the life cycle - TO identify the lag & overcome
100. The scenario is while reviewing requirement docs(SRS)if u find or feel any
requirement is not meeting the clients requirements whom do you report?and
what is your action?
When the System Requirement Specification does not meet the clients requirements, it
should be intimated to the PL (who prepares the SRS and should be documented in the
Test log & analysis of data which should be discussed in the Management Review
Meeting. The action is the SRS should undergo a revision thereby updating SRS to match
with CRS
101. How to choose a test automation tool?We have to choose depends upon the
application complexity & delivery time.
102. Did u come across STUBS and DRIVERS? How did u use these in u r project ?
Stub : A piece of code that simulates the activity of missing components.
Driver : A piece of code that passes test cases to another piece of code.
i will give a gen example.suppose u have 3 modulesA B CA n B r 100%
comp.and C is only 50% comp.u r under pressure to comp in a time framewhat u
do is u know to build the mod C u need at least 15 daysso u build a dummy mod C

which will take 1/2 daysThis is STUB now once all the mod A B and C(dummy) r
ready..u integrate them to see how it works..This is a DRIVER