© 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 technologywith 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 TalluriSenior ConsultantKalyan.talluri@smartesting.com

© 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 titreAgenda

1. Agile Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreAgenda

1. Agile Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreAgile Testing

Agile Environment1. The time between two deliveries is short, and test suites must pass

at all times. 2. Functional changes are frequently changing3. Technical changes are frequently changing

Testing Challenges4. 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

5. Less Productivity: Frequent changes mean a lot of regression . testing. Test design, manual execution & automation is time taking

6. 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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreModel-Driven Testing: What and Why?

Limitations of manual test design

1. Applications can be complex, risky2. Requirements are lacking detail and changing3. Time-Consuming, labor-intensive4. High level test design knowledge required5. Chance on human errors6. Expensive maintenance (manual rework)7. Late detection of specification omissions8. 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.

Model System

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 titreModel 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 titreMDT Applicability

Model-driven testing for enterprise software targets the key categories of black-box functional testing:•Several testing levels:

Acceptance testingSystem integration testingSystem testing

•Various testing types within these levels:Risk and Requirements Based TestingEnd-to-end testingRegression testingCombinatorial testing

• Using several accessibility modes:GUI-based testingAPI-based testingApplication testing & Component integration testingBatch 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 titreModel 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 titreModel 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 titreMDT - 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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreSoftware 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

EventEventsCall 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 titreState machines

Initial state

StateTransitions

TriggerEffect

GuardInternal 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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreMDT ToolsModel-based test case generatorsModel-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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreCase 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 Descriptiondocumentation change in enter time ----little changeadd a business rule in create user ----Email 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 titreSprint1 - 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 titreSprint1 - 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 titreSprint1 – 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 titreSprint1 – 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 titreSprint1 –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 titreSprint1–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 titreSprint1 – 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 titreSprint1 – 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 titreSprint2 - 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 titreSprint2 - 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 titreSprint2 – 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 titreSprint3 - 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 titreSprint3 – 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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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 titreSummary-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 titreAgenda

1. Agile in Testing2. Model driven testing3. Model for Test Generation4. MDT Tools5. MDT for Agile Testing - Case Study: Actitime 6. Summary7. 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

Q&A twitter.com/smartesting

Thank youfor your attention