SOFTWARE TESTING

Click to edit Master subtitle style

4/23/12

ABBRIVATIONS
T.E AUE

TEST ENGINEER APPLICATON UNDER TEST

4/23/12

DEFINATION AND GENERAL POINTS

OR SOFTWARE IN OTHE WORDS VALIDATING AND VERIFYING PARTICULAR PROJECT OR PRODUCT TO MAINTAIN QUALITY . , USER FRIENDLY .

WHAT IS QUALITY: JUSTIFICATION OF CUSTOMER REQUIREMENTS SOFTWARE QUALITY: DEPENDS ON THREE FACTORS

1. BUDGET/COST 2. INTIME RELEASE 3. REALIABILITY .

RESPONSEBILE , (T.E) IS RESPONSIBLE FOR RELIABILITY RESULT IN APPLICATION UNDER TEST(A.U.T)

DEFECT: DEVIATION BETWEEN EXPECTED RESULT TO ACTUAL T.E NEED TO TEST CLIENT REQUREMENTS APART FROM THAT HE

IS NOT SUPPOSED TO CHANGE ANY DATA OR CODING OR PROGRAM 4/23/12

TERMINOLOGY
CODING: writing a programs using

programming language or scripting languages in order to develop the application will be tested here

Testing : the developed code by developer Defect reporting: while Testing if they found

any defect in application those will be reported back to developer

Debugging: bugging the defect (digging the

defect )i.e, identify the root cause for a defect

4/23/12 Defect fixing: Modifying source code of the

terminology
Project: project is a some thing that is

developed based on particular customer requirements (web page) based on particular company requirements (Yahoo) estimation and signing off

Product: product is some thing developed

Bidding the project: requesting proposal , Kick of meeting: initial meeting conducted

by the company soon of the sign off the project in order to discuss overview of the project .(managers, customer 4/23/12

Manual and Automation Testing Manual testing: It is a process in which all

the phases of software testing life cycle like Test plan, Test Design, Test execution , Result analyses , Bug tracking and reporting are accomplished successfully with human efforts accurate, parallel operations are not possible, testing a functionality continually with same interest is not possible.

Draw backs: Time consuming, Tiredness, in-

Automation: It is a process which all the

drawbacks of manual testing are addressed properly and provide speed and accuracy in 4/23/12 order to perform proper testing. It is not replacement of Manual testing it is

Skill set for Q.A test engineers concepts Manual testing

Finance

4/23/12

Manual testing
Roles and responsibilities of Test Engineer Software Development life Cycle (SDLC) Quality Assurance (0r) Quality Control SDLC models Testing Methodologies

box

1. white box 2. Black box 3. Gray

Testing levels in S.D.L.C

1. Unit testing 2. Integration Testing 3. System Testing

Roles and responsibilities of T.E

requirement document like B.R.S or F.R.S module

Prepare test cases for manual testing Create automation test script (if applicable) Execute test case and automation test

scripts
Defect reporting and prioritize defects Participating in re testing and regression 4/23/12

testing

SDLC

What is software:

*set of instructions programs documents to perform particular task types software is categorized in to two

1. system software 2. Application software

output to system)

Application software: operations or

functionalities based on user inputs applications

Application software (A.S)is called front end 4/23/12

SDLC
SDLC: it is a process of developing

software project / product to fulfill the client requirements with in the specified cost and time life cycle are:

Phases involved in software development

1. requirement collection 2. Analysis phase 3. Design 4. Coding 5. Testing 6. Delivery and maintance
For each and every phase we need to know

what is the task, who is the role person , 4/23/12 what is process, what is proof (end

SDLC PHASES
REQ. PHASE TASK: getting requirements from client ROLE: Business Analyst , Engagement

manager

PROCESS: Select the technology and

environment

PROOF:[Link]

Analysis phase TASK: Detailed functionality document of

B.R.S document

4/23/12

ROLE: System Analyst

SDLC PHASES
DESIGNING PHASE TASK: High Level Design (H.L.D), Low Level

Design (L.L.D)

ROLE: chief Architecture Design

Engineer(c.a.e) & Team Leads(T.L)

requirements in to modules by using unified modeling language L.L.D : T.L will divide the module in to sub
4/23/12 modules by using (u.m.l.d)

SDLC PHASE
TESTING PHASE: TASK: Test the developed build ROLE: Test Engineer PROCESS: after receiving required

document T.E will try to understand , during understanding the document they raise doubts and mentioned into clarification note document (C.N.D), this document will send to business analyst for clarification, after successful test cases. review , T.E will4/23/12 writing start

SDLC
DELIVERY AND MAINTAINCE PHASE: TASK: Deliver the application to the client ROLE: Deployment Engineer/ Installation

Engineer
PROCESS: Deployment engineer will deploy

application

in client environment successfully and hand over the original software to client
PROOF: close the official agreement
4/23/12

STEPS IN PROJECT

4/23/12

Common problems in SDLC

Unclear requirements (or ) incomplete requirements to develop application

Un realistic schedule: If too much of work is assigned in short span of time will be problem

Inadequate testing : It is difficult to estimate how much testing is sufficient to validate the application

Miscommunication: If developer doesnt know exact requirements their will be problem to develop the application

WHEN DO DEFECTS WILL ARAISE : 1. wrong requirements wrong project / product 4/23/12 2. Mistakes in Design Design defects

Q.M: prevventing defects during

QUALITY MANAGEMENT

development process and to

ensure there are no defects in final products

4/23/12 Q.C: Team involves after product is built. It

identifies the

It is a process ASSURANCE

QUALITY

QUALITY CONTROL It is product

oriented

oriented

It is defects

It is defects

preventive approach
It involves

detective and ensure those defects has to be fixed

throughout life cycle are the examples for Q.A

product is built
s/w testing is an

Reviews, auditing

example for Q.C

SDLC MODLES
Depending up on functionality and need of

client we can adopt any one of the following SDLC models to develop the application.
v waterfall model v iterative model v v v v

Prototype model spiral model Rad model

fish model

Its preferable for small applications Clear requirements and routine type of

Water fall model

projects model

It developed in linear sequential waterfall

4/23/12

Disadvantage of waterfall model:

There is no feed back mechanism between the phases are identified at latest stage of testing.
During development process it

wont allow any dynamic change request from the client.

Iterative model :
For big projects& requirements are

not clear
It developed in terms of increments

those has to be delivered to the client after testing . 4/23/12