Introduction

Tests are where we put the fixtures and assertions created earlier, and add a schedule to execute the test. Once the test is created, it can be run, and outcome can be viewed in the history.

While there is no limit to the number of steps that can be included in a test. It is best to try and keep a test as simple as possible, and focus on just one area.

Test suites allow tests to be grouped together, so if there is several tests for new starters. You could create a test suite called New Starters, and then have the different tests for New Starters grouped here.

Creating a Test Suite

The following guide details how to create a test suite in Identity Panel.

Step	Image
Log in to Identity Panel
Go to Settings, and Select Test Panel
If required, update the provider to the testing Provider (This will normally be called Test or Testing)
Click the New Button
Enter the Suite Name using the following format: {XXX} - {Test Area} 001 - Employees - New Starters
Click the arrow, and add a description to the Notes
Click the save button to save the Test Suite (If prompted, add a commit message and click Ok). Repeat above steps for the required Test Suites

Creating Tests

The following guide documents how to create a test within Test Panel.

Steps	Image
Log in to Identity Panel, and go to the Test Suite you want to add a test for
Click the New Button under Tests
Enter a name, and click the down arrow. The name should describe the test in more detail.
In the Notes, add a description of what the test is performing.
Under Actions, we select existing fixture, and click new
From the drop down, select the fixture required
Using the actions drop down, select schedule, and click New
Select the required schedule
Add a note to describe what the schedule does
Using the actions drop down, select existing assertion, and click new
Select the Assertion from the drop down we want to run.
The test is now complete, and ready to be run. When looking at all the steps, we can see the DN for the fixture is 123456, and the DN being used for the Assertion is also 123456. This standard allows us to confirm that we have selected the correct Fixture and Assertion for the test, and will save time when it comes to validating that the test is working as expected. By adding the note to the schedule, it also makes it clear which sync is being run, and the steps that are being run as part of the schedule.

Articles in this section

Test Panel - Creating my first test

Introduction

Creating a Test Suite

Creating Tests

Comments

Articles in this section

Introduction

Creating a Test Suite

Creating Tests

Related articles