Embed Size (px)
DESCRIPTION
In this presentation you will learn steps towards making your testing: - Correct - Scalable - Agile - Low cost
Citation preview
IBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessModelDrivers.us
How to industrialize testing
How to industrialize testing
modelDT
ModelDrivers.us
About Model Drivers
Model driven products for Reporting Testing Business strategy and cases Regulatory conformance Business architecture
ModelDrivers.us
You started out with nothing
In this testing story, you start out with nothing. You will take baby steps from nothing
to full industrial strength testing.
ModelDrivers.us
Why you want to take the testing journey?
Labour intensive: as many as 50% of the staff on a project are supporting testing in some way.
In-consistent: 2 different testers derive 2 different approaches to the same problem
Inefficient: By catching errors late in the process the remediation costs are much higher than when caught early in the process.
Fragmented: The project manager, developer, tester, end user each manage the testing effort from their own perspective, with their own tools and artefacts.
As a result Cost is high: Testing of business systems and application can be 50% of a
projects cost. Quality is low:
ModelDrivers.us
Step 1: You do some data modelling
A simple UML Class diagram
You get Quality requirements Automated specs
Auto generation
ModelDrivers.us
Step 2: You start to crawl with XML
Transform
You get Automated testing of data format Guaranteed alignment between
business domain and test
Schema validation
XML Schema
Class diagram
ModelDrivers.us
Step 3: You take your first step with OCL
You get Automated testing of
data related business rules
Guaranteed alignment between business domain and test
ModelDrivers.us
Step 4: Introduce meta model for the business domain
You get Consistency
between your business domains
Conformance to high level management concerns
Re-use within the business domain
Architect
Design
Build
ModelDrivers.us
Step 5: The meta model for testing
Architect
Design
Build
ModelDrivers.us
6 domains of the testing meta model
A. Test architecture: Testing meta model, business domain, testing package
B. Test package: SUT, test context, test components
C. Test configuration: Test cases, scheduler, arbiters, logs
D. Test case: Testing activity
E. Test data: Data pools, partitions, selectors,
F. Deployment: Nodes for SUT, Test components, Scheduler
ModelDrivers.us
A. Test architecture
Testing meta model Business domain Testing package
ModelDrivers.us
B. Test package
SUT Test context Test components
ModelDrivers.us
C. Test configuration
Test cases Scheduler Arbiters Logs
ModelDrivers.us
D. Test case
Testing activity
ModelDrivers.us
E. Test data
Data pools Partitions Selectors
ModelDrivers.us
F. Deployment
Nodes for SUT Test components Scheduler
ModelDrivers.us
Benefit 1: Automation e.g artefact generation
Test package design
Automated data testing
Quality testing framework
Automated test specifications
Automated test runners
ModelDrivers.us
Benefit 2: Guaranteed Business domain testing coverage
Business domain – use case and data entities
Test
com
pone
nts:
E.g
. te
st c
ase
Coverage of business domain By testing package
ModelDrivers.us
AutomatedTest Factory
Benefit 3: Business domain and testing in lockstep
Pro
cess
Dat
a
Data model
Process model
ModelDrivers.us
Our story today
You started out with nothing Step 1: You modelled business domain in
MagicDraw Step 2: Converted to XML Step 3: Overlaid with OCL and OCL
validation Step 4: Introduced meta model for the
business domain Step 5: Introduced meta model for testing Step 6: Built an automated test factory
100 year old “Fauja Singh becomes oldest marathon runner” BBC, 17 October 2011
ModelDrivers.us
modelDT plugin development roadmap
1.0 Base Domain Specific Language Test Case designs Business domain coverage reports End user help, manual, training
1.1 Extended DSL Extended analysis reports
2.0 Test script outputs – Junit, Quality Centre, etc Methodology wizards Domain specific patterns and models
3.0 Synthetic test data generation Risk modelling and management
IBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessIBD Innovative Business Design – Build a better businessModelDrivers.us
Next steps
• Demonstration: Attend a short web presentation and explore any aspect of Model Driven Testing.
• White paper: Request a copy of “Roadmap to industrialised testing”.
• Questions: Greg Soulsby http://uk.linkedin.com/in/gregsoulsby
• Twitter: @modelDT, @modelDrivers• Youtube: modelDrivenTesting• Linked in group: www.linkedin.com/groups/Model-drivers-4341672/
• Blog: http://blog.modeldrivers.us/• Site: www.modelDrivers.us• Plugin beta: Get the benefits with free support & contribute
to direction
