© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre 1 1 Adopt Smartesting technology with Model Based Testing

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agile functional testing with a model-driven approach Kalyan Talluri Senior Consultant

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agile Testing Agile Environment 1.The time between two deliveries is short, and test suites must pass at all times. 2.Functional changes are frequently changing 3.Technical changes are frequently changing Testing Challenges 1.Poor Quality of test cases : How could a tester be efficient in scanning the changes in a few hundred tests repository, making the changes without a mistake and then executing them, all this inside a run 2.Less Productivity: Frequent changes mean a lot of regression. testing. Test design, manual execution & automation is time taking 3.Higher Cycle time to Deliver : Due to Manual test design & regression testing, testing duration will be increased for next iteration.

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Model-Driven Testing: What and Why? Limitations of manual test design 1.Applications can be complex, risky 2.Requirements are lacking detail and changing 3.Time-Consuming, labor-intensive 4.High level test design knowledge required 5.Chance on human errors 6.Expensive maintenance (manual rework) 7.Late detection of specification omissions 8.Difficult proof of test coverage Model driven testing Model-driven testing refers to the processes and techniques for the automatic derivation of abstract test cases from abstract formal models, the generation of concrete tests from abstract tests, and the manual or automated execution of the resulting concrete test cases. ModelSystem Abstract tests Executable tests can be run against are derived from is a partial description of are abstract versions of The complexity of applications requires a smart approach to test design

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Model Driven Testing

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre MDT Applicability Model-driven testing for enterprise software targets the key categories of black-box functional testing: Several testing levels: Acceptance testing System integration testing System testing Various testing types within these levels: Risk and Requirements Based Testing End-to-end testing Regression testing Combinatorial testing Using several accessibility modes: GUI-based testing API-based testing Application testing & Component integration testing Batch application testing Levels of Testing

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Model driven testing in the scrum process Working increment of models for test generation Model-based testing

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Model driven testing in the scrum process - Roles

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre MDT - Execution

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Software Model

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre 15 BPM Notation Overview Task Gateway Event Events Call Activities Lane Connector

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre State machines Initial state State Transitions Trigger Effect Guard Internal transition Choice point

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre MDT Tools Model-based test case generators CertifyIt from Smartesting takes business process and behavioral models as input. It uses the standard modeling notations BPMN and a sub-part of UML. Smartesting CertifyIt targets enterprise software for system testing, acceptance testing, end-to-end testing, and regression testing. Designer from Conformiq takes as input UML state machines with a proprietary action language (QML – Qtronic Modeling Language). QML is a superset of the Java programming language. Conformiq tools have a special focus on datacom and telecom equipment vendors as well as service providers. Spec Explorer from Microsoft takes as input state-oriented model programs that are coded in C#, and targets component and system testing;

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Case Study–Actitime Reqs sprint1 ----admin functions (flow, params, Business rules, documentation) login as admin, create customer,create project,create user sprint2 - user functions (flow, params, Business rules, documentation) login as user, Add task, enter time, save time, view Time Track, view report sprint3 - (flow, params, Business rules, documentation) login as admin, delete user, delete customer, delete project, extra field in create project -----Project Description documentation change in enter time ----little change add a business rule in create user ---- as User Name

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 - Statemachine

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 - Statemachine

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 – Class diagram

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 – Business Rules

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 –Test Generation

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1–QC Manual test

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 – QTP Script

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint1 – Req Tracebility

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint2 - Statemachine

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint2 - Statemachine

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint2 – Class diagram

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint3 - Statemachine

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Sprint3 – Class diagram

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Summary-Benefits of MDT Tests are available earlier in the process Improved quality of the test cases (coverage and usability) Test maintenance facilitated Capitalization on test assets (reuse) Same service level with reduced QA budget Easier automation by a native support of Keyword-Driven Testing Automated traceability links of business requirements No restriction in technologies No restriction on test strategies (acceptance, end-to-end, …) Testing becomes real fun!

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre Agenda 1.Agile in Testing 2.Model driven testing 3.Model for Test Generation 4.MDT Tools 5.MDT for Agile Testing - Case Study: Actitime 6.Summary 7.Q&A

© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre twitter.com/smartesting