1 of 4

Automation - Run HCM Console Script

This step involves executing the Postman collection for collective creation of hierarchical data, file uploads, template generation, validation, and campaign creation within the same

Steps

Import the environment variable file and collection file in Postman.

Click on the Import button and drop both files.

Go to the Environment tab on the left side and click on it.

Certain values of environment variables should be changed depending on the following:

URL: This depends on the environment being used (for example, development, staging, production).
tenantid: Identifies the specific tenant for which the operations are being performed.
projecttype: Specifies the type of project, which can be either "LLIN-mz" or "MR-DN" (MDMS configuration).
locale: Defines the locale/language for localization purposes (e.g., en_IN for English in India, en_MZ for English in Mozambique).
msgId: Unique identifier combined with locale (e.g., 1710912592752|en_MZ). In msg id, change as per the locale used.

Go to the collection tab on the left side and click on it.

List of APIs

Start executing the script one by one.
In Filestore upload API, upload the Excel sheet in the file field by uploading the valid file. You will get a filestore id in response.

For example, A valid file can be created - if hierarchyType is "MH" and the sheet has 6 levels consisting of COUNTRY, PROVINCE, DISTRITO, POST ADMINISTRATIVE, LOCALITY and VILLAGE. Change the sheet name to MH_COUNTRY, MH_PROVINCE, MH_DISTRITO, MH_POST ADMINISTRATIVE, MH_LOCALITY, and MH_VILLAGE and all the boundaries as per hierarchy and upload the Excel sheet.

The sample sheet with valid data is given below:

Based on the campaign type, create a draft campaign by changing the variable of project type.
From 13. check the Excel with filestore Target API, and click on the filestore link by clicking on ctrl+click. It will download the target file.

From 14. filestore upload target API. After downloading the file, upload the valid file by filling in the target column in the sheet. You will get a filestore id in response.

Sample Sheet:

From 17, check the Excel with filestore API. Click on the filestore link (ctrl+click). It will download the facility file.

From 18, filestore upload Facility API; after downloading the file, upload the valid file by filling in the facility usage and boundary code column in the sheet. You will get a filestore id in response.

Sample Sheet:

From 21, check the Excel with filestore API, and click on the filestore link by pressing ctrl+click. It will download the user file.

From 22, filestore upload User API. After downloading the file, upload the valid file by filling in all columns in the sheet. You will get a filestore id in response.

Sample Sheet:

From 29, you have to create a campaign as per the campaign type i.e. LLIN/IRS and MRDN.

Based on Campaign create curl of campaign type, delivery rules and additional details are specified. change dates wherever required.

From 32, check user creds Excel. You will be able to get the user credentials Excel sheet by clicking on the filestore link (ctrl+click).

In the user credentials sheet, you will be able to see the username and password to log into the app.

Sample Sheet:

User

This page contains collection consisting of different scenarios of User Uploads which can be done to test in any environments.

These sheets have been created based on following assumptions:

URL -

locale - en_MZ

msgId - 1710912592752|en_MZ

hierarchy Type - ADMIN

project Type - LLIN-mz

Steps

Import the environment variable file and collection file in Postman.

Successful run scenario:

When a user adds valid data to the user file.

Example:

When a user uploads a valid sheet with a missing row in between

Example:

Negative run scenarios:

With an empty "Name of the Person (Mandatory)" column.

Example:

With less than 2 letters in "the "Name of the Person (Mandatory)" column.

Example:

Without phone number.

Example:

With invalid values in the phone number column.

Example:

With the same phone number.

Example:

Without data in the role column.

Example:

Without data in the Employment Type column.

Example:

With an empty Boundary Code column.

Example:

With invalid values in the Boundary Code column.

Example:

Test Run collection -Passed

Target

This page contains collection consisting of different scenarios of Target Uploads which can be done to test in any environments.

These sheets have been created based on following assumptions :

Url - https://unified-qa.digit.org

locale - en_MZ

msgId - 1710912592752|en_MZ

hierarchy Type - ADMIN

project Type - LLIN-mz

Steps

Import environment variable file and collection file in Postman.

Successful run scenario:

With a valid range of numbers in the 'Target' column.

Example:

Negative run scenario:

With an empty 'Target' column.

Example:

With invalid values in the 'Target' column (max, min, date, negative, zero, decimal values).

Collection runner result - Passed.

Facility

This page contains collection consisting of different scenarios of Facility Uploads which can be done to test in any environments.

These sheets have been created based on following assumptions :

Url - https://unified-qa.digit.org

locale - en_MZ

msgId - 1710912592752|en_MZ

hierarchy Type - ADMIN

project Type - LLIN-mz

Import environment variable file and collection file in Postman:

Successful run scenarios:

Valid file with correct values in all columns.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With a valid file with a missing row in between.

Example:

Negative run scenarios:

With an empty "Facility Usage" column.

Example:

With all inactive values for the "Facility usage" column.

Example:

With an empty "Boundary Code" column.

Example:

With duplicate names in the "Facility Name" column.

Example:

With an empty "Facility Name" column.

Example:

With an invalid value in the "Facility Name" column.

With an empty "Facility Type" column.

With an empty "Facility Status" column.

With empty and invalid values in the 'Capacity' column (max, min, date, negative, zero values).

With empty and invalid values in the "Boundary Code" column.

Collection runner result -passed:

Automation - Run HCM Console Script

This step involves executing the Postman collection for collective creation of hierarchical data, file uploads, template generation, validation, and campaign creation within the same

Steps

Import the environment variable file and collection file in Postman.

Click on the Import button and drop both files.

Go to the Environment tab on the left side and click on it.

Certain values of environment variables should be changed depending on the following:

URL: This depends on the environment being used (for example, development, staging, production).
tenantid: Identifies the specific tenant for which the operations are being performed.
projecttype: Specifies the type of project, which can be either "LLIN-mz" or "MR-DN" (MDMS configuration).
locale: Defines the locale/language for localization purposes (e.g., en_IN for English in India, en_MZ for English in Mozambique).
msgId: Unique identifier combined with locale (e.g., 1710912592752|en_MZ). In msg id, change as per the locale used.

Go to the collection tab on the left side and click on it.

List of APIs

Start executing the script one by one.
In Filestore upload API, upload the Excel sheet in the file field by uploading the valid file. You will get a filestore id in response.

The sample sheet with valid data is given below:

Based on the campaign type, create a draft campaign by changing the variable of project type.
From 13. check the Excel with filestore Target API, and click on the filestore link by clicking on ctrl+click. It will download the target file.

From 14. filestore upload target API. After downloading the file, upload the valid file by filling in the target column in the sheet. You will get a filestore id in response.

Sample Sheet:

From 17, check the Excel with filestore API. Click on the filestore link (ctrl+click). It will download the facility file.

From 18, filestore upload Facility API; after downloading the file, upload the valid file by filling in the facility usage and boundary code column in the sheet. You will get a filestore id in response.

Sample Sheet:

From 21, check the Excel with filestore API, and click on the filestore link by pressing ctrl+click. It will download the user file.

From 22, filestore upload User API. After downloading the file, upload the valid file by filling in all columns in the sheet. You will get a filestore id in response.

Sample Sheet:

From 29, you have to create a campaign as per the campaign type i.e. LLIN/IRS and MRDN.

Based on Campaign create curl of campaign type, delivery rules and additional details are specified. change dates wherever required.

From 32, check user creds Excel. You will be able to get the user credentials Excel sheet by clicking on the filestore link (ctrl+click).

In the user credentials sheet, you will be able to see the username and password to log into the app.

Sample Sheet:

Facility

This page contains collection consisting of different scenarios of Facility Uploads which can be done to test in any environments.

These sheets have been created based on following assumptions :

Url - https://unified-qa.digit.org

locale - en_MZ

msgId - 1710912592752|en_MZ

hierarchy Type - ADMIN

project Type - LLIN-mz

Import environment variable file and collection file in Postman:

Successful run scenarios:

Valid file with correct values in all columns.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With a valid file with a missing row in between.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

Negative run scenarios:

With an empty "Facility Usage" column.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With all inactive values for the "Facility usage" column.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With an empty "Boundary Code" column.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With duplicate names in the "Facility Name" column.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With an empty "Facility Name" column.

Example:

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With an invalid value in the "Facility Name" column.

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With an empty "Facility Type" column.

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With an empty "Facility Status" column.

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With empty and invalid values in the 'Capacity' column (max, min, date, negative, zero values).

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

With empty and invalid values in the "Boundary Code" column.

Facility Name

Facility Type

Facility Status

Capacity (Units: Bales for Bednets/ SPAQ Blister for SMC)

Boundary Code (Mandatory)

Facility Usage

Collection runner result -passed:

User

This page contains collection consisting of different scenarios of User Uploads which can be done to test in any environments.

These sheets have been created based on following assumptions:

URL -

locale - en_MZ

msgId - 1710912592752|en_MZ

hierarchy Type - ADMIN

project Type - LLIN-mz

Steps

Import the environment variable file and collection file in Postman.

Successful run scenario:

When a user adds valid data to the user file.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

When a user uploads a valid sheet with a missing row in between

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

Negative run scenarios:

With an empty "Name of the Person (Mandatory)" column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

With less than 2 letters in "the "Name of the Person (Mandatory)" column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

Without phone number.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

With invalid values in the phone number column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

With the same phone number.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

Without data in the role column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

Without data in the Employment Type column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

With an empty Boundary Code column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

With invalid values in the Boundary Code column.

Example:

Name of the Person (Mandatory)

Phone Number (Mandatory)

Role (Mandatory)

Employment Type (Mandatory)

Boundary Code (Mandatory)

Test Run collection -Passed