Explore Curiosity's Platform Use Cases

Our innovative quality solutions help you deliver rigorously tested software earlier, and at less cost!

Test Modeller                    Use Cases

Explore a range of Test Modeller use cases and solutions!

Test Data Automation        Use Cases

Explore our range of Test Data Automation use cases and solutions!

Helpful Resources

Discover a range of helpful resources for getting started with our solutions!

Explore Curiosity's Resources

See how we empower customer success, watch our latest webinars, explore our newest eBooks, read our blogs, and more.

Latest Resources

Explore a wide range of the latest resources from the Curiosity team!

Customer Success Stories

Learn how our customers use our tools to achieve success!

Help & Support

Explore the helpful links below if you need any help.

Creating Quality Since 1995

Curiosity are your partners when designing, building and rigorously testing complex systems in short sprints!

Get To Know Curiosity

Explore our history, learn about our team and the latest Curiosity news!

Customer Success Stories

Learn how our customers use our tools to achieve success!

Connect With Us

Reach out to our team or keep up to date with our latest news!

 

Modelling an Existing UI

The Art of Modelling series from Curiosity Software – Learn how you can model an existing, concept and evolving UI using Test Modeller and it's built in UI Scanner.

Schedule a Demo   Try Test Modeller

 

Create a New UI Model

The video above introduces a simple customer login screen where emails and password fields and different elements of the application get picked up by a UI Scanner. This scan is then translated to a model 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.

 

Modelling a UI Concept

Modelling upfront is a key part of test or behaviour driven development, from which user stories are generated. At which point, developers can action the user stories to write an application or at least produce initial test scenarios to test it against, or as soon as the application is ready and available to be tested.

Despite the application not actually existing, at the start we lay out three blocks to explain the high level goal or high level use case of this page. This segment considers some key differences involved in modelling a UI when the application doesn't already exist, rather than an existing one.

 

Modelling an Evolving UI

As a UI evolves according to requirements, a model gives a focus for different stakeholders to collaborate within the Test Modeller canvas. So a model will easily evolve from day one through to possibly day 20. From coming in and explaining some of the most basic functionality or journeys on your app through to where a model has its different nodes rules applied, the outcome is to embed data ready for automation.

Additionally, rule-based generation are used on task blocks, essentially saying that for any instance given the logic as invalid data, will be forced down the invalid credentials route to inform test cases. The invalid password gets pushed through into a negative scenario, where we end up with a necessary error state.

 

Watch More of The Art of Modelling Series

 

 

Speak with an expert

Discover how Curiosity's Test Modeller can help automate your testing today!

Schedule a Demo