How to create a load manualy in web based testing

Question Posted / singhmanish79

1 Answers
4096 Views
NetSity, I also Faced
E-Mail Answers

How to create a load manualy in web based testing..

Explain me about test scenarios? How will you write it?
Answer
# 2 Test scenarios are generally the paths which cover whole
application. Mainly these are generated on the basis of Use
cases . then test cases are generated on the basis of test
scenarios.

What is the difference b/w Smoke and Sanity Testing? I heard
that Sanity testing will be done by developers. Is that so?
Answer
SMOKE Testing - When a tester get build from the Dev,
tester perform the initial testing to ensure that the basic
functionality is working fine or not. If not then further
detail testing is not proceeded. This initial testing
before the detail testing is known as SMOKE testing.

Sanity Testing - Once the all the test cycles have been
executed and all the open defects have been fixed and
retested, now before providing the signoff for next phase
testers needs to do Sanity testing to test some critical
functionality which will ensure that the defect fixes have
not disturb the other functionality. This test cycle is
short and quick and is known as Sanity testing.

Low Severity and High Priority:

When there is a spelling mistake in a Login page i.e for
example The company logos such as SATYAM is spelled as
SAYAM in the front page of the application. This is treated
as a Low severity and High priority.
(or)

Banking application:
in some situations customer will not get confirmation
message even though the process is going on smoothly at
backend.

Medium Sev and Medium Priority:

When there are mistakes in Error messages or warning
messages.

High severity and Low priority:

Suppose as per clients req ur application should work on
Both IE 5.5 and IE 6.0. But it is working fine with IE 6.0
and not working with IE 5.5.
Hence it is not meeting the req it is high sev and hence
it's functionality is working fine but can fix it at any
time so of low priority.

REGRESSINON

Whenever enhancements added to the existing functionality
then only we go for Regression testing because ensure that
the new
changes are whether effecting the old functionality or not

what is test log? tell the process?
Answer
# 4 test log is nothing but the what are test cases we r
executed.
the pass/fail criteria of that testcases

Re: Difference btween the QA and QC?
Answer
# 3 ________________________________________
Quality Assurance
Preventing problems
Prepare Standards and Guidelines
Review the reports
Prepare the test plans
Verification

Quality Control
Identify problems
Implement Standards and Guidelines
Prepare the reports
Implement the test plans
Validation

What is metrics? explian the type of metrices.
Answer
# 3 Metrics are generally classified into 2 types
1. Process metrics
2. Product metrics
b a metric used to measure the haracteristic of the
methods, techniques and tools employed in eveloping,
implementing and maintaining the software system.

Product metric: a metric used to measure the characteristic
of the documentation and code. The metrics for the test
process would include status of test activities against the
plan, test coverage achieved so far, amongst others. An
important metric is the number ofdefects found in internal
testing compared to the defect found in customer tests,
which indicate the effectiveness of the test process itself.

e: What is testing life Cycle and Explain different phases?
Answer
# 1 1.Testing Requirement: Gather all type of requirements and
scope of the application fro SRS.
2.Testing Design: Writing test cases for each functionality
of the application provided in FS.
3.Test Execution: Executing all test cases to find if there
exists any bug.
4.Test Reporting: Analysis of the whole system testing
5.Test Deliverable: Test report has to be generated to
validate the system.

Re: What is reference matrix or tracability matrix?
Answer
# 7 We use tracebility Matrix to map the test cases with the
requirements. So that we ensure all the requirements are
covered in test cases. With the help of RTM we can measure
the potential risk.

Can any one explain me, What is Integration testing process?
Answer
# 7 INTEGRATION TESTING:
Definition: A process of testing the connectivity or data
transfer between the couple of unit tested modules.
THREE TYPES OF TESTING.
INCREMENTAL ---- Top-Down and Bottom-Up

BIGBANG ---- Bigbang

TOP-DOWN INCREMENTAL TESTING: A process of integrating
modules one by one using top-down approach.

Stubs (Top-down) : Temporary modules which are replacements
of the original components.

Process : Start integrating the module from top to bottom
and then do testing.

Phase of testing : After Unit Testing.

Automation : No, not needed.

BOTTOM-UP INCREMENTAL TESTING: A process of integrating
modules one by one using bottom-up approach.

Drivers (Bottom-Up) : Temporary modules which are
replacements of the original components.

Process : Start integrating the module from bottom to top
and then do testing.

Phase of testing : After Unit Testing.

Automation : No, not needed.

BIGBANG TESTING : A process of integrating all the modules
together at once.

Process : Start integrating all modules together and do
testing.

Phase of testing : After Unit Testing.

Automation : No, not needed.

What is a Test Strategy? What is d difference between a Test
Strategy and a Test Plan?
Answer
# 5 Test Strategy: This document is a organizational level
document and is prepared by the PM. This document contains
the details about the whole testing approach, methodologies
etc.

Test Plan: This document is prepated by the Test Lead. It
consists of the testing details i.e.
who is going to test
what would be environment
what is in scope of testing
delivery dates
risks and contingencies etc

what is the difference between test bed & test environment.
Answer
# 1 Test Bed :
An execution environment configured for testing. May
consist of specific hardware, OS, network topology,
configuration of the product under test, other application
or system software.

Test Environment :
The hardware and software environment in which tests will
be run, and any other software with which the software
under test interacts when under test including stubs and
test drivers.

Advantages and Dis-advantages of V-model?Is every company is
using V-model only? pls send me the answer very quick asap.
Answer
# 7 The advantages of V model are:
1) Time saving - This is because the Testing activities
start as soon as the customer gives the requirement
(parallal to the development activites)i.e. testing design
starts when requiremnts are given by customer meanwhile
developers start with coding and when the coding is
complete testing can immediately start without waste in
time for the design.
2) Cost Saving - V model is cost saving because there is
early detection of bugs while development and unit testing.

Now coming to the next part of question, All the companies
do not implement V Model. It depends on customer
requirement eg. if the customer is more interested to cover
up all risks then the company may use Spiral Model.

There are few disadvantages of V model:
1) Expensive
2) For BIG projects its a repeated process
Re: Iam new to Testing Field.How do i need to answer if
they ask like Integaration Testing? Can you give example
with your requirement?
Answer
# 3 Integration testing is a type of testing. When two or more
than two modules are integrated, then this tesing will be
done to check whether the flow of the data from one module
to other is proper or not.

This type of testing is not only done by the developer, but
also will be done by the person who is having the codng
knowledge.In this process stubs and drivers are used. They
are also calld as Called and calling programs.

There are two types of integration testing
1. Top-down integration
2. Bottom-up integration

What is the differencein validation & verification?? What we
exactly do in verification & validation ????? Give an
example....
Answer
# 1 Verrification is a process that whether we are building the
product right, i.e we have the equirement with us. whether
we are developing the product accordingly or not?

Validation is the process that whether we are building the
right product, i.e the product which we have developed is
right or not?

Verificaation involves collection of the requirements,
Analyse those requirements, Preparation of HLD and LLD.

Validation invoves unit,Integration,system and User
acceptance testing.

V Model is the best Example. left side of the V-Model is
verification and right side is the validation

Bug : Any discrepancy found during testing of software
product.

Defect: Any discrepancy found by the customer in the
software product after the release in to production

Error: Any discrepancy in the coding

# 3 Test Life Cycle:
Requirements Gathering--Test Plan Preparation--Test Cases
Preparation--Test Cases Execustion--Report Ananlysis--Bug
Ananlysis--Bug Reporting

Defect Life Cycle:
New--Open--Assign--Fixed/Deferred/Not a
bug/Later/WontFix/Duplicate--Test--Verified--Reopen/Close
What is security testing? How to test the web application
using security testing ?

Question Submitted By :: Anil Grandhi
I also faced this Question!! Rank Answer Posted By

Re: What is security testing? How to test the web
application using security testing ?
Answer
# 1 using three methods the sequerity is provided

1) Authorazation/Authentication
Allowing valid user and preventing invalid users.....

2) Access Control
Permission to valid user to access user
fctionalitites in software build.

3) Encryption/Dis\cryption
Data conversions in b/n client process and server
provcess to prevent third party avccessing

What is security testing? How to test the web application
using security testing ?
Answer
# 4 There is different type of methods are using for security
testing
1)Authorization and Authentication:For checking the valid
and invalid user.
2)Access Control:access permission to valid user to access
user functionalities in application.
3)Encryption and Decryption: Data conversions in between
client process and server process to prevent third party
accessing

The above techniques using for security testing for web
application

Re: What is Functional Testing?
Answer
# 3 functional testing means testing all the functionalities in
the application which can given by the client

Can anyone tell me testing comes under verification or
validation?
Answer
# 1 Verification is proving that a product meets the
requirements specified during previous activity carried out
correctly throughout development life cycle ,while
validation checks that the system meets the customer's
requirements at the end of the life cycle.
The creation of the test product is much more closely
relation to validation than to verification .
Traditionally software testing has been consider a
validation process.

Yes we will write regression test cases.... Regression is
nothing but when new functionality is added then we r doing
regression testing... so we r writing test cases for new
functionality and we will write test cases like P1 for
regression test

Explain Boundary value analysis, Equivalence partitoning and
Error guessing?
Answer
# 1 Boundary value analysis : Designing test cases at boundary
values. If field take values from 10 to 20 numbers,
following are the boundary values which is taken care while
doing testing.
Valid boundary values 10, 11, 19, 20
Invalid Boundary values 9, 21.

Equivalence partitioning : Designing test cases by deviding
the input values in to equivalence partitions.

valid Equivalence partitions 14 or 18
Invalid equivalence partitions 5, 26

Error guessing : From testers experience , are able to guess
where bug will come and in which scenario.

what is the defference between stress and load testing?
Answer
# 5 To test how much load is applied on Server/CPU and response
time of server for different configuration of load is known
as Performance testing. For conducting performance testing,
we use three techniques:

Load Testing : to check the performence of an application
based on increasing no.of vusers.

Stress Testing : to check the performence of an application
based on increasing no.of resources.

Performence Testing : To check whether our application is
giving response with in the expected time or not.

Volume Testing =
->Test a system against Large amounts of data.
->Oftenly related to Data base testing,No real users.

Load Testing =
->To determine @ which point of Time system degrades from
expected behaviour against a load.
->Large amount of users.
->Time constraints.
->Within the defined load limits.

Stress Testing =
->Too many users, too much data, too little time and too
little room.
->Test the system against increasing load.
->To find out @ which point of load system gets Crash or
Break down.

Re: Difference b/w test case and scenarios.
Answer
# 2 Test Scenario: Identifying the all possible areas to be
tested (What)

Test Case: describes an input action and expected result to
ensure that a certain feature works correctly as per the
specifications.

What is the Configuration Management?
Answer
# 2 Configuration Management is :
- The process of identifying & defining the configuration
items in a system,
- controlling the release and change of these items
throughtout the system life cycle,
- recording and reporting the status of configuration items
and change requests,
- and verifying the completeness and correctness of
configuration items.

What is the difference between bug,defect, error, failulre,
fault & mistake?
Answer
# 2 Bug: Error which appears during testing phase

Defect: Error that appears during development phase

Failure: When the result is not equal to actual result then
it is said to be Failure

Fault & Mistake: Errors which are made at that time and
recognised at that time itself

testing how well the system protect against unauthorized
internal or external aceess willfull damage etc

Retest

after fixes of defect doing testing that is Retesting

Regression
After Fixes and modification in the application finding the
impact of that fixed or modification in the application

Let me add few more points:
Desktop:
01. Application runs in single memory (Front end and Back
end in one place)
02. Single user only

Client/Server:
This type of testing usually done for 2 tier applications
01. Application runs in two or more machines
02. Application is a menu-driven
03. Connected mode (connection exists always until logout)
04. Limited number of users
05. Less number of network issues when compared to web app.

Web:
This is done for 3 tier applications
01. Application runs in two or more machines
02. URL-driven
03. Disconnected mode (state less)
04. Unlimited number of users
05. Many issues like hardware compatibility, browser
compatibility, version compatibility, security issues,
performance issues, etc
Regards,

Projects are broadly divided into two types of :
2 tier applications
3 tier applications
Client server testing:
It is 2-tier architecture and also called thick client.
Uses User interface as front end
uses database as backend.
Here there are no urls and hyperlinks it contain only forms.
Where as in web testing:
it is 3-tier or n-tier architecture.
It is also known as thin client.
Here there are so many URLs and hyperlinks.
it is internet based and there would be many servers between.

Client- server applications: Application is loaded at the
server. In every client machine, an exe is loaded to call
this application.

Web Based application : Application is loaded at the
server.but,No exe is installed at the client machine. We
have to call the application through browser.

Web Testing, you test the application with different
browsers and different versions of the same browsers. Here,
you would be concentrating on User Interface, Functionality
and Performance of the application. In Client Server
Testing, you don’t require any media/browser to test the
application.

A higher degree of Security, Performance and Reliability
testing is required for web based applications than client
server applications because web based applications are multi
user applications whereas client server applications are
single user applications.

If the database is changed in client server application, the
front end source code needs to be changed where as in web
based, if the database changes, only the middle-ware has to
be changed accordingly as client never interacts with the
server directly. The business logic is @ middle-ware in web
based application where as the same is at client in fat
client/thin server architecture and at server in thin
client/fat server architecture.

Client Server Testing:-

In client server testing test engineer are conduct the
following testings:-

1.Behaviour testing(GUI TESTING)

2.Input domain testing

3.Error Handling testing

4.Backend testing

In Web testing test engineer are condut the following
testings:-

1.Behaviour Testing

2.Static web testing

3.Input domain testing

4.Backend testing

5.Error handling testing

5.Frame Level testing

Re: What is stub and driver in integration testing ? Explain
with example. Answer
# 1
types of integeration testing:
top down
bottom up
Top down :
testing hierarchy starts from higher level
to lower level.if suppose testers dnt get the lower modules
for testing(consider the lower modules are under developmnt)
wat the testers wil do thy wil place dummy modules and
integerate these dummy modules with the higher level
modules.in top down apparoach the dummy modules r called
Stubs.
Stubs- Def
stubs r the dummy modules tht simulates the low
level modules.
Bottom up:
in this the dummy modules r called drivers.
Drivers- Def:
drivers r the dummy modules tht simulate the high
level modules.
. What is difference between a Test Plan, a Test Strategy, A
Test Scenario, and A Test Case ? What’s is their order of
succession in the STLC? Answer
# 2
The order in the STLC
1. Test Plan
2. Test Strategy
3. Test Scenario
4. Test Case

Test Plan: This document describes the different types of
testing that we follow in our testing cycle, along with the
exit and entry criteria, the deliverables at a high level and
defect management etc...

Test Strategy: This document gives the approch for testing.

Test Scenarios: It may contain high level flow of the
functionality later which this can be break down into n
number of test cases.

Test Cases: Test cases contain a detail level of
functionality check

: 6. What is difference between a Test Plan, a Test
Strategy, A Test Scenario, and A Test Case ? What’s is their
order of succession in the STLC? Answer
# 3
Test Plan : A document describing the scope, approach,
resources and Schedule of intended test activities. It
identifies amongst other test items, the features to be
tested , the testing tasks, who will do each task, degree
of tester independence, the test enviornment, the test
design techniques and entry and exit criteria to be used,
and the rationale for their choice, and any risks requiring
contingency planning. Its a record of test planning
process. [After IEEE 829]

: what is unit testing? It comes under white box or Black
Box testing? Answer
# 7
Hi
Unit testing is testing individual module fo an
application.it is done by developers.it comes under white
box testing.In black box testing we test the functinality
or behavior of an application.we dont have the internal
knowledge of the application.where as in white box testing
basic path coverage,loops and funtions written in coding

esting of each and every part indivdually called Unit
Testing. Unit Testing is done by Developers before giving
the application to Testers.

: Unit Testing Reply
# 14
Testing an Individual program or component is known as UNIT
TESTING (or) MICRO TESTING. (or) PROGRAM TESTING.
This type of testing is undertaken by Developers.They will
test for the program correctness
It is classified into 3 types:
(i)Execution Testing
(ii)Operation Testing
(iii)Mutation Testing (Mutation means Change)

i)Verifying the logic of the program.(statement
coverage,loop coverage,conditional coverage,programme
technique coverages)

ii)Checking whether the program is running on the customer
expected platform(ie OS,Compilers,Browser etc.)
iii)To check whether the program is responding to the
changes or not.
User accepting test: User accepting test means user has
tested it is working or not as per the requirment this is
called the user acceptence testing..

# 2
User acceptance Testing is performed by the Client of the
applcation to determine whether the application is
Developed as per the requirements specified by him/her.
it is performed within the development of the organization
or at the client site.
Alpha testing and Beta testing are the examples of
Acceptance Testing.
S

After finishing of integration testing system testing will
start. system testing: testing all the requirements in the
application is called system testing.

System testing is the combination of Functional & Non
functional testings.

Functional testing: Testing the application functionality
against functional specifications provided by the client

Unit Testing
Smoke testing / Sanity testing
Integration Testing (Top Down,Bottom up Testing)
Interface & Usability Testing
Regression Testing
Pre User Acceptance Testing(Alpha & Beta)
User Acceptance Testing
White Box & Black Box Testing

Non-Functional Testing: Testing the application against
client's and performance requirement.
Non-Functional Testing covers:

Load and Performance Testing
Stress & Volume Testing
Compatibility & Migration Testing
Data Conversion Testing
Installation Testing
Security Testing (ApplicationSecurity, Network Security,
System Security)

What is meant by system testing? Answer
# 5
system testing: testing all the requirements in the
application is called system testing.
it was done by test engineer.
in system testing test engineer test the
1)user interface (colour,size,font,allignement,e.t.c),
2)usability (tab movements,curser blinking,shotcut
keys,e.t.c),
3)functional (front end,back end),
4)non functional (performance,security),
5)validate.

plz let me know if any mistakes in it.

The different states of a bug can be summarized as follows:

1. New
2. Open
3. Assign
4. RF-Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed

Description of Various Stages:
1. New: When the bug is posted for the first time, its state
will be “NEW”. This means that the bug is not yet approved.

2. Open: After a tester has posted a bug, the lead of the
tester approves that the bug is genuine and he changes the
state as “OPEN”.

3. Assign: Once the lead changes the state as “OPEN”, he
assigns the bug to corresponding developer or developer
team. The state of the bug now is changed to “ASSIGN”.

4. Test: Once the developer fixes the bug, he has to assign
the bug to the testing team for next round of testing.
Before he releases the software with bug fixed, he changes
the state of bug to “TEST”. It specifies that the bug has
been fixed and is released totesting team.

Deferred: If the bug is not related to current build or can
not be fixed in this release or bug is not important to fix
immediately then the project manager can set the bug status
as deferred.
6. Rejected: If the developer feels that the bug is not
genuine, he rejects the bug. Then the state of the bug is
changed to “REJECTED”.

7. Duplicate: If the bug is repeated twice or the two bugs
mention the same concept of the bug, then one bug status is
changed to “DUPLICATE”.

8. Verified: Once the bug is fixed and the status is changed
to “Readt foir TEST”, the tester tests the bug. If the bug
is not present in the software, he approves that the bug is
fixed and changes the status to “VERIFIED”.

9. Reopened: If the bug still exists even after the bug is
fixed by the developer, the tester changes the status to
“REOPENED”. The bug traverses the life cycle once again.

10. Closed: Once the bug is fixed, it is tested by the
tester. If the tester feels that the bug no longer exists in
the software, he changes the status of the bug to “CLOSED”.
This state means that the bug is fixed, tested and approved.

While defect prevention is much more effective and efficient
in reducing the number of defects, most organization
conducts defect discovery and removal. Discovering and
removing defects is an expensive and inefficient process. It
is much more efficient for an organization to conduct
activities that prevent defects.

Explain me about test scenarios? How will you write it?
Answer
# 2 Test scenarios are generally the paths which cover whole
application. Mainly these are generated on the basis of Use
cases . then test cases are generated on the basis of test
scenarios.
Answer
Smoke Testing:
Smoke testing is nothing but to test the functionality of
the software once build is done.
Sanity testing:
Sanity testing is nothing but to test the existing behaviour
of an application, environment check up before starts
execution.
What is severity and priority?Give some examples of
severity and priorty and high severity & low priority and
viceverse and also explain each.
Question Submitted By :: Veeru I also faced this Question!!
Rank Answer Posted By Answer
Severity:seriousness of defect wrt to functionality

!High:without resolving the defect we r unable to continue
testing.
!Medium:compulsory to solve but able to continue
!low:May or may not be resolved.

Prority:Importance of the defect wrt customer
(High,medium,low)
When we go for examples
1.user interface bugs[low severity]
Eg1:Spelling mistake(High priority)
Eg2:Improper allignment(Low priority)

2.Input domain bugs:[medium severity]
Eg1:Doesnot allow valid values(high priority)
Eg2:allows invalid type also(low priority)

3.Race condition bugs[High severity]
Eg1:Deadlock(High priority)
Eg2:improper order or services(Low priority)
like this there r many,but the thing is that as the name
severity itself says seriousness,
based on the seriousness created by the bug we give priority
ie., importance

suggest me if there is any mistake
1. High Severity -Low priority
Supposing, you try the wildest or the weirdest of operations
in a software (say, to be released the next day) which a
normal user would not do and supposing this renders a run
-time error in the application,
the severity would be high.The priority would be low as the
operations or the steps which rendered this error by most
chances will not be done by a user.
2. Low Severity -High priority
An example would be- you find a spelling mistake in the name
of the website which you are testing.
Say, the name is supposed to be Google and its spelled there
as 'Gaogle'.Though, it doesnt affect the basic functionality
of the software,it needs to be corrected before the release.
Hence, the priority is high.
3. High severity--- High Priority
A bug which is a show stopper.i.e, a bug due to which we are
unable to proceed our testing.
An example would be a run time error during the normal
operation of the software,
which would cause the application to quit abruptly.
4. Low severity --- low priority
Cosmetic bugs

Severity: Describes the bug in terms of functionality.
Priority: Describes the bug in terms of customer.

few examples:

High Severity and Low Priority -> Application doesn't allow
customer expected configuration.
High Severity and High Priority -> Application doesn't allow
multiple user's.

Low Severity and High Priority -> No error message to
prevent wrong operation.
Low Severity and low Priority -> Error message is having
complex meaning.

What is the difference b/w Smoke and Sanity Testing? I heard
that Sanity testing will be done by developers. Is that so?
Answer
SMOKE Testing - When a tester get build from the Dev,
tester perform the initial testing to ensure that the basic
functionality is working fine or not. If not then further
detail testing is not proceeded. This initial testing
before the detail testing is known as SMOKE testing.

Sanity Testing - Once the all the test cycles have been
executed and all the open defects have been fixed and
retested, now before providing the signoff for next phase
testers needs to do Sanity testing to test some critical
functionality which will ensure that the defect fixes have
not disturb the other functionality. This test cycle is
short and quick and is known as Sanity testing.

Low Severity and High Priority:

When there is a spelling mistake in a Login page i.e for
example The company logos such as SATYAM is spelled as
SAYAM in the front page of the application. This is treated
as a Low severity and High priority.
(or)

Banking application:
in some situations customer will not get confirmation
message even though the process is going on smoothly at
backend.

Medium Sev and Medium Priority:

When there are mistakes in Error messages or warning
messages.

High severity and Low priority:

Suppose as per clients req ur application should work on
Both IE 5.5 and IE 6.0. But it is working fine with IE 6.0
and not working with IE 5.5.
Hence it is not meeting the req it is high sev and hence
it's functionality is working fine but can fix it at any
time so of low priority.

REGRESSINON

Whenever enhancements added to the existing functionality
then only we go for Regression testing why because new
changes are whether effecting the old functionality or not

what is test log? tell the process?
Answer
# 4 test log is nothing but the what are test cases we r
executed.
the pass/fail criteria of that testcases

Re: Difference btween the QA and QC?
Answer
# 3 ________________________________________
Quality Assurance
Preventing problems
Prepare Standards and Guidelines
Review the reports
Prepare the test plans
Verification

Quality Control
Identify problems
Implement Standards and Guidelines
Prepare the reports
Implement the test plans
Validation

What is metrics? explian the type of metrices.
Answer
# 3 Metrics are generally classified into 2 types
1. Process metrics
2. Product metrics
b a metric used to measure the haracteristic of the
methods, techniques and tools employed in eveloping,
implementing and maintaining the software system.

Product metric: a metric used to measure the characteristic
of the documentation and code. The metrics for the test
process would include status of test activities against the
plan, test coverage achieved so far, amongst others. An
important metric is the number ofdefects found in internal
testing compared to the defect found in customer tests,
which indicate the effectiveness of the test process itself.

e: What is testing life Cycle and Explain different phases?
Answer
# 1 1.Testing Requirement: Gather all type of requirements and
scope of the application fro SRS.
2.Testing Design: Writing test cases for each functionality
of the application provided in FS.
3.Test Execution: Executing all test cases to find if there
exists any bug.
4.Test Reporting: Analysis of the whole system testing
5.Test Deliverable: Test report has to be generated to
validate the system.

Re: What is reference matrix or tracability matrix?
Answer
# 7 We use tracebility Matrix to map the test cases with the
requirements. So that we ensure all the requirements are
covered in test cases. With the help of RTM we can measure
the potential risk.

Can any one explain me, What is Integration testing process?
Answer
# 7 INTEGRATION TESTING:
Definition: A process of testing the connectivity or data
transfer between the couple of unit tested modules.
What is a Test Strategy? What is d difference between a Test
Strategy and a Test Plan?
Answer
# 5 Test Strategy: This document is a organizational level
document and is prepared by the PM. This document contains
the details about the whole testing approach, methodologies
etc.

Test Plan: This document is prepated by the Test Lead. It
consists of the testing details i.e.
who is going to test
what would be environment
what is in scope of testing
delivery dates
risks and contingencies etc

what is the difference between test bed & test environment.
Answer
# 1 Test Bed :
An execution environment configured for testing. May
consist of specific hardware, OS, network topology,
configuration of the product under test, other application
or system software.

Test Environment :
The hardware and software environment in which tests will
be run, and any other software with which the software
under test interacts when under test including stubs and
test drivers.

Advantages and Dis-advantages of V-model?Is every company is
using V-model only
# The advantages of V model are:
1) Time saving - This is because the Testing activities
start as soon as the customer gives the requirement
(parallal to the development activites)i.e. testing design
starts when requiremnts are given by customer meanwhile
developers start with coding and when the coding is
complete testing can immediately start without waste in
time for the design.
2) Cost Saving - V model is cost saving because there is
early detection of bugs while development and unit testing.

Now coming to the next part of question, All the companies
do not implement V Model. It depends on customer
requirement eg. if the customer is more interested to cover
up all risks then the company may use Spiral Model.

There are few disadvantages of V model:
1) Expensive
2) For BIG projects its a repeated process

# Integration testing is a type of testing. When two or more
than two modules are integrated, then this tesing will be
done to check whether the flow of the data from one module
to other is proper or not.

This type of testing is not only done by the developer, but
also will be done by the person who is having the codng
knowledge.In this process stubs and drivers are used. They
are also calld as Called and calling programs.

There are two types of integration testing
1. Top-down integration
2. Bottom-up integration

What is the differencein validation & verification?? What we
exactly do in verification & validation ????? Give an
example....
Answer
# 1 Verrification is a process that whether we are building the
product right, i.e we have the requirement with us. whether
we are developing the product accordingly or not?

Validation is the process that whether we are building the
right product, i.e the product which we have developed is
right or not?

Verificaation involves collection of the requirements,
Analyse those requirements, Preparation of HLD and LLD.

Validation invoves unit,Integration,system and User
acceptance testing.

V Model is the best Example. left side of the V-Model is
verification and right side is the validation

Bug : Any discrepancy found during testing of software
product.

Defect: Any discrepancy found by the customer in the
software product after the release in to production

Error: Any discrepancy in the coding

# 3 Test Life Cycle:
Requirements Gathering--Test Plan Preparation--Test Cases
Preparation--Test Cases Execustion--Report Ananlysis--Bug
Ananlysis--Bug Reporting

Defect Life Cycle:
New--Open--Assign--Fixed/Deferred/Not a
bug/Later/WontFix/Duplicate--Test--Verified--Reopen/Close
Re: What is security testing? How to test the web
application using security testing ?
Answer
# 1 using three methods the sequerity is provided

1) Authorazation/Authentication
Allowing valid user and preventing invalid users.....
2) Access Control
Permission to valid user to access user
fctionalitites in software build.

3) Encryption/Dis\cryption
Data conversions in b/n client process and server
provcess to prevent third party avccessing

What is security testing? How to test the web application
using security testing ?
Answer
# 4 There is different type of methods are using for security
testing
1)Authorization and Authentication:For checking the valid
and invalid user.
2)Access Control:access permission to valid user to access
user functionalities in application.
3)Encryption and Decryption: Data conversions in between
client process and server process to prevent third party
accessing

The above techniques using for security testing for web
application

Re: What is Functional Testing?
Answer
# 3 functional testing means testing all the functionalities in
the application which can given by the client

Can anyone tell me testing comes under verification or
validation?
Answer
# 1 Verification is proving that a product meets the
requirements specified during previous activity carried out
correctly throughout development life cycle ,while
validation checks that the system meets the customer's
requirements at the end of the life cycle.
The creation of the test product is much more closely
relation to validation than to verification .
Traditionally software testing has been consider a
validation process.

Yes we will write regression test cases.... Regression is
nothing but when new functionality is added then we r doing
regression testing... so we r writing test cases for new
functionality and we will write test cases like P1 for
regression test

Explain Boundary value analysis, Equivalence partitoning and
Error guessing?
Answer
# 1 Boundary value analysis : Designing test cases at boundary
values. If field take values from 10 to 20 numbers,
following are the boundary values which is taken care while
doing testing.
Valid boundary values 10, 11, 19, 20
Invalid Boundary values 9, 21.

Equivalence partitioning : Designing test cases by deviding
the input values in to equivalence partitions.

valid Equivalence partitions 14 or 18
Invalid equivalence partitions 5, 26

Error guessing : From testers experience , are able to guess
where bug will come and in which scenario.

what is the defference between stress and load testing?
Answer
# 5 To test how much load is applied on Server/CPU and response
time of server for different configuration of load is known
as Performance testing. For conducting performance testing,
we use three techniques:

1.LOAD TEST --> Estimating the performance of Server/CPU
under customer expected load is called Load Test.

2.STRESS TEST --> Estimating the performance of Server/CPU
under maximum load or peak load is called Stress Test.

3.VOLUME TEST --> Estimating the response time of Server/CPU
applying more than maximum load or peak load is called
volume test.

Re: Difference b/w test case and scenarios.
Answer
# 2 Test Scenario: Identifying the all possible areas to be
tested (What)

Test Case: describes an input action and expected result to
ensure that a certain feature works correctly as per the
specifications.

What is the Configuration Management?
Answer
# 2 Configuration Management is :
- The process of identifying & defining the configuration
items in a system,
- controlling the release and change of these items
throughtout the system life cycle,
- recording and reporting the status of configuration items
and change requests,
- and verifying the completeness and correctness of
configuration items.

What is the difference between bug,defect, error, failulre,
fault & mistake?
Answer
# 2 Bug: Error which appears during testing phase

Defect: Error that appears during development phase

Failure: When the result is not equal to actual result then
it is said to be Failure

Fault & Mistake: Errors which are made at that time and
recognised at that time itself

testing how well the system protect against unauthorized
internal or external aceess willfull damage etc

Retest

after fixes of defect doing testing that is Retesting

Regression
After Fixes and modification in the application finding the
impact of that fixed or modification in the application

1) New: A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with
status as ‘New’.
2) Deferred: If the bug is not related to current build or
can not be fixed in this release or bug is not important to
fix immediately then the project manager can set the bug
status as deferred.
3) Assigned: ‘Assigned to’ field is set by project lead or
manager and assigns bug to developer.
4) Resolved/Fixed: When developer makes necessary code
changes and verifies the changes then he/she can make bug
status as ‘Fixed’ and the bug is passed to testing team.
5) Could not reproduce: If developer is not able to
reproduce the bug by the steps given in bug report by QA
then developer can mark the bug as ‘CNR’. QA needs action to
check if bug is reproduced and can assign to developer with
detailed reproducing steps.
6) Need more information: If developer is not clear about
the bug reproduce steps provided by QA to reproduce the bug,
then he/she can mark it as “Need more information’. In this
case QA needs to add detailed reproducing steps and assign
bug back to dev for fix.
7) Reopen: If QA is not satisfy with the fix and if bug is
still reproducible even after fix then QA can mark it as
‘Reopen’ so that developer can take appropriate action.
8 ) Closed: If bug is verified by the QA team and if the fix
is ok and problem is solved then QA can mark bug as ‘Closed’.
9) Rejected/Invalid: Some times developer or team lead can
mark the bug as Rejected or invalid if the system is working
according to specifications and bug is just due to some
misinterpretation.
Software Testing - Bug Life Cycles
Various life cycles that a bug passes through during a
software testing process.

Enlarge Image
What is a Bug Life Cycle?
The duration or time span between the first time bug is
found (‘New’) and closed successfully (status: ‘Closed’),
rejected, postponed or deferred is called as ‘Bug/Error Life
Cycle’.

(Right from the first time any bug is detected till the
point when the bug is fixed and closed, it is assigned
various statuses which are New, Open, Postpone, Pending
Retest, Retest, Pending Reject, Reject, Deferred, and
Closed. For more information about various statuses used for
a bug during a bug life cycle, you can refer to article
‘Software Testing – Bug & Statuses Used During A Bug Life
Cycle’)

There are seven different life cycles that a bug can passes
through:

< I > Cycle I:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) Test lead finds that the bug is not valid and the bug is
‘Rejected’.

< II > Cycle II:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with
status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is invalid and is marked with a status of
‘Pending Reject’ before passing it back to the testing team.
5) After getting a satisfactory reply from the development
side, the test leader marks the bug as ‘Rejected’.

< III > Cycle III:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with
status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug as
‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug to
‘Pending Retest’ and passes on to the testing team for retest.
7) The test leader changes the status of the bug to ‘Retest’
and passes it to a tester for retest.
8) The tester retests the bug and it is working fine, so the
tester closes the bug and marks it as ‘Closed’.

< IV > Cycle IV:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with
status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug as
‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug to
‘Pending Retest’ and passes on to the testing team for retest.
7) The test leader changes the status of the bug to ‘Retest’
and passes it to a tester for retest.
8) The tester retests the bug and the same problem persists,
so the tester after confirmation from test leader reopens
the bug and marks it with ‘Reopen’ status. And the bug is
passed back to the development team for fixing.

< V > Cycle V:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team with
status as ‘New’.
4) The developer tries to verify if the bug is valid but
fails in replicate the same scenario as was at the time of
testing, but fails in that and asks for help from testing team.
5) The tester also fails to re-generate the scenario in
which the bug was found. And developer rejects the bug
marking it ‘Rejected’.

< VI > Cycle VI:
1) After confirmation that the data is unavailable or
certain functionality is unavailable, the solution and
retest of the bug is postponed for indefinite time and it is
marked as ‘Postponed’.

< VII > Cycle VII:
1) If the bug does not stand importance and can be/needed to
be postponed, then it is given a status as ‘Deferred’.

This way, any bug that is found ends up with a status of
Closed, Rejected, Deferred or Postponed.

Status Alternative Status
NEW
ASSIGNED OPEN
DEFERRED
DROPPED REJECTED
COMPLETED FIXED, RESOLVED, TEST
REASSIGNED REOPENED
CLOSED VERIFIED
What is a bug/error?
A bug or error in software product is any exception that can
hinder the functionality of either the whole software or
part of it.

How do I find out a BUG/ERROR?
Basically, test cases/scripts are run in order to find out
any unexpected behavior of the software product under test.
If any such unexpected behavior or exception occurs, it is
called as a bug.

What is a Test Case?
A test case is a noted/documented set of steps/activities
that are carried out or executed on the software in order to
confirm its functionality/behavior to certain set of inputs.

What do I do if I find a bug/error?
In normal terms, if a bug or error is detected in a system,
it needs to be communicated to the developer in order to get
it fixed.

Right from the first time any bug is detected till the point
when the bug is fixed and closed, it is assigned various
statuses which are New, Open, Postpone, Pending Retest,
Retest, Pending Reject, Reject, Deferred, and Closed.

(Please note that there are various ways to communicate the
bug to the developer and track the bug status)

Statuses associated with a bug:
New:
When a bug is found/revealed for the first time, the
software tester communicates it to his/her team leader (Test
Leader) in order to confirm if that is a valid bug. After
getting confirmation from the Test Lead, the software tester
logs the bug and the status of ‘New’ is assigned to the bug.

Assigned:
After the bug is reported as ‘New’, it comes to the
Development Team. The development team verifies if the bug
is valid. If the bug is valid, development leader assigns it
to a developer to fix it and a status of ‘Assigned’ is
assigned to it.

Open:
Once the developer starts working on the bug, he/she changes
the status of the bug to ‘Open’ to indicate that he/she is
working on it to find a solution.

Fixed:
Once the developer makes necessary changes in the code and
verifies the code, he/she marks the bug as ‘Fixed’ and
passes it over to the Development Lead in order to pass it
to the Testing team.

Pending Retest:
After the bug is fixed, it is passed back to the testing
team to get retested and the status of ‘Pending Retest’ is
assigned to it.

Retest:
The testing team leader changes the status of the bug, which
is previously marked with ‘Pending Retest’ to ‘Retest’ and
assigns it to a tester for retesting.

Closed:
After the bug is assigned a status of ‘Retest’, it is again
tested. If the problem is solved, the tester closes it and
marks it with ‘Closed’ status.

Reopen:
If after retesting the software for the bug opened, if the
system behaves in the same way or same bug arises once
again, then the tester reopens the bug and again sends it
back to the developer marking its status as ‘Reopen’.

Pending Reject:
If the developers think that a particular behavior of the
system, which the tester reports as a bug has to be same and
the bug is invalid, in that case, the bug is rejected and
marked as ‘Pending Reject’.

Rejected:
If the Testing Leader finds that the system is working
according to the specifications or the bug is invalid as per
the explanation from the development, he/she rejects the bug
and marks its status as ‘Rejected’.

Postponed:
Sometimes, testing of a particular bug has to be postponed
for an indefinite period. This situation may occur because
of many reasons, such as unavailability of Test data,
unavailability of particular functionality etc. That time,
the bug is marked with ‘Postponed’ status.

Deferred:
In some cases a particular bug stands no importance and is
needed to be/can be avoided, that time it is marked with
‘Deferred’ status.

REASSIGNED / REOPENED: If the Tester finds that the ‘fixed’
bug is in fact not fixed or only partially fixed, it is
reassigned to the Developer who ‘fixed’ it. A REASSIGNED bug
needs to be COMPLETED again.

CLOSED / VERIFIED: If the Tester / Test Lead finds that the
bug is indeed fixed and is no more of any concern, it is
CLOSED / VERIFIED. This is the happy ending.

Bug Life Cycle Implementation Guidelines
• Make sure the entire team understands what each bug status
exactly means. Also, make sure the bug life cycle is documented.
• Ensure that each individual clearly understands his/her
responsibility as regards each bug.
• Ensure that enough detail is entered in each status
change. For example, do not simply DROP a bug but provide a
reason for doing so.
• If a bug tracking tool is being used, avoid entertaining
any ‘bug related requests’ without an appropriate change in
the status of the bug in the tool. Do not let anybody take
shortcuts. Or else, you will never be able to get up-to-date
bug metrics for analysis.

Madurai - 625 004.
Phone: 0452 - 237 0329, 237 2172

9944339220-rani
-9942682059,dayavinodha@yahoo.co.in

Sanity testing

whenever the tester founds the bug, he will inform to the
developers about the bug and to fix it. the developer than
fixes the bug and sends to the tester, this process of
fixing the bug and sending the new version to the tester is
called Build.
the tester has to test whether the major functionality of
the application is working good or stopping us from testing
is called as sanity testing.

Re: What is sanity testing? and how to do sanity testing
for a telephone Answer

Sanity means that, normal testing to verify that whether
the build is fit for further testing or not?
Eg.1.
From GUI perspective, we need to test whether all links are
working fine or not (any broken links?), i.e. if I click on
one link, whether the page is taking me to that particular
page or not?

Eg.2.
In GUI, we need to test that, whether the help is
documented properly or not? i.e. if the user is stuck any
point of time, and if help is clicked, whether the page is
navigating to the exact help context or not?

Eg.3.
As per installation is concerned, we need to verify,
whether the build is properly getting installed or not?
Whether the build is compatible (supports for upgradation
and degradation of other versions) or not?

Eg.4.
If CLI Menus are theer, we need to make sure that, no main
menus and the child menus are missing.

In a word, we can say that, Usability (GUI), Compatibility,
Installation, CLI will all comes in to picture for the
sanity to be done.

Re: What is the difference between Sanity and Smoke Testing?
With Example. Answer
# 1
Sanity Testing:

Its the first test/initial test that is done to check
weather the new software version is performing well enough
to accept it for a major testing effort. Ex: System not
hanging soon..

Smoke Testing:

It is performed after Sanity Test to check the weather all
the functionalities are available to perform the detailed
testing.

Identifying or Testing whether build is ready for testing
is called sanity testing.It performs in Development
environment.

Testing the major functionalities of the project is called
smoke testing.It performs in testing environment

Smoke testing is useful for checking for the main funality
of the application.

Sanity testing is useful for the checking for the basic
finicality of the application

Is This Answer Correct ?

1 Yes

0 No

Post New Answer