completed slides

Example For Quality

Enter Text here:

abc

ok

Please enter validdata

Enter Text here:

abc123

OK

Please enter valid data

Summary for above two Examples

The Application should be prepared according to client’s requirements and it should be User-Friendliness.

Project taken by the Organization in a procedural way...

BOA

Requirements

TCS

Infosys

IBM

Tech Mahindra

DSS

RFP

Client

Contents of RFP

Full form of RFP : Request for Proposal Document

Contents :

1) Introduction

2) Cost

3) Experience

4) Resources

5) Approach

6) Methodologies ....etc

BOA DSSSelected

The Official People of both the companies will meet tofinalize the agreement. For finalizing they will sign onDocuments.

SLA Service level Agreement

SOW Statement of work

SDLC Phases

1) Initial or Requirement phase

2) Analysis Phase

3) Design Phase

4) Coding Phase

5) Testing Phase

6) Release & Maintenance

Where exactly Testing will be started

1) UnConventional Testing

2) Conventional Testing

Unconventional Testing : The person will test the application whether this application is going according to company standards are not. Herethe person is QA(Quality Analyst)

Conventional Testing : The person will test the application whether thisapplication is according to clients requirements or not. Here the personis Software Test Engineer.

Testing Methodologies : There are two types of testing methodologies.

1) Black Box Testing

2) White Box Testing

There is one more which is derived from above two methodologies.i.e Gray Box Testing.

Black Box Testing : The people who performs testing only on thefunctional part of the application is called as Black Box test Engineers.

White Box Testing : The people who test the structural part of theapplication i.e Coding part is known as White Box Testing.

> Usually developers are White Box Test Engineers.

Gray Box testing : The people who test the Functional and Structuralpart of the application is known as Gray Box Testing.

Levels of Testing

Different Levels of Testing are :

1) Unit Level Testing2) Module level Testing3) Integration level Testing4) System level Testing5) User acceptance Testing

Unit Level Testing :

Unit is defined as a Smallest part of the program in an application.

These will be performed by developers where they will test each and every unit of an application(i.e coding) and combination of units.

Different ways of unit testing are :

1) Structural Testing

2) Conditional Testing

3) Branch Testing

Module Level Testing :

Combining more than one functionality to perform a major task of related feature to test is known as Module Level Testing

These will be performed by Software Test Engineers.

City

GOA

HYD

Others

SelectLocation here

: OK

Example 2

City

GOA

HYD

Others

SelectLocation here

: OK

Enter Location name : PUNE

OK

SelectLocation here

:

City

GOA

HYD

PUNE

Others

OK

3) Integration Level Testing :

Combining all the modules of a project by using different approaches. The approaches are :

1) Top-Down Approach2) Bottom- Up Approach3) Hybrid Approach4) Big bang Integration

1) Top-Down Approach : Combining the modules from top(i.e parent) level to bottom(i.e Child) level is known as Top-down Approach.

A

B C

D E F G

From top to Bottom

Parent Module

Stub

Stub : In Top-Down approach if any original module is replacedWith dummy module that module we will call it as Stub.

Bottom-Up Approach : Combining the modules from child level to parent level is known as Bottom-up approach.

A

B C

D E F G

Parent Module

Driver

Child Module

From Bottom to Top

Hybrid Approach : Combination of both the approaches is known asHybrid approach.

Big Bang Integration : Combining all the modules at a time after Preparing the modules is known as Big bang Integration.

System Level Testing : Testing each and every functionality of the application where we will perform all the types of testing is knownas system level testing.

Software Development Models

Water Fall Model or Linear Sequential Model

Initial

Analysis

Design

Coding

Testing

R & M

Phases

Cost

Cost of a bug phase by phase

Initial

Analysis

Design

Coding

Testing

R & M

When ever Requirements are addedIn the middle again the process Should start from first.

ENVIRONMENT

Present Layer

Database Layer

Applicati-on Layer

Request Request

ResponseResponse

Validations Appropriate data

Displaying data

There are 4 types of architectures :

1) 1-Tier Architecture2) 2-Tier Architecture3) 3-Tier Architecture4) n-Tier Architecture

Environment in the Organization for a project

D1 D2

D3

T1 T2

T3

P1

Dev Environment Test Environment Production Environment

Build 1 released

Build 1(Defects)

D1 D2

D3

T1 T2

T3

P1

Dev Environment Test Environment Production Environment

Build 1000 released

Build 1000 (No Bugs found)

Deploying Build 1000

Types of Testing

1) Build Verification Testing or Build Acceptance Testing or Sanity Testing

Conditions for accepting the Build :

1) Build Installation.2) Navigating through pages.3) Features Availability.4) Required connections are properly established or not.

If all these conditions are satisfied then we will continue withNormal testing.

Sanity Testing : After releasing the build the testing will be performed onsome major functionalities to accept the build is known as Sanity Testing.

Smoke Testing : Before releasing the build the developers will test the application that is known as Smoke testing.

2) Regression Testing : It is a type of testing in which one will perform testing on the already tested functionality again with there dependencies.

Usually we do it in two scenarios.

Whenever we raise the defects to the development department, once the next build is released we will test the defect functionality as well as the related functionality again and again.

Whenever some new features added (incorporated) to application, When next build is released to the testing department then all the related features of the new features will be tested once again.

Example for Regression Testing

Calculator

V1 1

V2 2

Res 3

ADD

SUB

MUL

V1 1

V2 2

Res 30

ADD

SUB

MUL

Clicking on SUB

V1 1

V2 2

Res 300

ADD

SUB

MUL

Clicking on MUL

Retesting :

Username : abc

Password : abc

OK Cancel

Username : abcd

Password : abcd

OK Cancel

Definition : Testing the application again and again with differentset of values is known as Retesting.

Alpha Testing : It is a type of user acceptance testing conducted in the software company by our test engineers in front of client to make him accept.

Example : Project or Product

Beta Testing : It is a type of testing conducted by the End users or third party experts or clients before releasing to Client is known as beta Testing.

Example : Product

Static Testing :

Usernane :

Passward :

Cancel

Login

Definition : Without performing any actions on the application while testing is known as Static Testing

Dynamic Testing : Here we will perform some actions on the application to test the functionality whether it is according to client requirement.

Example : Functionality Testing

Installation Testing :-It is a type of testing in which one will install the application into the environment by following the guidelines provided in the deployment document. In-order to come to a conclusion whether those guidelines are perfectly suitable for installing the application or not.

Compatibility Testing:-It is a type of testing in which one will install the application into the number of environments prepared with different combinations in-order to confirm whether the application is suitable with all those environments or not. Usually the type of testing is compulsory for products rather than projects.EX:- Testing the application with different browsers(Netscape Navigator, Mozilla Firefox, Internet explorer).