Presented by Elodie Bernard

Slides:



Advertisements
Similar presentations
Model-Based Testing with Smartesting Jean-Pierre Schoch Sogetis Second Testing Academy 29 April 2009.
Advertisements

Behavior Driven Test Development
© 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.
SCRUM basics Julie Rudder & Claire Stewart. What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie)
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Create New feature Approved Change request Create User Stories for the feature Add User stories to Target Process backlog User Stories – 1.Create Story.
A GIS Approach to Pedestrian Level of Service Natalia Domarad 14th TRB Transportation Planning Applications Conference Columbus, Ohio May 5-9, 2013.
A Tool to Support Ontology Creation Based on Incremental Mini- Ontology Merging Zonghui Lian Data Extraction Research Group Supported by Spring Conference.
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
How do you simplify? Simple Complicated.
Task Manager Software Engineering: CS 673 Spring 2009 John Spencer, Parag Shah, Rich Moffitt, Hassan Sobhie May 4, 2009.
Cyreath.co.uk Empirical Pragmatic Testing Copyright ©Mark Crowther 2009 An introduction to SCRUM Agile Project Management Mark Crowther – Empirical Pragmatic.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Odin Technology Ltd. Automated Testing that Delivers.
Copyright © Siemens AG All rights reserved. Essential Criteria on MBT to Ensure Quality of Software in Industry PVR Murthy Andreas Ulrich Siemens.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Automated Acceptance Testing and Continuous Delivery Larry Apke Agile Expert
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
1 Presentation Title Test-driven development (TDD) Overview David Wu.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Model Based Testing implementing with tools Ruud van Houwelingen 1 December 2, 2009.
6 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Site Hub User Role – Managing Sites.
Embedded Systems Software Engineering
CS223: Software Engineering
Agile Project Management and the yin & yang of
HPE ALM Octane.
Interface Concepts Modeling Core Team
Flight Software Conference 2016
Software Testing.
TEST AUTOMATION IN BDD WAY
Scrum.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Wael Ellithy, Ph.D. Arx ICT
The Five Secrets of Project Scheduling A PMO Approach
Systems Analysis and Design in a Changing World, 6th Edition
Deploying ArcGIS for Water
Object-Oriented Analysis and Design
Object-Oriented Software Engineering Using UML, Patterns, and Java,
SysML v2 Usability Working Session
Week 10: Object Modeling (1)Use Case Model
Chapter 3 – Agile Software Development
By: By: Agile Scrum Master Online Training.
Product Backlog List of things that needs to be done to make the product come into existence 
Approaches to Systems Development
Agile Workshop Tuesday, November 7, 2017
Burn Down charts for Project Management
Demystifying SAFe.
Advantages OF BDD Testing
Burn Down charts for Project Management
Agile Project Management
Summarizing Our Models to Date
Systems Analysis and Design in a Changing World, 6th Edition
Object Oriented Analysis and Design
Model Based Testing Venkata Ramana Bandari, Expert Software Engineer
Agile Process: Overview
Introduction to UML.
Object-Oriented Systems Development Life Cycle (CH-3)
Business transformation and GDPR compliance platform
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Overview of the ETSI Test Description Language
Scriptless Test Automation through Graphical User Interface
Introduction to BDD. Introduction to BDD “BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale, high-automation,
Use Case Modeling Part of the unified modeling language (U M L)
Scrum in Action.
Topic 9: Requirements Definition and Prioritisation
Street Manager Training approach
Presentation transcript:

Presented by Elodie Bernard Experience Report : Visual Test Design for Test Automation in Agile of a Large-Scale IT Systems Presented by Elodie Bernard © All rights reserved

Statement Problem and workflows © All rights reserved

Advanced Automated Testing Problem statement Complexity in use of the current MBT approaches Introduction of a Lightweight MBT : a visual test design approach Simplify the modeling notation Facilitate the maintenance of test cases during and through sprints User Conference on Advanced Automated Testing © All rights reserved

Typical MBT modeling approach Workflows statement Visual test design Typical MBT modeling approach Behavioral modeling User Conference on Advanced Automated Testing © All rights reserved

Modeling concepts © All rights reserved

Example of visual test design with YestⓇ (from Smartesting) Limited number of modeling artifacts High modelling capability Ability to represent simple as well as complex business processes User Conference on Advanced Automated Testing © All rights reserved

Acceptance Test Driven Development With a visual test design approach © All rights reserved

ATDD concept with a visual test design approach Start of a new sprint End of the sprint We have new : User stories Business rules Acceptance criteria Changes in product backlog occur in the sprint and will be developed We update the graphical representation to be in line with business rules Features are developed and made accessible on a test environment We generate acceptance scenarios We test the new features User Conference on Advanced Automated Testing © All rights reserved

Lessons learned from using a visual test design approach Helps to easily update the test assets Allows to quickly generate tests that required an update Improves communication and work between project stakeholders User Conference on Advanced Automated Testing © All rights reserved

Test automation Overview © All rights reserved

Test automation overview Keyword-driven-testing Java Selenium add-on Data set management Keywords table with Yest User Conference on Advanced Automated Testing © All rights reserved

Test automation process The visual representation of the test The abstract scenario and the corresponding automated test script The test script in java/Selenium with the use of dataset User Conference on Advanced Automated Testing © All rights reserved

Test automation process The scripting details Data set collection The scenario to automate Link the keywords to the test actions Link data sets to the future automated script Create a data set collection User Conference on Advanced Automated Testing © All rights reserved

Lessons learned about the automation process Our experiences have shown that : Having a visual link between the manual and automated test assets is beneficial Documentation of automated test cases is directly accessible to all project stakeholders through a visual approach The ability to transcribe test cases easily via the keyword-driven system provides visibility and improves maintenance management User Conference on Advanced Automated Testing © All rights reserved

Conclusion and futur works © All rights reserved

What is new in our approach ? The approach dramatically simplified the MBT approach Maintain a short learning curve and good usability by functional testers Be in line with iterative and incremental development approaches Supporting both scenario-based and automated test User Conference on Advanced Automated Testing © All rights reserved

Advanced Automated Testing Futur works To experiment the training of functional testers Continue to develop an add on in Yest To define good practice to facilitate and improve MBT approach, visual test design Apply new approaches and methodologies to a group of IT projects User Conference on Advanced Automated Testing © All rights reserved