DIGIT Docs
v0.2
  • DIGIT Knowledge Base
  • Local Governance
v0.2
  • Introducing HCM Console
  • Release Notes
    • 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
      • Low Level Design
        • Project Factory (Campaign Manager)
      • Services
        • Project Factory
          • Campaign Manage APIs
          • Data Manage APIs
            • Target Upload
          • Boundary Campaign Setup
            • Boundary Generation
        • HCM Console Web
          • User Interface Design
          • Create New Campaign
            • Campaign Details
            • Delivery Details
            • Boundary Details
            • Resource Upload Details
            • Setup and Implementation of Campaign
            • Summary Screen
          • Change Campaign Dates
          • My Campaign
            • Action Column Integration
          • Boundary Bulk Upload
          • Campaign Timeline
  • SETUP
    • Installation
    • Configuration
    • 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

Target

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

PreviousUserNextFacility

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 environment variable file and collection file in Postman.

  1. Successful run scenario:

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

Example:

District
Post administrative
Locality
Village
Household Target at village level (Mandatory and to be entered by the user)

Yarnee

Klagbe Clinic

Klagbe Town

Pailey Towns

101

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

102

  1. Negative run scenario:

  • With an empty 'Target' column.

Example:

District
Post administrative
Locality
Village
Household Target at village level (Mandatory and to be entered by the user)

Yarnee

Klagbe Clinic

Klagbe Town

Pailey Towns

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

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

District
Post administrative
Locality
Village
Household Target at village level (Mandatory and to be entered by the user)

Yarnee

Klagbe Clinic

Klagbe Town

Pailey Towns

-1

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

0

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

1.11

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

AB$$

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

12/04/24

Yarnee

Klagbe Clinic

Klagbe Town

Pailey test town

1000000000

  1. Collection runner result - Passed.

https://unified-qa.digit.org
8KB
Target upload.postman_environment.json
environment.json
83KB
Target Upload API Automation.postman_collection.json
collection.json
13KB
valid file target.xlsx
13KB
empty target upload.xlsx
13KB
invalid values in Target column.xlsx
21KB
Target Upload API Automation.postman_test_run.json