Notesale: Turn your study into money

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above

---

Testing Titans: Becoming an Expert in
Software Quality Assurance Questions

Q
...


Sub
Q
...


1
...


Ans:

Skills of software tester are as follows :
1
...
The major objective of testing is to identify the hidden errors, not simply prove that the
software works
...
For a tester to be effective in his role, he must be able to analyze the given business
situation and judge all the possible scenarios
...
He should have the capacity to identify and tackle unfamiliar problems and should develop
a strategy to validate it
...
Creating situations and validating the application under test, before presenting it to
customers, can be done effectively only by a person who has strong analytical skills
...
The ability to envision business situations
i)
...

ii)
...

iii)
...

iv)
...

v)
...

vi)
...

3
...
A tester should understand that being an intellectual and being intellectually curious are not
the same
...
A tester should arguably be the latter one -- intellectually curious -- which is all about
asking questions and not about having answers
...
He should believe in the pursuit of knowledge as a value in and of itself
...
He should love asking questions and should not consider it a blow to his ego if he is wrong
about something
...
It is intellectual curiosity that motivates and prompts a tester to identify interesting
questions about the software being tested
...
Thus, a tester should develop the skill to see what everyone else hasn't seen, to think what
no one else has thought of and to do what no one else has dared
...
A "global" approach
i)
...

ii)
...

iii)
...

iv)
...

v)
...

5
...
The quality of life of an individual and the quality of what he produces/delivers depends
largely on the quality of his thought process
...
The thought process of a tester should be undistorted, impartial and without any prejudices
...
A tester should be able to take charge of the inherent structures and impose intellectual
standards upon the software under test
...
He should be able to raise vital questions precisely and clearly, gather and assess relevant
information, interpret it effectively in order to come to well-reasoned conclusions and
solutions, and test those conclusions against the given criteria and standards
...
The ability to apply basic and fundamental knowledge
i)
...

ii)
...
One can attain
knowledge by so many means, but that knowledge is worthwhile only when it adds value
to situations encountered
...
A smart tester should be able to apply the knowledge attained over years of experience
with the domain, process, product, customers, mistakes and successes in his testing
...
He should be able to make use of fundamental communication, mathematical and software
application skills
...
He should also be able to effectively apply the skills he has attained to practical situations
...
Continue to learn
i)
...

ii)
...

iii)
...

iv)
...

v)
...

8
...
A tester should be able to examine the piece of software under test and the resulting
processes, with focus on the given specification, and understand the behavior of the
software
...
Being human, a tester may have severe biases, prejudices and intolerances that prevent him
from performing well
...
He should possess the intellectual integrity to correct those barriers in order to efficiently
understand the nature of the software under test
...
He should also be willing to shrug off the set of practices and character traits that
undermine his intellectual integrity
...
Planning, time management skills
i)
...

ii)
...

iii)
...

iv)
...

v)
...

vi)
...

10
...
A tester must be able to communicate his thoughts and ideas effectively, using a variety of
tools and media
...
He needs to develop and use this skill throughout his career and should learn to
communicate effectively to the stakeholders so as to avoid ambiguities and inconsistencies
...
For example, printed presentations should be concise and to the point and should follow
logically
...
The language should be pragmatic rather than philosophical, and arguments should be
supported by facts
...
In the case of oral presentations, the voice, body language and appearance of the presenter
are as important as the content and visual aids
...
A tester should develop his skills to overcome shyness and any fear of speaking
...


Page 3 of 32

(ii)

Explain decision table with suitable example
...
g
...
This
technique is sometimes also referred to as a cause-effect‘ table
...

The system should not contain too many inputs otherwise the number of combinations will
become unmanageable
...
Once you have identified the aspects
that need to be combined, then you put them into a table listing all the combinations of True
and False for each of the aspects
...


Decision table testing is black box test design technique to determine the test scenarios
for complex business logic
...
Decision tables provide a systematic way of stating complex business rules, which is
useful for developers as well as for testers
...
Decision tables can be used in test design whether or not they are used in specifications,
as they help testers explore the effects of combinations of different inputs and other
software states that must correctly implement business rules
...
It helps the developers to do a better job can also lead to better relationships with them
...
Testing combinations can be a challenge, as the number of combinations can often be
huge
...
Testing all combinations may be impractical if not impossible
...
We have to be satisfied with testing just a small subset of combinations but making the
choice of which combinations to test and which to leave out is also important
...
If you do not have a systematic way of selecting combinations, an arbitrary subset will be
used and this may well result in an ineffective test effort
...
Because of this, it‘s always good to
take small sets of combinations at once
...
, so the top row will have all ―Yes‖ and then all ―No‖ (Apply the same principle to all
such tables)
...


Ans:

1
...
Drivers are tools used to control and operate the software being tested
...
One of the simplest examples of a driver is a batch file, a simple list of programs or
commands that are executed sequentially
...

3
...

4
...

5
...
Stubs
1
...

2
...

3
...


(iv)

Describe two types of test reports
...
There are
3 types of test reporting
...
Test incident report:
A test incident report is communication that happens through the testing cycle as and when
Defects are encountered
...
The high impact test incident are Highlighted in the
test summary report
...
Test cycle report:
A test cycle entails planning and running certain test in cycle, each cycle using a different
build of the product
...

Test cycle report gives
1
...

2
...
Progress from the previous cycle to the current cycle in terms of defect fixed
4
...
Any variation observed in effort or schedule
3
...
A report
that summarizes the result of a test cycle is the test summary report
...
Phase wise test summary ,which is produced at the end of every phase
2
...


(Any two
types of
test
report
with
explanati
on:
4marks,
2marks
each )

Page 6 of 32

A Summary report should present
1
...
Description : Identify the test items being reported in this report with test id
3
...

4
...

5
...

6
b)

Attempt any ONE of the following :
6M

(i)
Ans:

What are sanity testing and smoke testing
...

Smoke Testing is a testing technique that is inspired from hardware testing, which checks for
the smoke from the hardware components once the hardware's power is switched on
...

ii) If the Test fails, build is declared as unstable and it is NOT tested anymore until the smoke
test of the build passes
...

ii) Designing and executing the basic functionalities of the application
...

iv) Smoke Tests enables uncovering obvious errors which saves time and effort of test team
...

Sanity testing, a software testing technique performed by the test team for some basic tests
...
The
terminologies such as Smoke Test or Build Verification Test or Basic Acceptance Test or
Sanity Test are interchangeably used; however, each one of them is used under a slightly
different scenario
...
It
is used to determine if the section of the application is still working after a minor change
...
Sanity test is a narrow regression test that focuses
on one or a few areas of functionality
...


Ans:

Requirements defects: A valid requirement which is mandatory and supposed to code (or
implement) is missed
...
These types of observations are categorized as ‗Missed
requirements defects‘ since the requirements are missed from requirement specification
document
...

Example:
Tester observation while testing the Website: Tester found that ‗Disclaimer‘ link is missing in

(Require
ment
defects : 3
marks
and
coding
defects: 3
marks )

Page 7 of 32

the website
...

Coding defects: The requirements have been coded incorrectly due to which behavior of an
implemented software function is not in accordance with the requirement specification
documents
...

Example:
Requirement as per specification document: If user clicks on ‗Home‘ link in a website then
‗Home‘ page should be presented to the user
...
This is an example of coding defect
...


Attempt any FOUR of the following :
a)

16

What factors shall be considered while selecting resource requirements?
4M

Ans:

1
...

2
...
Supporting tools such as compilers , test data generators configuration management tools,
and so on
4
...
Special requirements for running machine- intensive tests such as load tests and
performance tests
6
...

Office and lab space: Where will they be located?
Page 8 of 32

How big will they be?
How will they be arranged?
Software: Word processors, databases, custom tools
...
What else
might be necessary over the course of the project? The specific resource requirements are
very project-, team-, and company-dependent, so the test plan effort will need to
carefully evaluate what will be needed to test the software
...


4M

Advantages of using automated tools for testing are as follows :
1
...

Every time source code is modified software tests should be repeated
...

iii) Manually repeating these tests is costly and time consuming
...

iv) Automated software testing can reduce the time to run repetitive tests from days to hours
...


(Two
advantag
es: 2
marks, 2
disadvant
ages: 2
marks )

2
...

ii) Automated tests perform the same steps precisely every time they are executed and never
forget to record detailed results
...
Increase Test Coverage
i) Automated software testing can increase the depth and scope of tests to help improve
software quality
...

iii) They can even be run on multiple computers with different configurations
...

v) Automated software tests can easily execute thousands of different complex test cases
during every test run providing coverage that is impossible with manual tests
...

4
...

Page 9 of 32

ii) Automated testing can simulate tens, hundreds or thousands of virtual users interacting
with network or web software and applications
...
High investments required in package purchasing and training
...
High package development investment costs
...
High manpower requirements for test preparation
...
Considerable testing areas left uncovered
...

Stress testing is testing the software under less than ideal conditions
...
Look at your
software and determine what external resources and dependencies it has
...
With stress testing you starve the software
...
g
...
But if the system runs low on resources you had a greater potential
to expect a bug
...
Ideally the software would run
without crashing or losing data
...
In order to perform load
testing on the software you feed it all that it can handle
...
If the software operates on peripherals such as printer, or communication
ports, connect as many as you can
...
With most software it is important for it to run
over long periods
...
So
Time acts as a important variable
...

Stress testing and load testing are the types of performance testing
...

Example: Open many number of browsers in the windows simultaneously
...

Connect more than one printer to the system
...


(load
testing : 2
marks,
stress
testing : 2
marks )

4M

(Guidelin
i) Assessment of the organization‘s maturity (e
...
readiness for change);
es:
ii) Identification of the areas within the organization where tool support will help to improve 4marks)
testing processes;
iii) Evaluation of tools against clear requirements and objective criteria;
iv) Proof-of-concept to see whether the product works as desired and meets the requirements
and objectives defined for it;
v) Evaluation of the vendor (training, support and other commercial aspects) or open-source
network of support;
vi) Identifying and planning internal implementation (including coaching and mentoring for
those new to the use of the tool)
...
List any two characteristics of defect 4M
management process
...
The primary goal is to prevent defects
...

2
...
e
...

3
...
In other words, the project staff, by
doing their job, should capture information on defects at the source
...
As much as possible, the capture and analysis of the information should be automated
...
Defect information should be used to improve the process
...

6
...
Thus to prevent defects, the
process must be altered
...


i) Boundary conditions are special because programming, by its nature, is susceptible to
problems at its edges
...

iii) If an operation is performed on a range of numbers, odds are the programmer got it right
for the vast majority of the numbers in the middle, but maybe made a mistake at the edges
...

1
...
h>
2
...
{
4
...
printf(―enter the number ―);
6
...
for(i =1 ;i <=n;i++)

(Need for
BVA : 2
marks,
example :
2 marks )

Page 11 of 32

8
...
printf (―the factorial of a number is ‖%d‖, fact);
10
...

3
...

{**Note: Any other relevant diagram also shall be considered**}

4M

State or graph based testing is useful in situations where
1
...

2
...


(Diagram
:2 marks,
Explanati
on:2
marks)

In the above case, each of the states (represented by circles) is an event or a decision point
while the arrows or lines between the states represent data inputs
...
The application can be characterized by a set of states
...
The data values (screen, mouse clicks) that cause the transition from one state to another
is well understood
...
The methods of processing within each state to process the input received is also well
understood
...


Ans:

Bi- directional integration is a combination of the top-down & bottom-up integration approaches (Diagram
: 2 marks,
used together to derive integration steps
...
The individual components 1, 2, 3, 4 and 5 are tested separately and
bi-directional integration performed initially with the use of stubs and drivers
...
A driver is a
function which redirects the requests to some other components and stubs simulate the behavior
of missing components
...
Once components 6, 7 and 8 become available, the integration
methodology then focus only on those components, as there are the components which need
focus and are new
...

Advantages:
1
...

2
...

2
...
Units are tested and brought together to make a system
Integration is done
downwards
...
It require very high cost for testing because one part has Top-down approach while
another part has bottom-up approach
...
It cannot be used for smaller system with huge interdependence between different
modules
...


c)
Ans:

4M

Write four test cases to test sign-in form of gmail account
...
Try
again‖

Pass
It gives
message as
―Please enter
your
password‖
It give
Pass
message as‖
Sorry, Google
doesn‘t
recognize that
email‖
Pass
It gives
message
―Wrong
password
...


4M

Compare alpha testing and beta testing
...

2
...

4
...

6
...

Performed
in
controlled
Environment as developer
is
present
...

It is done during implementation
phase of software
It is not considered as live
application
Less time consuming as developer
can make necessary changes in given
time
...


Beta Testing
Performed at End user‗s site
...

High probability of finding errors as
end user can use it the way he wants
...


5
...


1
...


3
...
More time consuming
...


4M

Ans:

Product Metrics is classified as :
1
...

2
...
It includes both development activities and testing activities
...
Test defect metrics b
...
Test defect metrics: help the testing team in analysis of product quality and testing
b
...

3
...
These
metrics help in planning and estimating of testing activities
...


a
...


12

(i)

Describe structural walk through under static testing
...

In walkthroughs, a set of people look at the program code and raise questions for the author
...
If the author is unable to
answer some questions, he or she then takes those questions and finds their answers
...

(ii) In a walkthrough, the programmer who wrote the code formally presents (walks through)
it to a small group of five or so other programmers and testers
...

(iv) Having at least one senior programmer as a reviewer is very important
...

Limitations of Manual Testing are as given below :
Manual testing is slow and costly
It is very labor intensive, it takes a long time to complete tests
...
As the complexity of the software increases the complexity
of the testing problem grows exponentially
...

Manual testing is not consistent or repeatable
...
One tester may approach and perform a certain test
differently from another, resulting in different results on the same test, because the tests are
not being performed identically
...

GUI objects size difference and color combinations are not easy to find in manual testing
...

Batch testing is not possible, for each and every test execution Human user interaction is
mandatory
...

Processing change requests during software maintenance takes more time
...

Limited support for regression testing: when one portion of software is changed then
regression testing is performed to ensure that other portions are not infected by the recent
Page 15 of 32

change
...

Error Prone Testing: as test process is repeated several times test engineers become bored
which may result in missing some important test case and leads to release defective
software
...
client applications has to be
installed on several machines and it is supposed to be tested by one person to see the
performance of whole software which is very tedious and time consuming task
Non consistent: Manual testing process is not consistent as testing methods and approaches
applied by every person are not remaining same
...
There is no standardization
Limited scope: not suitable for the time bounded and large scale projects as scope of
manual testing is very limited as compared to automated testing
...


4M
(Templat

DEFECT TEMPLATE: In most companies, a defect reporting tool is used and the elements of e
with
a report can vary
...

attributes
:4 marks)
i)
...

ii)
...
) then it won‘t be addressed properly by the developers, so it is
very important to fill as much information as possible in the defect template so that it is
very easy to understand the actual issue with the software
...
2
...

Expected Result:
Actual Result:
OR

Page 16 of 32

ID
Project
Product
Release Version
Module
Detected Build Version
Summary
Description
Steps to Replicate
Actual Result
Expected Results
Attachments
Remarks
Defect Severity
Defect Priority
Reported By
Assigned To
Status
Fixed Build Version
iv)

Ans:

Unique identifier given to the defect
...

Product name
...
(e
...
1
...
3)
Specific module of the product where the defect was
detected
...
g
...
2
...
5)
Summary of the defect
...

Detailed description of the defect
...
Keep it simple but comprehensive
...
Number the steps
...

The expected results
...

Any additional comments on the defect
...

Priority of the Defect
...

The name of the person that is assigned to analyze/fix the
defect
...

Build version of the product where the defect was fixed
(e
...
1
...
3
...


(Any
2
standards
explanati
on:
2
marks
each)

Internal standards are:
1
...

2
...
Test coding standards
4
...

1
...
It enables
a) Easy identification of the product functionality
...

e
...
modules shall be M01,M02
...
sh,
...

2
...

b) Sufficient inline comments, spread throughout the file
c) Up-to-Date change history information, reading all the changes made to the test file
...
Test coding standards:
a) Enforce right type of initialization
b) Stipulate ways of naming variables
...

4
...
It provides guidelines on the level of details that should be present in the
test report, their standard formats and contents
...

(i)

Ans:

Attempt any ONE of the following:

6
6M

Explain V model with diagram
...
It is sequential path of execution of
processes
...

Under V-model, the corresponding testing phase of the development phase is planned in
parallel
...

Verification Phase:
1
...
This phase involves detailed
communication with the customer to understand his expectations and exact requirements
...

2
...
The system design comprises of understanding & detailing the complete
hardware, software & communication set up for the product under development
...
Doing this at earlier stage leaves more time
for actual test execution later
...
High level design: High level specification are understood & designed in this phase
...
System design is broken down further into
modules taking up different functionality
...
Low level design: In this phase the detailed integral design for all the system modules is
specified
...
Components tests can be designed at this stage based on
the internal module design,
5
...
The base suitable programming language is decided base on
requirements
...

Validation:
1
...
This helps to eliminate bugs at an early stage
...
Components testing: This is associated with module design helps to eliminate defects in
individual modules
...
Integration Testing: It is associated with high level design phase & it is performed to test
the coexistence & communication of the internal modules within the system
Page 18 of 32

4
...
It checks the entire system
functionality & the communication of the system under development with external
systems
...

5
...
These tests uncover the compatibility issues with the other systems available
in the user environment
...


OR

Page 19 of 32

Advantages of V-model:
Simple and easy to use
...
This saves a lot
of time
...

Proactive defect tracking – that is defects are found at early stage
...

Works well for small projects where requirements are easily understood
...

Software is developed during the implementation phase, so no early prototypes of the
software are produced
...

(ii)

What is equivalence partitioning? Give example
...
It is
use to reduce test cases
...

The set of input values that generate one single expected output is called a partition
...

Example: 1
...

A life insurance company has base premium of $0
...
Based on the age group,
an additional monthly premium has to pay that is as listed in the table below
...
50 +$ 1
...
15
2
...


a)

Ans:

Attempt any TWO of the following:

16

Write the entity, purpose and attributes of the following elements of test infrastructure
management
...


Test case database(TCDB)

Entity
Test case

Test case- product crossreference

Test case run history

Test case – Defect crossreference

Purpose
Records all the ―static‖
information about the tests

Provides a mapping between
the tests and the
corresponding product
features ; enables
identification of tests for a
given feature
Gives the history of when a
test was run and what was
the result; provides inputs on
selection of tests for
regression runs (see chapter
8)
Gives details of test cases
introduced to test certain
specific defects detected in
the product ;provides inputs
on the selection of tests for
regression runs

Attributes
Test case ID
Test case name
(filename)
Test case owner
Associated files for the
test case
Test case ID
Modulate ID

( Test
case
database(
TCDB) :
4 marks,
Defect
repositor
y: 4
marks)

Test case ID
Run date
Time taken
Run status
(success/failure)
Test case ID
Defect reference#
(points to a record in the
defect repository)

Page 21 of 32

ii)
...
Crossreferences the TCDB

Defect ID
Test case ID

Fix details

Provides details of fixes for a
given defect; crossreferences the configuration
management repository
Captures all the details of the
communication that
transpired for this defect
among the various
stakeholders these could
include communication
between the testing team and
development team, customer
communication, and so on
...

(2) By looking at the software from the same perspective, you can more easily map the
white-box information you gain to the black-box cases you‘ve already written
...
Data includes all the variables, constants, arrays, data structures,
keyboard and mouse input, files and screen input and output, and I/O to other devices
such as modems, networks, and so on
...
h>
(2) void main()
(3) {
(4) int i , fact= 1, n;
(5) printf(―enter the number ―);
(6) scanf(―%d‖,&n);
(7) for(i =1 ;i <=n;i++)
(8) fact = fact * i;
(9) printf (―the factorial of a number is ‖%d‖, fact);
(10)
}
(11)
The declaration of data is complete with the assignment statement and the variable declaration
statements
...


(Code
coverage
testing
with
Example:
4 marks,
Path
coverage
and
condition
testing: 2
marks
each
...
The most straightforward form of code coverage is called statement coverage or line
coverage
...
If you‘re monitoring statement coverage while you test your software, your goal is to
make sure that you execute every statement in the program at least once
...
With line coverage the tester tests the code line by line giving the relevant output
...
h>
(2) void main()
(3) {
(4) int i , fact= 1, n;
(5) printf(―enter the number ―);
(6) scanf(―%d‖, &n);
(7) for(i =1 ;i <=n; i++)
(8) fact = fact * i;
(9) printf (―the factorial of a number is ‖%d‖, fact);
(10) }

Page 23 of 32

ii)
1
...

3
...


5
...

7
...

c)

Ans:

Condition Coverage
Attempting to cover all the paths in the software is called path testing
...

To check all the possibilities of the boundary and the sub boundary conditions and it‘s
branching on those values
...

Every branch (decision) taken each way, true and false
...

Just when you thought you had it all figured out, there‘s yet another complication to path
testing
...


List any four features of client server application
...


i) This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front-end and backend
...
E
...

iii) The backend for these applications would be MS Access, SQL Server, Oracle, Sybase,
MySQL, Quadbase
...

The approaches used for client server testing are
1
...
GUI Testing - Characteristics:
i) GUI is a hierarchical, graphical front end to the application, contains graphical objects
with a set of properties
...

iii) It has capabilities to exercise GUI events like key press/mouse click
...

v) To check the GUI representations to see if they are consistent with the expected ones
...

2
...
A test plan document is
prepared that acts as a guide to the testing process to have the complete test coverage
...


(Client
Server
Testing: 4
marks,
Approach
es : 4
marks, 1
mark
each)

Page 24 of 32

3
...


There are two major Functional Testing techniques as shown below:

4
...
It can
be of two types - forward compatibility testing and backward compatibility testing
...

16
Attempt any FOUR of the following:

6
...
Describe any two of them
...
It is also termed ‗desk checking/verification
/white box testing‘
...
Static technique is so named because it involves no execution of code, product,
documentation, etc
...

Dynamic Testing: Dynamic testing is a validation technique which includes dummy or actual
execution of work products to evaluate it with expected behavior
...
The testing methods evaluate the product
with respect to requirements defined, designs created and mark it as ‗pass ‗or ‗fail‘
...

Operational techniques: Operational techniques typically include auditing work products and
projects to understand whether the processes defined for development /testing are being
followed correctly o not, and also whether they are effective or not
...
Operational technique may include smoke
testing and sanity testing of a work product
...
5
marks
each)

Page 25 of 32

OR

The various techniques to detect defects are
a) Quick attacks
...
Strengths
 The quick-attacks technique allows you to perform a cursory analysis of a system in a
very compressed timeframe
...

 The skill is relatively easy to learn, and once you've attained some mastery your quickattack session will probably produce a few bugs
...

 They can help you to make a rapid assessment
...

 If your attacks don't yield any defects, you may have some confidence in the general,
happy-path functionality
...
Weaknesses
 Quick attacks are often criticized for finding "bugs that don't matter"— especially for
internal applications
...

b) Equivalence and Boundary Conditions
i
...

 They also provide a mechanism for us to show that the requirements are "covered"
...

Weaknesses
 The "classes" in the table in Figure 1 are correct only in the mind of the person who chose
them
...

c) Common Failure Modes
i
...

 If your team is new, or you haven't previously tracked bugs, you can still write down
defects that "feel" recurring as they occur—and start checking for them
...

Weaknesses
 In addition to losing its potency over time, this technique also entirely fails to find "black
swans"—defects that exist outside the team's recent experience
...
), the riskier the project will be—and, at the same time, the less
valuable this technique will be
...

Strengths
 Mapping out the application provides a list of immediate, powerful test ideas
...

 Once you have the map, you can have other people draw their own diagrams, and then
compare theirs to yours
...

ii
...
"
 Drawing a diagram won't find these differences, and it might even give the team the
illusion of certainty
...

e)

Use Cases and Soap Opera Tests
Use cases and scenarios focus on software in its role to enable a human being to do
something
...
Strengths
 Use cases and scenarios tend to resonate with business customers, and if done as part of
the requirement process, they sort of magically generate test cases from the requirements
...
Soap opera
tests offer more power, and they can combine many test types into one execution
...
Weaknesses

Soap opera tests have the opposite problem; they're so complex that if something goes
wrong, it may take a fair bit of troubleshooting to find exactly where the error came from!
f) Code-Based Coverage Models
Imagine that you have a black-box recorder that writes down every single line of code as
it executes
...
Strengths
Page 27 of 32

 Programmers love code coverage
...

 Meanwhile, looking at the code that isn't covered also can yield opportunities for
improvement and bugs!
ii
...

 After installing the tool, most people tend to focus on statement coverage—the least
powerful of the measures
...

 Having code-coverage numbers can be helpful, but using them as a form of process
control can actually encourage wrong behaviours
...

g) Regression and High-Volume Test Techniques
 People spend a lot of money on regression testing, taking the old test ideas described
above and rerunning them over and over
...

i
...

 Likewise, if the software deliverable is a report written in SQL, you can hand the problem
to other people in plain English, have them write their own SQL statements, and compare
the results
...

For a pacemaker or a missile-launch device, finding those issues can be pretty important
...
Weaknesses
 Building a record/playback/capture rig for a GUI can be extremely expensive, and it might
be difficult to tell whether the application hasn't broken, but has changed in a minor way
...

 While some software projects seem ready-made for this approach, others
...

 You could waste a fair bit of money and time trying to figure out where your project falls
...
(Any four points)

Ans:

(Any four
points :1
mark
each)

OR

Quality Assurance:
i
...

ii
...
Quality Assurance is fundamentally focused on planning and documenting those processes
to assure quality including things such as quality plans and inspection and test plans
...
Quality Assurance is a system for evaluating performance, service, of the quality of a
product against a system, standard or specified requirement for customers
...
Quality Assurance is a complete system to assure the quality of products or services
...
It is a way of
management
...
A part of quality management focused on fulfilling quality requirements
...
The operational techniques and activities used to fulfill requirements for quality
...
Quality Control on the other hand is the physical verification that the product conforms to
these planned arrangements by inspection, measurement etc
...
Quality Control is the process involved within the system to ensure job management,
competence and performance during the manufacturing of the product or service to ensure
it meets the quality plan as designed
...
Quality Control just measures and determines the quality level of products or services
...
Here are some guidelines:
i
...

 Do you mean ‗Click Button B‘ or ‗Press ALT+B‘ or ‗Focus on Button B and click
ENTER‘
...
‖ Understanding all the paths at
once will be difficult
...
‖ You can, of course,
mention elsewhere in the report that ―D can also be got if you do ‗B and Y‘ or ‗C and Z‘
...
‖ What does the ‗it‘ stand for? ‗Z‘ or, ‗Y‘, or ‗X‘ or ‗Application A‘?‖
ii
...
In other words, do not be lazy
...

iii
...
‖
 Stick to the facts and avoid the emotions
...
Reproduce the defect:
 Do not be impatient and file a defect report as soon as you uncover a defect
...

v
...

 Review it at least once
...


(Any four
points :1
mark
each)

d)

4M

What are the things that test case specification shall identify?

Ans:
1
...
Each test case
should aim to evaluate the operation of a key element or function of the system
...
Failure of a test case, depending upon the severity of the failure, would be catalogued as
part of the overall evaluation of the suitability of the system for its intended use
...
Test cases can start with a specific ‗form‘ that allows operator entry of data into the
system
...

4
...


(1 mark
each, or
any
relevant
point)

Page 30 of 32

e)

Describe any four testing approaches of web application
...

Web Application Testing - Techniques:
(1) Functionality Testing - The below are some of the checks that are performed but not
limited to the below list:
Verify there is no dead page or invalid redirects
...

Wrong inputs to perform negative testing
...

Verify the data integrity
...

Test the navigation and controls
...

Check for user intuition
...

(4) Compatibility testing- Compatibility testing is performed based on the context of the
application
...

(5) Performance testing - Performed to verify the server response time and throughput under
various load conditions
...
Load testing will result in measuring important business
critical transactions and load on the database, application server, etc
...

Stress testing - It is performed to find the upper limit capacity of the system and also to
determine how the system performs if the current load goes well above the expected
maximum
...
During soak tests the parameters
such as memory utilization is monitored to detect memory leaks or other performance
issues
...

Spike testing -Spike testing is performed by increasing the number of users suddenly by a
very large amount and measuring the performance of the system
...

(6) Security testing - Performed to verify if the application is secured on web as data theft
and unauthorized access are more common issues and below are some of the techniques
to verify the security level of the system

---