Testing for Freshers

In this blog i will help you in gaining some knowledge about Manual testing.
First of all i wanna tell you this my first blog. So Lets get started with Manual Testing.

First question that comes to mind is 
Q.what do you mean by Testing?
Ans.Testing - It basically means Quality Control and Quality Control measure the quality of product or software 
now questions comes

Q. What do you mean by Manual Testing?
Ans:-Manual Testing means testing a software manually to find the defects .The role of end user is played by the tester and use most of the features or functionality to ensure the correct behavior of the application

now we discuss about the SDLC
SDLC stands for SOFTWARE DEVELOPMENT LIFE CYCLE

Q. What is SDLC?
Ans:- SDLC is a process of building an application through different phases.
          Here The phases are 5 types, 
          they are: - Requirement Analysis, Design, Coding, Testing and Maintenance.

          

Lets Discuss about the phases of SDLC
1.Requirement Analysis -It basically deals with the concept what the customer wants?.This is the entry point of the software product.                                    This phase ends with an SRS(SYSTEM REQUIREMENT SPECIFICATION)

The Requirement Phase has three stages:
     1.1Problem Analysis
The goal of problem analysis is to obtain a clear understanding of the
requirements of the client and the users. This involves interviewing the client
and the end users. 

    2.1Requirement Specification(SRS)This is a result of a successful problem analysis. The SRS makes an Agreement between the user(client) of the system and the developer on what the software product will do.

    3.1Requirement Validation
Validation of requirement is necessary to fill out some small gaps in the SRS. It validates whether the requirement specification document does not have any error in it. The common errors that may occur are incorrect fact , inconsistency and ambiguity(where their is no meaning for the requirement).

2.Design - System analysis leads to design decision, which exactly determines how the system operates in terms of process, data, hardware, network infrastructures, user interface, and other important factors in the system environment

3.Coding- It is used to develop the product or software what customer asks for

4.  Maintenance - There are two goals of Maintenance in SDLC:
                1. Increase the ability of the software 
                 2.avoidance of failures.

Better Adaptability of the Software – SDLC’s idea of maintenance is very beneficial not only to the developers but also for the software itself.   With the use of available data, developers will learn something new.   In this account, they will be able to apply this knowledge to the software.

Although any developer would not wish for a problem, it poses a great opportunity to learn more about the industry and release updates to combat problems once and for all.  The end result of constant updates will be a better software that can adapt to the changing environment.   When a business spends thousands of dollars on project development, they expect more from the software.  Maintenance will ensure that the software will last for a very long time.

Avoidance of Failures – Maintenance does not only ensure that the problem will be fixed but maintenance should prevent the same event from happening again. Software will always have that “learning” property as long as they are handled well by the developers.   Developers will often work on the problem and at the same time give updates on the system to prevent failures.   It is essential for developers to release updates especially if the software is an important part of the business.

5.Testing - Testing used to ensure the correct behaviour of the application we are working on.

NOW,We will talk about the SDLC Models

There are 7 SDLC Models
1.Built & Fix Model
2.Waterfall Model
3.Iterative Model
4.Prototyping Model
5.Spiral Model
6.RAD Model
7.V-Model

Lets discuss each Model one by one

1.Built & Fix Model 

 This model is the worst model developing a project. In    this the product or software is built without proper specifications and design steps .In essence, the product is built and modified as many times as possible until it satisfies the client or customer.
the cost of using this model is really high 

2.Waterfall Model

   Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of Software development is divided into separate phases.

 The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible. of software development is divided into separate process phases.

3.Iterative Model

In this model the project is divided into the release or increments and a end product is obtained.

In this until and unless we deliver the 1st release or increment we cannot start with the 2nd release or increment of product

4.Prototyping Model

 The prototyping model is a system development method(SDM) in which a prototype (an early approximation of a final system or product) is built ,tested and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.

This model works best in scenarios where not all of the project requirements are known in detail ahead of time .It is an iterative ,trail and error process that take place b/w the developers and the users 

5.Spiral Model

Risk analysis is the main feature for Spiral Model.It is also known as spiral lifecycle model

The steps in the spiral model can be generalized as follows:

1. The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

1. A preliminary design is created for the new system.

1. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

1. A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second prototype; (3) planning and designing the second prototype; (4) constructing and testing the second prototype.

1. At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer's judgment, result in a less-than-satisfactory final product.

1. The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

1. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

1. The final system is constructed, based on the refined prototype.

1. The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime

6.RAD

RAD stands for Rapid Application Development Model

RAD is incremental software development process model that allows usable systems to be built in as little as 60-90 days, often with some compromises. The RAD model used for information systems development. The RAD model contains the following phases:

Business modelling

Data modelling

Proccess modeling

Application generation

Testing and turnover

7.V-Model

In V-model the testing begins as soon as possible in the project life cycle.It is always good practice to involve tester at earlier phases of product life cycle. There are variety of test activities need to be carried out before end of the coding phase.This activities should be carried out in parallel to the development activities so that testers can produce a set of test deliverable.

The V-model illustrates that testing activities (Verification and Validation) can be integrated into each phase of the product life cycle

As the word comes verification and validation lets talk about them

Verification

It is the process of evaluating work products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase or not.And to check every phase individually is called Verification of that project

Validation

It is process of evaluating the software during or at the end of the development process to determine whether it satisfies specified business requirements .It majorly focused on User's Request and User's Needs

Functional testing                     Testing Techniques

NON-Functional testing              Defects

Testing approach                      Test cases example

Next