Mar 1, 2024
Efficient Testing Strategies for IBM Planning Analytics
One of the challenges of IBM Planning Analytics (TM1) being such a powerful and *actual* real-time totally connected model is that one small tweak to the model somewhere can sometimes have an unanticipated effect on something else in the model that is hard to catch.
Unlocking Efficiency: The Advantages of the Arc Test Centre
With the Test Centre feature in Arc+, you can now easily set up reusable tests of your TM1 applications. Just re-run them whenever you want in Dev every time you do any development to make sure you didn’t accidentally mess up something in your model. Then confidently migrate to production (or give your UAT testers a consistently higher quality product).
Easy-to-use, integrated user interface:
- Adopt DevOps Best Practices for Your TM1 Development.
- Write your tests alongside your code.
- Quickly and easily find, create, edit, and organize your tests.
Designed for TM1
- Create tests without writing any code.
- Select processes, chores, and cubes from searchable lists.
- Utilize integrated shortcuts—for example, create a test directly from a data cell to verify its value or from a dimension to validate an element.
Built-in integration with Pulse
- Monitor which TM1 objects have associated tests.
- Track Test Execution Over Time.
- Expect exciting future features, including code coverage and integration with Pulse migration.
Navigating the Arc Test Centre: A Brief Exploration
The Arc Test Centre allows users to set up individual Unit Tests, either as part of the development phase or prior to deployment, and group them together to be run in sequence.
Collections
A Collection
defines a group of related Unit Tests
designed to thoroughly test a particular module or feature.
It provides a way to bundle together tests that are intended to be executed together, in sequence. A Unit Test
can belong to more than one Collection
making Unit Tests
reusable.
The Collections
tab displays the list of defined Collections
. To edit, click the Collection
name, or the edit button to the right of the Collection
. To create a new Collection
, click the New Collection
button.
Categories
A Category
is a way to group related Unit Tests
together. It is a label that provides a high-level organization of tests, making it easier to manage and navigate through them.
The Categories
tab displays the list of defined Categories
. To edit, click the Category
name, or the edit button to the right of the Category
. To create a new Category
, click the New Category
button.
Unit Tests
A Unit Test
defines a Unit Test to be executed by the Test Centre.
The Unit Tests tab displays the list of defined Unit Tests. To edit, click the Unit Test name, or the edit button to the right of the Unit Test. To create a new Unit Test, click the New Test
button.
Assertions
Each Unit Test
can have a list of Assertions
. Assertions
define the criteria to determine whether a Unit Test
passes or fails.
Assertions
are executed from top to bottom in the order given. Once any Assertion
fails, the Unit Test
fails and no further Assertions
are checked.
You can access the list of Assertions
from the Edit Unit Test
dialog by selecting the Assertions
tab.
Try it now!
The Arc Test Centre could be a product on its own, but it is added as a *feature* of Arc+ (i.e. if you have both Arc and Pulse, then you can use it). If you don’t have Arc and/or Pulse, then this is probably the time to trial them.
If you are already using Arc and Pulse, just follow the steps below to unlock many exciting features: