TESTINGMANTRA - BLOG
Blog
Testing Types
Usability Testing
Smoke Testing
Load Testing
Stress Testing
Domain Testing
Exploratory Testing
Recovery Testing
Scenario Testing
Regression Testing
User Acceptance Testing
Alpha Testing
Beta Testing
Unit Testing
Static & Dynamic Analysis Testing
Functional Testing
Ad-hoc Testing
Volume Testing
System Testing
Sanity Testing
Black Box Testing
Interoperability Testing
Volume Testing Techniques
Gray Box Testing
White Box testing
Articals
Agile Development
Coverage Criteria for GUI Testing
Release Life Cycle
Quality Concept
TQM - Total Quality Management
When are the Test Plan written
Unit Testing Advantages & Techniques
Classification of Defect
Requirement Testing Techniques
When is Testing Complete?
Quantative Project Management
Software Configuration Management
When to use Regression Testing?
V-Model Concept of Testing
Activity of Software Test Engineer
Risk Management
Sanity Testing A Overview
Website Security Smoke Test Template
Software Testing Techniques
Requirements & Specifications
Traceability Matrix
Test Plan - Objectives and Benefits
Agile Testing - Master the new game
Testing Vocabulary
SQL Tutorial
Test Strategy
Error Handling Testing
SDLC - Concept
Steps of Software Testing Life Cycle
Why to use Metrics?
Defect Tracking
SyncML
Mobile Testing
GSM Basic
Cellular Network Architecture
Mobile Communication Overview
Mobile & handheld usability testing
Why Mobile Testing is different
True BREW Testing
VOIP Testing
SIP Testing - An overview
SIP Messages
Structure of SIP Protocol
SIP Important terms
SDLC Model
Software Development Life Cycle
Waterfall model
Spiral Model
V-Model
Iterative Model
Big Bang Model
RAD Model
Prototype Model
SOFTWARE TESTING
Test Plan
Test Case & Test Design techniques
Templates
Software Project Template
Software Testing Template
Automated Testing Tools
QTP
Winrunner
JUnit
Selenium IDE
LoadRunner
JMeter
Estimation Techniques
Using Use Case Points
Quick Estimation Technique
Testing Estimation Process
Certifications
CSQA
CSTE
                                                                                                                                                                  Usability Testing      Smoke Testing      Load Testing      Stress Testing      Domain Testing      Exploratort Testing       Recovery Testing      Scenario Testing      Regression Testing      User Acceptance Testing      Alpha Testing      Beta Testing      Unit Testing      Static & Dynamic Analysis Testing                                                                                             







Share
Follow us at Twitter
Follow us at Facebook
Share
THE "V" MODEL CONCEPT OF TESTING

Testing Life cycle involves continuous testing of the system during the developmental process. At predetermined points, the results of the development process re inspected to determine the correctness of the implementation. These inspections identify defeats at the earliest possible point.

Testing life cycle cannot occur until a formalized SDLS has been incorporated. Testing Life Cycle is dependent upon the completion of predetermined deliverable at specified points in the development life cycle. If information services personnel have the discretion to determine the order in which deliverables are developed, the cycle test process becomes ineffective. This is due to variability in the process, which normally increases cost.

Testing life cycle concept can best be accomplished by the formation of a test team. The team is comprised of members of the project who may be both implementing and testing the system. When members of the team are testing the system, they must use a formal testing methodology to clearly distinguish the implementation mode from the test mode. They also must follow a development. Without a specific structure test methodology for testing as they used for developing the system under one methodology and testing it under another.
Advantages and Disadvantages of the Waterfall Model and V-Model

The Verification and Validation model commonly known as V Model is considered to be an extension of the Waterfall model. This is because just like the waterfall model, it’s a welltructured method in which the different phases progress in a sequential or linear way. That means each phase begins only after the completion of the previous phase.


An important aspect of this model is that testing activities like planning, test designing happens well before coding. The advantage is that it saves ample amount of time and since the testing team is involved early on, they develop a very good understanding of the project at the very beginning.


The biggest disadvantage of V-model is that it’s very rigid and the least flexible. If any changes happen mid way, not only the requirements documents but also the test documentation needs to be updated. Even with these disadvantages, it’s the most favored software development process as it’s simple and easy to use.

In short we can summaries these as below:

WaterFall Model advantages:
                It is a linear sequential model
                It is very simple model to implement
                It is the first model.
                It needs very few resources to implement
Disadvantages:
                In this model there is no back tracking.
                For example if any error occurred at any stage of software development, it can’t be corrected in that build.

V-Model advantages:
                It is also called as verification and validation Model.
                This means the verification and validation will be done side by side.
                It emphasis is the strict process flow to develop a quality product.
                The errors occurred in any phase will be corrected in that phase itself.
V-Model disadvantages:
                It needs lot of resources and money.
                It needs an established process to implement.
                It can be implemented by only some big companies.


V-Model Concept of Testing