1.

Test Design Techniques

There are four types of test design techniques.

 Boundary Value Analysis (BVA)

 Equivalence Class Partition (ECP)
 Cause and Effect Graphing (CEG)
 Error Guessing
 Boundary Value Analysis (BVA)
BVA is used to reduce the number of test cases based on the inputs.
Consider the object age and its range is from 0-150 and should change in intervals of 2 months. In
this case we can use BVA. Taking random values from the mentioned range and to validate the
output.
 Equivalence Class Partition (ECP)
It is also used to reduce the number of test cases based on the inputs.
Consider the object age and its range is from 0-150. Instead of giving multiple inputs here, we can go
with the values as “(lower limit-1), (middle value), (upper limit+1)”. So here the inputs can be, “(-1),
(75), (151)”.
 Cause and Effect Graphing (CEG)
After completing CEG only, BVA and ECP are done. There are multiple methods of CEG. Here we use,
based on the inputs, outputs are validated.
 Error Guessing
It is used to find the components of software where defects might be present. It is mostly done by
experienced testers who can use their past experience to find defects in software. Error guessing has
no rules for testing, it only uses the testers.

2. BBT & WBT

WHITE BOX TESTING TECHNIQUE BLACK BOX TESTING TECHNIQUE

It is done to check the internal structure of the It is done to check the external functionality of the
coding where test cases are executed on it program where test cases are written and
executed on it
It is done by developer It is done by tester
Unit testing is done here Functional and non-functional testing are done
here
Test cases are written based on the FRS Test cases are written based on the SRS

The test cases for WBT are written first, however, the test cases for BBT are only executed first.

3.SDLC software Development life cycle

SDLC- Software Development Life Cycle, it is a protocol followed by monitoring to

bringout the project in good quality.
It consist of 6 faces:
 1. Requirements gathering
2. Planning & analyst
3. Designing
4. Testing
5. Implementation support
6. Maintenance

1.Requirements gathering:
Requirements should be gathered from the client environment, and the document
like SRS & BRS will be performed, and project will be analyzed the client place.
2.Planning & analyzing:
Strategies will be performed by the clients and starting of the project, and risk will
be analyzed, mitigation will be performed by this project

3. Designing:
This is the face where the project design will be performed, where as the hardware
selection and software selection, architecture design and high level and low level activities will
be performed,
Hardware and software activities will be performed by system analyst, and also
architecture design will be performed,
Architecture design:
A structure given to the application according to its usage
It should be categorize the 4 types:
 Single tier
 Two tier
 Three tier
 Multi tier

Single tier: In the type all the layers are available from this application,

For eg: desktop application, word, excel,etc..

Two tier: In this type should contain the only one server and many clients

Three tier: In this type should contain the application server and web server and database, it should
store and retrived the datas from the database.

Multi tier: In this should contain single tier and two tier and three tier and all this types will be in
single application

Hardware and software activities will be performed by: software architect, Technical writer,
Technical designer, system analyst, and business analyst,
 And higher module should be stipulated in the small projects, where know as project hierarchy

Project hierarachy means:

Projects-> Modules -> sub modules->screens -> scenarios ->functions ->objects

Scenario:

A brief description about an even or even what is the screen as the application has to perform

Functional requirement specification:

This document is prepared by the technical writer, it contain the details description above
the each and every individual objects and their functions, it is mainly used by the developers, codings
and also used to write the testcase for unit testing

Codings: Developers will be develop the codings by using FRS Document.

Testing: External functions will be tested by the testers by by using SRS (Software requirement
specitication) document used to write the testcase

Implementation & Maintenance: application will be implemented by the customer support

environment by using properly. And maintenance will be done to the maintenance team.

4.Test scenario:
An event what the screen has to perform and brief description about the event is called
test scenario.

5.Test data:
An input is given to a field to validate its functionalities is called test data. It is
catagorized into 4 types as follows
1.valid
2.invalid
3.illegal
4.blank

6.Levels of Testing:

In consist of 4 types of testing:

 Unit level of testing
 Integration level of testing
 System level of testing
 Acceptance level of testing
Unit levels of testing: It is 1st level of testing which should be executed document developers by using
FRS document, where the internal codings will be combined with inputs and validate its outputs,

Integration level of testing: It is the 2nd level of testing, it will be performed after unit testing is
completed, it should be performed by both developers and testers,

Developers will be performed by the structural integration b/w the codings, and Testers will be
performed by functions and communication interface b/w the components or modules and also
between the application

Top down approach:

Developers will using this approach by develop the Stubs and drivers

It is done to the higher level module or the lower level module, it contain the 2 method ie:
Depthwise and breadhwise.

Stubs: It is partially incompleted portion of a build.

Drivers: This should be contain the transport datas from the dummy database or
original database, dummy database is as called drivers.

Bottom up approach:

Testers will using this approach by contain the objects and the higher module

Sandwich approach: combation of both top down and bottom up approach will be used to identify the
missing links and high module, time consumtion is disadvantage

Big bang approach: combaining all the modules or components together to form the single application
and communication interface b/w the entire module are the testing functions

System level of testing: combination of the modules or components together to form the single
application , check whether the appilication is used satisfactorily about the requirement.

Acceptance level of testing: it is done to check whether the application working satisfactorily about
customer acceptance criteria.

It contain two type: alpha testing : validation of the application has to performed developer
environment with real time inputs:

Beta testing: validation of the application has to performed customer s environment

with real time inputs.
7. VERIFICATION AND VALIDATION.

Verification means Testing the software correctly implements the specific function in that phase.It
performs each and every stage of SDLC. "Are we building the product right” .The software should
conform to its specification. It ensures the product is designed to deliver all functionality to the
customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements
and specifications; this can be done with checklists, issues lists, and walkthroughs and inspection
meetings.

Validation Means to ensure the software that satisfied customer's requirements.It ensures that
functionality, as defined in requirements, is the intended behavior of the product; validation typically
involves actual testing and takes place after verifications are completed. "Are we building the right
product”. The software should do what the user really requires.

8. Acceptance criteria

A prioritized set of criteria that the solution must meet before it passes through to the next phase or
goes into production in the case of customer acceptance criteria

9. What is the difference between build and release?

Build: It is a number given to Installable software that is given to testing team by the development team.

Release: It is a number given to Installable software that is handed over to customer by the tester or
developer.

10. What is bug leakage and bug release?

Bug release is when software or an application is handed over to the testing team knowing that the
defect is present in a release. During this the priority and severity of bug is low, as bug can be removed
before the final handover.

Bug leakage is something, when the bug is discovered by the end users or customer, and missed by the
testing team to detect, while testing the software
11. What ifs the difference between defect, error, bug, failure, fault?
Error:
“Is an undesirable deviation from requirements?”
Any problem or cause for many problems which stops the system to perform its
Functionality is referred as Error
Bug:
Any Missing functionality or any action that is performed by the system which is not
Supposed to be performed is a Bug.
“Is an error found BEFORE the application goes into production?”
Any of the following may be the reason for birth of Bug
1. Wrong functionality
2. Missing functionality
3. Extra or unwanted functionality
Defect:
A defect is a variance from the desired attribute of a system or application.
“Is an error found AFTER the application goes into production?”
Defect will be commonly categorized into two types:
1. Defect from product Specification
2. Variance from customer/user expectation.
Failure:
Any Expected action that is supposed to happen if not can be referred as failure or we can
say
Absence of expected response for any request.
Fault:
This generally referred in hardware terminologies. A Problem, which cause the system not
to perform its task or objective.