Model-Based Testing for Cypress

© Curiosity Software Ireland Ltd. 2020
Model-Based Testing for Cypress
September 29th 2020
Moderator: Tom Pryce
Communication Manager, Curiosity Software Ireland
Thomas.Pryce@Curiosity.Software
@TomTestsToo
Gleb Bahmutov
VP of Engineering, Cypress
Gleb@Cypress.io
@bahmutov
James Walker
Director of Technology, Curiosity.
James.Walker@Curiosity.Software
@CuriositySoft
Harry Burn
Solutions Architect, Curiosity
Harry.Burn@Curiosity.Software
@CuriositySoft

Model-Based Testing for Cypress
1. Barriers to successful test automation
2. How can MBT for Cypress help with these problems?
3. Demo: MBT for a Cypress framework
4. Questions and discussion

1. Barriers to successful
test automation
What automation challenges are worth solving?

Poll: What are the primary barriers to test
automation at your organisation?

5 Barriers to in-sprint test automation
1. Automated test creation remains wholly manual (there’s never enough time!).
2. Manual test case design cannot achieve sufficient coverage for complex systems.
3. Test data destabilises automation and creates bottlenecks.
− The average QA team spend 44% of their time searching, managing and generating data.1
4. Brittle tests need maintaining manually before every release.
− 65% of World Quality Repot respondents cite difficulties in automation “because our applications change too much”2
5. Automation code might not be easily re-usable, over-working a team of skilled engineers.
− 46% of respondents lack the skilled “test automation resources” needed to achieve their desired automation rate.2
1 Sogeti, Capgemini (2020), Continuous Testing Report 2020 2 Capgemini, Sogeti, Micro Focus (2019), World Quality Report 2019-20

Change is a real headache…
Change requests/user
stories flow in
A code change made to a
maze of components
Which tests are
affected? Which need
updating?
What has been
impacted by the
change? What
needs re-testing?
Test Automation Engineer
Automated test maintenance kills the ROI of automation
No formal mapping: code requirements
Code
Commit

Challenges across the SDLC
Silo
‘Agile’, Continuous Testing, “DevOps”… Or mini-waterfalls?
Wall Information Hop Delay
No feedback
or traceability
Dev Automation EngineersQA/TestBAs
Effort: Repetitious.
“Flat” formats prevent
automation in QA & Dev.
Quality:Most bugs
originate in incomplete,
ambiguous requirements.
Effort: Re-coding after
misunderstood designs
and uncaught bugs.
Quality:Bugs are more
damaging the later they
are discovered.
Effort: Slowly create
and maintain 1000s of
test cases. Wait for data.
Quality:Manually
derived tests hit a
fraction of system logic.
Effort: Repetitious
scripting, growing
maintenance.
Quality: Data clashes,
false positives, false
negatives, low coverage.
Formulate complex requirements
and change requests in
disparate, unconnected formats.
Convert the incomplete designs
into code, trying to fix the impact
of changes on complex systems.
Unsystematically create high
volume, low coverage test cases,
mismatched with system designs.
Choose between creating new
scripts for new logic or
maintaining existing code.

© Curiosity Software Ireland Ltd 2020
2. Why MBT for Cypress?
How can modelling and Cypress work together to solve these problems?

Poll: How much experience do you have
with model-based testing?

Model-Based Testing for
Cypress
Recorded
tests activity
Test Cases
BPMN
diagrams
BDD
Scenarios
Business
Requirements
Application Scans
Reactive Model
of the system
Find / Make / Allocate Test Data
Run Results
Tests
New
Iteration
 Perfect sets of tests
 Fast Maintenance
 Reusable Components
 Move faster
 Deliver with confidence
Test Automation

Solving challenges in automation
Modelling does the hardwork upfront, helping break barriers to test automation:
1. Modelling automates potentially slow and repetitive test case and data creation.
2. It minimises manual rework – updating models updates all artefacts generated from them.
3. Test generation optimises tests to find bugs earlier and at less cost to fix.
4. Modelling reduces silos, miscommunication, and the need to convert assets from one format to another –
everything ripples from the models.
5. Re-usability frees up engineering time – engineers focus on feeding in new code which is re-used across
cross-functional teams.
6. Model-based testing minimises test data frustrations, creating unique combinations for every test.

Across the SDLC: Collaborate,
communicate, share and re-use
The models then automate the creation test assets and specifications, driving
accurate development and in-sprint testing
Skills sharing & cross-team collaboration:
People who understand the user
requirements
People who understand testing
People who understand automation
People who understand data
People who understand integration
People who understand CI/CD
A single source of truth for all assets
Test scripts
Test Cases
Written Requirements & Diagrams
Gherkin specifications
Test Data
Service Definitions & Virtual Services
Cross-team alignment & real-time communication • No technical debt • In-sprint
automation • Minimal dev rework • Avoid duplicate effect and cumbersome maintenance

Modelling is an accelerator, not
replacement, for good automation
With modelling, automation becomes a largely automated comparison
of the modelled system to the system built in code.
That means accurate regression tests executed in-sprint.
Feeding in new code to your Cypress framework, it becomes re-usable in
future sprints and by non-coders.
You can focus on testing what’s new and interesting, testing fast-
changing systems.

Demo

What value has model-based
testing delivered at
organisations?
Harry Burn
Solutions Architect, Curiosity
@CuriositySoft

Questions and Discussion

Carry on the conversation?
• We’d love to chat further. Book a web meeting at
calendly.com/curiosity-james
• Want to try MBT? Visit Testmodeller.io for a free trial. Use our free
Cypress tutorial to get started.
• Follow @CuriositySoft and @Cypress_io.
• Email us on James.Walker@Curiosity.Software or Gleb@Cypress.io

Thank you
James.Walker@Curiosity.Software
Gleb@Cypress.io

Model-Based Testing for Cypress

More Related Content

What's hot

Similar to Model-Based Testing for Cypress

More from Curiosity Software Ireland

Recently uploaded

Model-Based Testing for Cypress

Editor's Notes