error. It is an anomaly in the software that may cause it to behave
incorrectly and not according to its specification
Failure : A failure is the inability of a software system or
component to perform its required functions within specified
performance requirements
1.Graph-based Testing Methods
Black-box methods based on the nature of the relationships (links)
among the program objects (nodes), test cases are designed to
traverse the entire graph
Transaction flow testing (nodes represent steps in some transaction
and links represent logical connections between steps that need to be
validated)
Finite state modeling (nodes represent user observable states of the
software and links represent transitions between states)
Data flow modeling (nodes are data objects and links are
transformations from one data object to another)
Timing modeling (nodes are program objects and links are sequential
connections between these objects, link weights are required
execution times)
2.Equivalence Partitioning
Black-box technique that divides the input domain into classes of
data from which test cases can be derived
An ideal test case uncovers a class of errors that might require many
arbitrary test cases to be executed before a general error is
observed
Equivalence class guidelines:
If input condition specifies a range, one valid and two invalid
equivalence classes are defined
If an input condition requires a specific value, one valid and
two invalid equivalence classes are defined
If an input condition specifies a member of a set, one valid
and one invalid equivalence class is defined
If an input condition is Boolean, one valid and one invalid
equivalence class is defined
3.Boundary Value Analysis
Black-box technique that focuses on the boundaries of the input
domain rather than its center
BVA guidelines:
If input condition specifies a range bounded by values a and b,
test cases should include a and b, values just above and just
below a and b
If an input condition specifies and number of values, test
cases should be exercise the minimum and maximum numbers, as
well as values just above and just below the minimum and
maximum values
Apply guidelines 1 and 2 to output conditions, test cases
should be designed to produce the minimum and maxim output
reports
If internal program data structures have boundaries (e.g. size
limitations), be certain to test the boundaries
4.Comparison Testing
Black-box testing for safety critical systems in which independently
developed implementations of redundant systems are tested for
conformance to specifications
Often equivalence class partitioning is used to develop a common set
of test cases for each implementation
5.Orthogonal Array Testing
Black-box technique that enables the design of a reasonably small set
of test cases that provide maximum test coverage
Focus is on categories of faulty logic likely to be present in the
software component (without examining the code)
Priorities for assessing tests using an orthogonal array
Detect and isolate all single mode faults
Detect all double mode faults
Multimode faults
6.Specialized Testing
Graphical user interfaces
Client/server architectures
Documentation and help facilities
Real-time systems
Task testing (test each time dependent task independently)
Behavioral testing (simulate system response to external
events)
Intertask testing (check communications errors among tasks)
System testing (check interaction of integrated system software
and hardware)
7.Advantages of Black Box Testing
More effective on larger units of code than glass box testing
Tester needs no knowledge of implementation, including specific
programming languages
Tester and programmer are independent of each other
Tests are done from a user's point of view
Will help to expose any ambiguities or inconsistencies in the
specifications
Test cases can be designed as soon as the specifications are complete
8.Disadvantages of Black Box Testing
Only a small number of possible inputs can actually be tested, to
test every possible input stream would take nearly forever
Without clear and concise specifications, test cases are hard to
design
There may be unnecessary repetition of test inputs if the tester is
not informed of test cases the programmer has already tried
May leave many program paths untested
Cannot be directed toward specific segments of code which may be very
complex (and therefore more error prone)
Most testing related research has been directed toward glass box
testing
Assure that leap years are validated correctly & do not cause
errors/miscalculations.
Assure that month code 00 and 13 are validated correctly & do not
cause errors/miscalculations.
Assure that 00 and 13 are reported as errors.
Assure that day values 00 and 32 are validated correctly & do not
cause errors/miscalculations.
Assure that Feb. 28, 29, 30 are validated correctly & do not cause
errors/ miscalculations.
Assure that Feb. 30 is reported as an error.
Assure that century change is validated correctly & does not cause
errors/ miscalculations.
Assure that out of cycle dates are validated correctly & do not cause
errors/miscalculations.
Numeric Fields
Assure that lowest and highest values are handled correctly.
Assure that invalid values are logged and reported.
Assure that valid values are handles by the correct procedure.
Assure that numeric fields with a blank in position 1 are processed
or reported as an error.
Assure that fields with a blank in the last position are processed or
reported as an error an error.
Assure that both + and - values are correctly processed.
Assure that division by zero does not occur.
Include value zero in all calculations.
Include at least one in-range value.
Include maximum and minimum range values.
Include out of range values above the maximum and below the minimum.
Assure that upper and lower values in ranges are handled correctly.
Alpha Field Checks
Use blank and non-blank data.
Include lowest and highest values.
Include invalid characters & symbols.
Include valid characters.
Include data items with first position blank.
Include data items with last position blank.
Every testing project has to follow the waterfall model of the testing
process.
The waterfall model is as given below
1.Test Strategy & Planning
2.Test Design
3.Test Environment setup
4.Test Execution
5.Defect Analysis & Tracking
6.Final Reporting
According to the respective projects, the scope of testing can be tailored,
but the process mentioned above is common to any testing activity.
Black-Box testing technique:
This technique is used for testing based solely on analysis of
requirements (specification, user documentation.). Also known as functional
testing.
White-Box testing technique:
This technique us used for testing based on analysis of internal
logic (design, code, etc.)(But expected results still come requirements).
Also known as Structural testing.
Before starting testing we need to follow these steps:-
1)Get requirements.
2)Make test Plan
3)write test cases
4)Build test bed.
5)Get all required software tools.
6)Divide work b/w team members.
5)Finally start testing.
6)Execute test case
7)Report bugs
8)retest fixed bugs
9)generate test report
Test plan can be defined as a document that describes the scope, approach,
resources and schedule of intended test activities. The main purpose of
preparing test plan is that every one concerned with the project are in
synchronized with regards to scope, deliverables, deadlines and response
for the project.
Test planning can and should occur at several levels. The first plan to
consider is the Master Test Plan. The purpose of the Master Test Plan is to
consider testing at all levels (unit, integration, system, acceptance,
beta, etc.). The Master Test Plan is to testing what the Project Plan is to
the entire development/testing effort.
General contents of a test plan:
Purpose:
This section should contain the purpose of preparing the test plan.
Scope:
This section should talk about the areas of the application which are to be
tested by the QA team and specify those areas which are definitely out of
the scope.
Test approach :
This would contain details on how the testing is to performed and whether
any specific strategy is to be followed.
Entry criteria:
This section explains the various steps to be performed before the start of
test (i.e) pre-requisites.
E.g. Environment setup, starting web server/ application server, successful
implementation of latest build etc.
Resources:
This list out the people who would be involved in the project and their
designation etc
Tasks and responsibilities:
This talk about the tasks to be performed and the responsibilities assigned
to the various members in the project.
Exit criteria:
This contains tasks like bringing down the system or server, restoring
system to pre-test environment, database, refresh etc.
Schedules/ Milestones :
This section deals with the final delivery date and the various milestone
dates to be met in the course of project.
Hardware/ software requirements :
This section contains the details of system/server required to install the
application or perform the testing, specific s/w that needs to be installed
on the system to get the application running or to connect to the database,
connectivity related issues etc.
Risks and mitigation process :
This section should list out all the possible risks that can arise during
the testing and mitigation plans that the QA team plans to implement incase
the risk actually turns into a reality.
Tools to be used :
This would list out the testing tools or utilities that are to be used in
the project.
E.g. Winrunner, QTP, Test Director PCOM etc.
Deliverables :
This section contains various deliverables that are due to the client at
various points of time. i.e. daily, weekly, start of project, end of
project etc. these could include test plans, test procedures, test
matrices, status reports, test scripts etc. templates for all these also be
attached.
Annexure :
This section contains the embedded documents or links to document which
have been/will be used in the course of testing. E.g. Templates used for
reports, test cases etc. reference documents can also be attached here.
Sign off :
This section contains the mutual agreement between the client and QA team
with both leads/ managers signing off their agreement on the test plan.
