Model Concurrency Testing - Packages

Options
andy_tarr
andy_tarr Member, ALL USERS, Employee Posts: 5 Master Anaplanner of the Year
in Anaplan Community

 

1. Purpose

 The 2 packages (Standard and Premium) have been defined to enable the easy selection of the Model Concurrency Testing that meets the customer/project needs and included in the SoW. 

To deliver a consistent and predictable Model Concurrency Testing service it is important that projects fall into one of the defined packages based on the number of User Journeys and Concurrency Scenarios required.

 

2. Packages

 

packages.png

3. Definitions

 3.1. User Journeys to Simulate

A User Journey is the sequence of steps that a user will perform to complete a specific task/achieve a specific outcome as part of their job/role. Each User Journey should be up to 50 steps. Each set of User Journey steps provided will be translated into computer-driven simulation that will be used to simulate concurrent user model interactions in the Concurrency Scenarios.

As the focus is on model concurrency, the User Journeys selected must be expected to be performed by the highest number of users at the same time/the most often and the User Journeys that include running actions should be prioritised.

 

3.2. Test Types

 The definition of all the different tests available and their purpose can be found in this article.

  • Standard: 2 test types are included (Peak Load, plus Stress OR Endurance)
  • Premium: 3 test types are included (Peak Load, plus Stress and Endurance)

 

3.3. Concurrency Scenarios


A Concurrency Scenario consists of one or more User Journeys that represents the expected concurrent model usage during a defined period of activity, such as the busiest period of a typical business day or an exceptional period i.e. month end.

Each Scenario will have the same set of parameters that includes:

  • Test type
  • The User Journeys to be included
  • Number of current users that will be performing each User Journey.
  • Number of times each User Journey is expected to be completed in an hour.
  • Additional information (any other information about how the Scenario should be executed)

These Scenarios are defined in the Model Interaction Specification.

 

3.4. Test Cycles Included

 The number of test iterations that are included.

The definition of a test cycle is one run of each of the requested scenarios and retesting of the same Concurrency Scenarios after any model optimisations have been applied.

 

 

 

Tagged:

Categories