DIGIT Docs
v0.3
  • DIGIT Knowledge Base
  • Local Governance
v0.3
  • Introducing HCM Console
  • Release Notes
    • v0.3: Release Notes
      • v0.3 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
      • HCM Console Test Cases V0.3
      • Gate 2 Release Checklist
        • Release Showcase
    • v0.2: Release Notes
      • v0.2 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
    • v0.1: Release Notes
      • v0.1 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
      • Gate 2 Release Checklist
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document (PRD)
    • Functional Specifications
  • TECHNOLOGY
    • Architecture
      • High Level Design
        • Project Factory
      • Low Level Design
        • Project Factory (Campaign Manager)
          • Create Campaign
          • Update Campaign
          • Manage Resources
        • Admin Console
          • Campaign Creation Flow
          • Campaign Updation Flow
          • Checklist Management
      • Services
        • Project Factory
          • Manage Campaign APIs
            • Microplan Integration
            • Update an Ongoing Campaign
          • Manage Data APIs
            • Target Upload
          • Manage Boundary APIs
            • Boundary Generation
            • Boundary Management
            • Boundary Management Through GeoJson
        • HCM Console Web
          • User Interface Design
          • Manage Campaign
            • Setup Campaign (New Campaign)
              • Campaign Details
              • Boundary Details
              • Delivery Details
              • Resource Upload Details
              • Summary Screen
              • Setup Campaign from Microplan
              • Setup and Implementation of Campaign
              • IRS Console Support
            • My Campaign
              • My Campaign Actions
              • Campaign Timeline
              • Update Campaign (Boundary/ Resources)
              • Update Campaign Dates
          • Boundary Data Management
          • Manage Checklist
            • Default Templates
  • SETUP
    • Installation
    • Configuration
      • UI Configurations
      • Steps to Enable a New Campaign Type in Console
      • Advanced Configurations
    • Quality Assurance Testing
      • Automation - Run HCM Console Script
        • User
        • Target
        • Facility
      • Performance Testing
  • GENERAL
    • Product Roadmap
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page

Was this helpful?

Export as PDF
  1. SETUP
  2. Quality Assurance Testing
  3. Automation - Run HCM Console Script

User

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

PreviousAutomation - Run HCM Console ScriptNextTarget

Was this helpful?

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

  1. Import the environment variable file and collection file in Postman.

  1. 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)

Name

5555627761

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • 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)

Name

5555627761

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  1. 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)

5555627761

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • 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)

N

5555627761

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • Without phone number.

Example:

Name of the Person (Mandatory)
Phone Number (Mandatory)
Role (Mandatory)
Employment Type (Mandatory)
Boundary Code (Mandatory)

Name

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • 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)

Name

6347374

Distributor

Temporary

ADMIN_MO_07_MAPUTO CITY

Name1

ABC23

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • With the same phone number.

Example:

Name of the Person (Mandatory)
Phone Number (Mandatory)
Role (Mandatory)
Employment Type (Mandatory)
Boundary Code (Mandatory)

Name

6347374748

Distributor

Temporary

ADMIN_MO_07_MAPUTO CITY

Name1

6347374748

Distributor

Permanent

ADMIN_MO_07_MAPUTO CITY

  • Without data in the role column.

Example:

Name of the Person (Mandatory)
Phone Number (Mandatory)
Role (Mandatory)
Employment Type (Mandatory)
Boundary Code (Mandatory)

Name

6347374748

Temporary

ADMIN_MO_07_MAPUTO CITY

Name1

6347374748

Permanent

ADMIN_MO_07_MAPUTO CITY

  • Without data in the Employment Type column.

Example:

Name of the Person (Mandatory)
Phone Number (Mandatory)
Role (Mandatory)
Employment Type (Mandatory)
Boundary Code (Mandatory)

Name

6347374748

Distributor

ADMIN_MO_07_MAPUTO CITY

Name1

6347374748

Distributor

ADMIN_MO_07_MAPUTO CITY

  • With an empty Boundary Code column.

Example:

Name of the Person (Mandatory)
Phone Number (Mandatory)
Role (Mandatory)
Employment Type (Mandatory)
Boundary Code (Mandatory)

Name

6347374748

Distributor

Temporary

Name1

6347374748

Distributor

Permanent

  • 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)

Name

6347374748

Distributor

Temporary

ABC

Name1

6347374748

Distributor

Permanent

111

Test Run collection -Passed

https://unified-qa.digit.org
3KB
User.postman_environment.json
environment.json
113KB
User Bulk Upload Automation.postman_collection.json
collection.json
141KB
valid user upload.xlsx
samplevalidfile
141KB
with row in between.xlsx
141KB
withoutname userupload.xlsx
141KB
with 2 letters in name of person.xlsx
141KB
without phone number.xlsx
141KB
With invalid values in phone number column.xlsx
141KB
with same phone number.xlsx
141KB
without role column.xlsx
141KB
without Employment type.xlsx
141KB
without Boundarycode column.xlsx
141KB
with invalid boundary code.xlsx
26KB
User Bulk Upload Automation.postman_test_run.json