EDI Bootcamp:

Unit Testing Training

Map Unit Testing

• To ensure quality of map deliverables, a map is

being tested for its functional requirements
against the specification report (in MS Excel
Format)

• Developers/QAs use the same specification

report, and adds new columns for the test
cases/scenarios, expected output, test input
and comments. The specs will then be renamed
as the Test Scenario document

12/9/21 | Slide 2 © 2009 GXS, Inc.

Screenshot of Test Scenario:

12/9/21 | Slide 3 © 2009 GXS, Inc.

Test Documents

• Test Scenario – identifies the positive or

negative scenario of each mapping rule or
condition in the specification report.

• Test Files – refers to the test input files derived

from the positive or negative scenario of the
test cases. These are usually created from the
original input file of the map and are modified
per test scenario.

12/9/21 | Slide 4 © 2009 GXS, Inc.

Conditional Statements

    ; These variables are to define the Conditional Error message

[]
VAR->OTConditionalMsgC = "Conditional (first present, so all must be present): "
    VAR->OTConditionalMsgE = "Exclusion (no more than one can be present): "
    VAR->OTConditionalMsgF = "First (first present, then none of the others can be present): "
    VAR->OTConditionalMsgL = "List Conditional (first present, so one of the others must be present): "
    VAR->OTConditionalMsgO = "One (one required and only one can be present): "
    VAR->OTConditionalMsgP = "Paired (one present, so all must be present): "
    VAR->OTConditionalMsgR = "Required (at least one must be present): "
 
Snippet from standard model:

12/9/21 | Slide 5 © 2009 GXS, Inc.

QA Process Workflow

• QA verifies completeness AND correctness of

map package from the developer
Readme file (.readme.txt) - MANDATORY
Source model (.mdl) - MANDATORY
Target model (.mdl) - MANDATORY
Attachment file (.att) - MANDATORY
Export file (.exp) - MANDATORY
Batch file (.bat) - MANDATORY
Input file(s) (.in, .txt, etc.) - MANDATORY
AI generated output file(s) - MANDATORY
Sample output - if provided in original specs package from FM
XREF table - if required in the map

o If issues/defects are found, QA sends Test Status Report email (with information
on the logged issues in HPQC), back to the developer

o Developer fixes the issues, and replies to the Test Status Report email of QA, with
the updated map package attached on the email

12/9/21 | Slide 6 © 2009 GXS, Inc.

QA Process Workflow cont.

Logs a new defect

Fix the issue

QA HP-QC Developer
Closes the defect ID

• If no more issues are found on the map, QA

sends an email to the analyst or integrator for
output approval or for deployment of the map.

12/9/21 | Slide 7 © 2009 GXS, Inc.

HPQC: Quality Administration

• HP Quality Center 9.2 is a Web-based test

management tool that organizes and
manages all phases of the application testing
process

• QA testers use this tool for defect logging

12/9/21 | Slide 8 © 2009 GXS, Inc.

HPQC: Quality Administration

• HPQC captures all issues and defects

detected in maps being tested.

• This is also used to track common issues and

defects that needs to be focused on by
management to be able to put in measures on
how to prevent the defects from recurring.

12/9/21 | Slide 9 © 2009 GXS, Inc.

HPQC: Quality Administration

HPQC Defect Window

12/9/21 | Slide 10 © 2009 GXS, Inc.

HPQC: Defect Module Window

12/9/21 | Slide 11 © 2009 GXS, Inc.

• Discussions or clarifications with the
team…

• EDI unit testing training (hands-on)

- 1 Inbound map
- 1 Outbound map

* Exercises will be given by the end of this session.

12/9/21 | Slide 12 © 2009 GXS, Inc.