Learn how to implement & carry through SDLC compliant naming conventions to Test Cases. Useful when used across CI/CD pipelines, giving all the testing team/stakeholders visibility of Test Cases & Test Suites within your Test ModellerProject.
By default, a path (Test Case) name shows as a sequence of named nodes. See clip: 1:45mins So, to clarify the names for stakeholders to avoid ambiguity, i.e. ‘what each Test Case is actually testing’ use Test Modeller’s naming conventions tab.
Note: Test Cases through a model with default named Start and End nodes will pick up the Coverage profile name. If, however, you change the End node name, the Test Case takes that name. Usually this is restrictive and not sufficiently descriptive, so use the Naming Conventions in Test Modeller to make more meaningful Test Case names.
To do so, click Coverage Profile in the top Ribbon Menu, in the Coverage Profile panel, click the Naming Conventions tab.
Test cases are equivalent to paths through the model of a system under test. They are generated automatically from a model, with or without test data and test automation associated with them. Test Modeller has coverage techniques using advanced algorithms to generate the smallest set of test cases needed to test given features with a required level of rigour.
Test Modeller is Curiosity's flow-driven model-based tool which provides a range of accelerators and connectors for building flowcharts rapidly. This includes importers for existing requirements and test cases, as well as recordings and scans of already built systems. These accelerators are designed to significantly reduce the time and technical knowledge needed to model complex systems, unlocking the value of model-based test automation.
A Project in Test Modeller represent the current collection of work the user is working on. Users can create multiple Projects within Test Modeller and switch between them at any time, this can be used to manage Models and User Teams.
Coverage Profiles are a wrapper for Coverage settings and options. Any number of Coverage Profiles can be created as required, each with its own Coverage settings. The Coverage button is on the Test Generation tab of a Model. Test Modeller Models come with Default Profile, User Stories and Test Cases Profiles built in.
This website uses analytics cookies. These cookies are used to improve your website experience and provide more personalized services to you. To find out more about the cookies we use, see our Privacy Policy.
