Modelling an Existing UI | The Art of Modelling | Curiosity Software
Book a meeting with a Curiosity expert: https://hubs.li/Q02-kpvr0
Visit the Curiosity Website: https://hubs.li/Q01hmm6n0
Follow Curiosity on LinkedIn: https://hubs.li/Q01XLxWv0
Modelling an existing UI. With George Blundell (Technical Analyst, Curiosity Software):
This introduces a simple customer login screen where emails and password fields and different elements of the application get picked up, from -to URL to eventually clicking on the sign-in button and in the model you see how different journeys get tracked.
We also take a closer look at using all three major block types of the test Modeller tool in conjunction with each other, to map out the different combinations of behaviour on the UI. This is a complete model which demonstrates some of the more basic best practices for modelling an existing UI relative to combinations of data but also combinations of user behaviour that can exist on top of a webpage.
Intro narration from Ben Riley, CIO at Curiosity Software:
George, one of our technical analysts walks you through the next few minutes with best practices when it comes to modelling, and how you have to think about slightly differently things like how do I overlay my automation, and work with data? But also, how do rules help specify different node logic in a model? There’s lots of exciting principles for you to get good at when it comes to modelling.
General info on Modelling a UI:
UI interfaces will at some point need testing, some will be a future concept while others evolve as requirements change. The segments consist of [1 - this] Modelling an existing UI. [2] Modelling a UI concept. [3] Modelling an evolving UI.
About the series: art of modelling
The art of modelling series from Curiosity Software – boost foundation thinking around the art of modelling for test case creation as a starting point, told through a series of 90 sec–2min clips.
Why focus on the ‘art of modelling’ rather than just getting stuck in with the software? We listened to customers and evolved this feedback to take deeper dives, but also stepping back to explore universal best practices.
The outcome is this series to focus on bringing a holistic alignment across projects for all stakeholders including testers, business users, SMEs, developers, SDETS, manual testers and end-users. Everyone across a team can model so positing a language of best practices, towards developing an art of modelling, this boosts collaborative effort.