EDI Unit Testing Training

EDI Bootcamp:

Unit Testing Training

April 9, 2023 | Slide 2 © 2009 GXS, Inc.

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


Screenshot of Test Scenario:


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.


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:


QA Process Workflow

• QA verifies completeness AND correctness of map package from the developer

Readme file (.readme.txt) - MANDATORYSource model (.mdl) - MANDATORYTarget model (.mdl) - MANDATORYAttachment file (.att) - MANDATORYExport file (.exp) - MANDATORYBatch file (.bat) - MANDATORYInput file(s) (.in, .txt, etc.) - MANDATORYAI generated output file(s) - MANDATORYSample output - if provided in original specs package from FMXREF 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


QA Process Workflow cont.

QA Developer

Logs a new defect

Fix the issue

Closes the defect ID

HP-QC

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


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



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



HPQC Defect Window


HPQC: Defect Module Window HPQC: Defect Module Window


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

EDI Unit Testing Training

Documents

Transcript of EDI Unit Testing Training