Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Q A Testing

Q A Testing

Ratings: (0)|Views: 94|Likes:
Published by api-3701809
Q A Testing Lab
Q A Testing Lab

More info:

Published by: api-3701809 on Oct 17, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





1. What is bug tracking tool ?
A tool used to track the defect/issues/concerns logged by tester. This is very much required in any testing
environment. Some common features of any bug tracking tool allow you to prioritize the defects, keep track of
bug status (like open/close/verified) ,date logged etc..
This is also a Software Application that helps the Test team in end-to-end Defect Life Cycle Management. The
advantage of this tool is that all the stake holders of the Testing Project can keep track of the latest Status of all
the Bugs logged in by the Test team.
Also, it will be help in the following:

1. Defect Categorization based on Priority, Severity.
2. Generating a variety of Bug reports such as Daily & Weekly and also Application wise and Module wise Bug lists.
3. Also the tool can be configured for sending automated mail messages to all the concerned people whenever a
Bug is logged in the tool and change occurs to the same.
4. Some tools have more features such as generating Graphical reports based on the Bug Data.

2. What is the difference between verification and Validation in software testing
Verification ensures the product is designed to deliver all functionality to the customer; it typically involves
reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done
with checklists, issues lists, and walkthroughs and inspection meetings.

Validation ensures that functionality, as defined in requirements, is the intended behavior of the product;
validation typically involves actual testing and takes place after verifications are completed
Verification is a process in which information is checked using accurate measures. E.g. when you enter a new
password you are asked to retype it to verify that the password supplied is correct.
Validation however is the automatic process in which rules are applied in order to make information correct,
e.g., if the right type of data is entered in a certain cell in a database.

3. What do u mean by Testing plan in software development life...
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. The completed document will help people outside the test
group understand the 'why' and 'how' of product validation
For a application or product to be success....testing phase or plan is a must.
Testing plan explains the scope of testing, Objectives, Test strategies (what are the kind of testing to be
conducted to find the bugs), Acceptance Criteria(At what point the testing should be stopped to adhere for the
bugs) and test case procedure which explains how the testing should be conducted.

"All the above put together makes a testing plan"
Test Plan is a roadmap to achieve your testing activity. i.e., what are the process that u are going to follow in ur

4. How do I test web-related applications?
First u have to test
web tier testing
1.browser compatible
2.compatible testing.
middle tier testing
1.security testing
2.performence testing
database tier
1.data integrity

web testing is done in three tiers
1. First tier of testing check is on look and feel, colors, fonts, everything.
2. Second tier comes database testing, performance testing
3.third tier comes security like network
security, transaction security
all other tests which are common for all

5.stress testing?
Just try some extreme conditions for your system : unplug the net cable, shut down the DB Server, kill a running
process of the system,.
Stress testing is subjecting the system under
heavy load but, denying the required resources for the system to perform (like RAM, Disc. etc).
Even if the system fails, it is not cause of worry.
The Idea is basically to confirm that the system does not fail in Improper manner.
The system should not Corrupt the data / Lose the existing data when it Fails.

Stress Testing is nothing but testing the software/product with resources.
That is Stress testing is a type of software Testing where we test the software with minimum and Maximum
Here we reduce the software Resources.
For Ex:
One software is recommended condition is 64 MB RAM.
For this software we will run it is 32 MB RAM, in this environment software should run. IT shouldn't crash the
system, it should have a Graceful exit.

6. What is stub & driver in integration testing?
Stub is a piece of code emulating a called function, a driver is a piece of code emulating a calling function
Stub: A piece of code that simulates the activity of missing component.
Driver: A piece of code that passes test case to another piece of code.

7.What is BVT in Testing field?
BVT is nothing but a build verification Test and will be done , after the integration of all modules/components
with the corresponding backend has been completed taken from the repository using some perl
scripts(usually).Also it can be considered to be given for alpha/beta testing.

8. Difference between load and stress testing
Load testing is stressing within maximum limits - focus is on Performance Criteria..

Stress testing is stressing beyond maximum limits - focus is to know failure behavior of the system.
Load Testing is a process to check where exactly the system/server starts to degrade.
Stress testing is negative testing. E.g., if a system can response properly for say 100 users. Bulk of users will be
accessed to check the systems performance, there by reducing the no. of users if the system degrades.

9.Exact difference bet Bug, Error & Defect?

Error: Is an undesirable deviation from requirements
Bug: Is an error found BEFORE the application goes into production
Defect: Is an error found AFTER the application goes into production

Error: Deviation for actual and the expected/theoretical value.
Bug : An Error found in the development environment before the product is shipped to the customer .
Defect : An Error found in the product itself after it is shipped to the customer .
10.What weaknesses within a computer network can have direct effect on the functionality of the system

The weakness may be from server to installation and unavalaiability and inability to retrieve the required
data or files to the system

11.What is Testing? What is Test Plan? What is Test case?
Testing: Executeing a program with a intent of finding bugs.
TestPlan: It is a roadmap for testing the system
Testcase:To check the behaviour of particular attidue

test plan: A record of the test planning process detailing the degree of tester indedendence, the test
environment, the test case design techniques and test measurement techniques to be used, and the rationale for
their choice.

test case: A set of inputs, execution preconditions, and expected outcomes developed for a particular objective,
such as to exercise a particular program path or to verify compliance with a specific requirement. After

Activity (6)

You've already reviewed this. Edit your review.
1 hundred reads
johnsonkk125 liked this
reachyudi liked this
snancyg1985 liked this
Sabu John liked this
Sabu John liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->