Testing

1. What is Software Testing?

Process of validating and verifying a software program/ application/ product

 to check that it works as per requirements.

 to detect errors or defects
 to ensure it is working as per user requirements

Software testing is a process of executing a program or application with the intent of finding the
software bugs.

2. What is Manual Testing?

Software testing where tester manually executes test cases without any automation tool

New application must be manually tested before its testing in automation

3. Why we need testing?

 Point out all errors/defeats by developer
 Customer satisfaction & customer reliability
 Good performance fast access of software
 Accurate & desired results
 Quality product & meet customer requirement
 Gain the confidence of customer

4. SDLC (Software Development Life Cycle)

It’s a predefined process

 to develop software or application.

 ensures good software is built.

Benefits of SDLC

It helps to develop a product

 high quality
 cost effective to maintain and enhance
 works in multiple environments
(Environment refers to different operating systems, Different Hard ware
configurations, Different Browsers etc.)
 produces accurate and consistent results.
Different SDLC models are:

1.Water Fall Model:

 first SDLC model.

 It is the oldest and mother of all development models.
 linear development model.

Phase 1 (Requirement Collection)

People Involved: Business Analyst, Customer, End Users.

 all the requirements required to develop the software are collected.

 BA (Business Analyst) will travel to customer place to collect requirements.
 There he interacts with Customers and end users who are going to use the software to
collect requirements.

There are different ways to collect requirements.

  One to One interaction with customer and end user if the number of end users is less.
 By arranging workshops for all end users and customers.
 By telephonic meetings
 By video sessions

Once all the requirements are collected he will document all the requirements and that document
is called as CRS (Customer requirement Specification).

Once this is done BA will travel back to Organization and starts with Analysis.

Phase 2 (Analysis/Feasibility Study):

People Involved: BA, TA, PM, HR, Finance Team

BA :

 analysis of requirements.
 remove all the conflicts in the requirements by interacting with customers.
 filter out all the unwanted requirements.
 With all these analysis BA will come with exact requirements and translate them in to
SRS (Software Requirement Specification).
 SRS is the document which will have requirements in software language. This will be
better understood by software people.

TA:

 Once the SRS is done it is given to TA (Technical Architect). TA is technical expert.

 know the technology in and out.
 By going through SRS, TA will have clear picture of end system.
 decide the technology that is been used to develop the system or software.

PM:

 Once the technology is decided by TA, now PM (Project manager) comes into picture to
setup the team which is going to build the application.
 PM will ask HR (Human Resource) people to look for resources who are required for that
project.

HR:

HR people are responsible for providing the skilled resources required for that project.
Finance team:

 deal with finance matters like cost estimation for technology used for developing the
application, cost estimates for resources etc.
 They will make sure that estimated budget is not running beyond the limit.
 After completing all analysis and feasibility study third phase will start.

Phase 3 (Design):

People Involved: TA, senior developers.

In this phase designs are done for the SRS. Here we have two types of designs

HLD (High level Design):

 Done by TA.
 High level design contains picture of overall system.
 defines the interface between different modules in the system.

Ex: Here requirement is to transfer money form Account A to B. For this below is the high level
diagram.
LLD (Low level Design):

 done by senior developers.

 High level design will further drill down to create low level designs.

Ex: low level design for above shown login page.

This design will give more details compared to HLD. By looking at this developers come
to know that Login page will have above shown objects and it makes easy for them to
develop the application. Similar kind of designs is done for Transfer module and logout
module as shown in the HLD. With all designs done coding phase will be started.

Phase 4 (Coding):
People Involved: Developers
In this phase developers will develop the application. Once the development is done the
application is moved to testing phase. With developed application testers will start
testing.

Phase 5 (Testing):
People involved: testers
In this phase testers will receive the application form developers and start testing. They
will do all kind of testing. All defects identified will be reported to developers through
bug tracking tool. Once complete testing is done application is move to implementation
phase where it is installed into the live environment.
 Phase 6(Implementation):
People Involved: Build Installation Team
Once testers completes the testing and gives sign off, Build installation team is going to
take the application and they are going to install it into customers place that is Live
environment.

Phase 7 (Maintenance):
People involved: Customers and end users
Once the application is installed into the live environment customers and end users will
start using that application. At that point of time they may find some defects in the
application. Those defects will be reported back to developers. Developers are going to
fix those defects and testers are going to test them after they fix them. Fixing and testing
the defects found in live environment is called maintenance.
Note: The way end users uses the application is different form how testers uses it to
test.

Advantages of Water fall model

1. After design phase requirements are frozen. This makes to develop a robust product.
2. It is easy to understand and use.
3. In this model phases are processed and completed one at a time. Phases do not overlap.
4. Waterfall model works well for smaller projects where requirements are very well
understood

Disadvantages of water fall model

1. Requirements and designs are not tested

2. Changing requirements are not accepted after design phase
3. No working software is produced until last phase of cycle.
4. Poor model for long and complex projects
5. Back tracking is not possible