Product-Management-Intelligence

he V - model is SDLC model where execution of processes happens in a sequential manner in V-shape. It is also known as Verification and Validation model. V - Model is an extension of the waterfall model and is based on association of a testing phase for each corresponding development stage. This means that for every single phase in the development cycle there is a directly associated testing phase. This is a highly disciplined model and next phase starts only after completion of the previous phase. V- Model design Under V-Model, the corresponding testing phase of the development phase is planned in parallel. So there are Verification phases on one side of the .V. and Validation phases on the other side. Coding phase joins the two sides of the V-Model. The below figure illustrates the different phases in V-Model of SDLC. Verification Phases Following are the Verification phases in V-Model: Business Requirement Analysis:  This is the first phase in the development c...

What is Agile Testing? Unlike the WaterFall method, Agile Testing can begin at the start of the project with continuous integration between development and testing. Agile Testing is not sequential (in the sense its executed only after coding phase) but continuous. Agile team works as a single team towards a common objective of achieving Quality. Agile Testing has shorter time frames called iterations (say from 1 to 4 weeks). This methodology is also called release, or delivery driven approach since it gives a better prediction on the workable products in short duration of time In this article we will discuss about Test Plan for Agile. Agile Testing Strategies. The Agile Testing Quadrant. QA challenges with agile software development. Risk of Automation in Agile Process. Test Plan for Agile Unlike waterfall model, in an agile model, test plan is written and updated for every release.  The agile test plan includes types of testing done in that iteration like tes...

Creating Keyword & Hybrid Frameworks with Selenium Frameworks help to structure our code and make maintenance easy. Without frameworks we will place all our code and data in same place which is neither re-usable nor readable. Using Frameworks, produce beneficial outcomes like increase code re-usage , higher portability , reduced script maintenance cost etc There are mainly three type of frameworks created by Selenium WebDriver to automate manual testcases Data Driven Test Framework Keyword Driven Test Framework Hybrid Test Framework Data Driven Test Framework In  data driven framework all of our test data is generated from some external files like excel, csv, XML or some database table. We already learned about Data Driven  testing  in our previous  tutorial Keyword Driven Test Framework: In keyword driven test framework, all the operations and instructions are written in some external file like excel worksheet. Here is how the complete frame...