slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Adopt Smartesting technology with Model Based Testing PowerPoint Presentation
Download Presentation
Adopt Smartesting technology with Model Based Testing

Loading in 2 Seconds...

  share
play fullscreen
1 / 37
margaret-greene

Adopt Smartesting technology with Model Based Testing - PowerPoint PPT Presentation

112 Views
Download Presentation
Adopt Smartesting technology with Model Based Testing
An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Adopt Smartesting technologywith Model BasedTesting 1

  2. Agile functional testing with a model-driven approach Kalyan Talluri Senior Consultant Kalyan.talluri@smartesting.com

  3. Agile Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  4. Agile Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  5. Agile Environment • The time between two deliveries is short, and test suites must pass at all times. • Functional changes are frequently changing • Technical changes are frequently changing • Testing Challenges • 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 • Less Productivity: Frequent changes mean a lot of regression . testing. Test design, manual execution & automation is time taking • Higher Cycle time to Deliver : Due to Manual test design & regression testing, testing duration will be increased for next iteration. Agile Testing

  6. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  7. is a partial description of Model System can be run against are derived from Abstract tests Executable tests are abstract versions of Model-DrivenTesting: What and Why? “The complexity of applications requires a smart approach to test design” Limitations of manual test design • Applications can be complex, risky • Requirements are lacking detail and changing • Time-Consuming, labor-intensive • High level test design knowledge required • Chance on human errors • Expensive maintenance (manual rework) • Late detection of specification omissions • Difficult proof of test coverage Modeldriventesting • 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.

  8. Model Driven Testing

  9. 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

  10. Model driven testing in the scrum process Model-based testing Working increment of models for test generation

  11. Model driven testing in the scrum process - Roles

  12. MDT - Execution

  13. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  14. Software Model

  15. Task Lane Gateway BPM Notation Overview Connector Event Events Call Activities

  16. State machines State Transitions Effect Trigger Initial state Guard Internal transition Choice point

  17. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  18. Model-based test case generators Model-based test case generators MDT Tools • CertifyIt from Smartestingtakes business process and behavioral models as input. It uses the standard modeling notations BPMN and a sub-part of UML. SmartestingCertifyIt targets enterprise software for system testing, acceptance testing, end-to-end testing, and regression testing. • Designer from Conformiqtakes 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 fromMicrosoft takes as input state-oriented model programs that are coded in C#, and targets component and system testing;

  19. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  20. Case Study–ActitimeReqs sprint1 ----admin functions (flow, params, Business rules, documentation) login as admin, create customer,createproject,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 ----Email as User Name

  21. Sprint1 - Statemachine

  22. Sprint1 - Statemachine

  23. Sprint1 – Classdiagram

  24. Sprint1 – Business Rules

  25. Sprint1 –Test Generation

  26. Sprint1–QC Manual test

  27. Sprint1 – QTP Script

  28. Sprint1 – ReqTracebility

  29. Sprint2 - Statemachine

  30. Sprint2 - Statemachine

  31. Sprint2 – Classdiagram

  32. Sprint3 - Statemachine

  33. Sprint3 – Classdiagram

  34. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  35. 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!

  36. Agile in Testing • Model driven testing • Model for Test Generation • MDT Tools • MDT for Agile Testing - Case Study: Actitime • Summary • Q&A Agenda

  37. Q&A twitter.com/smartesting Thank you for your attention