Aastha Sinha	Abhijeet Shah	Abhishek Suranglikar
Abhishek Tanwade	Abhishek Tiwari	Ajinkya Pathak
Amit Pawade	Ankita Kulkarni	Ankita Patidar
Antara Datta	Anup Manekar	Ashish Baldota
Chandra Gosetty	Deep Shikha Bhat	Dr. Girish Shinde
Ekta Shah	Gaurav Mishra	Gaurav Rathod
Gautam Patil	Harish Singh Chauhan	Harshali Chandgadkar
Kapil Joshi	Krishna Gunjal	Madhavi Pawar
Marappa Reddy	Mayur Wankhade	Milan Pansuriya
Minal Doiphode	Mohit Agarwal	Mohit Borse
Nalini Vijayraghavan	Nikhil Kulkarni	Omkar Ingawale
Omkar Kulkarni	Pooja Chavan	Pooja Dhule
Pranit Gangurde	Prashant Kankokar	Priya Patole
Rahul Ganorkar	Rashmi Nehete	Ravi Agrawal
Robin Pandita	Rohan Chavan	Rohini Wwagh
Sachin Saini	Sadhana Sharma	Sambid Pradhan
Sandeep Mali	Sanjay Toge	Sanjeev Fadnavis
Saurabh Pimpalkar	Sayanti Shrivastava	Shardul Gurjar
Shravani Dhavale	Shreyash Bhoyar	Shubham Kamble
Shubham Muneshwar	Shubham Navale	Shweta Chinchore
Sidhant Naveria	Souvik Adhikary	Sujay Hamane
Tejbahadur Singh	Uddhav Dandale	Vasishtha Ingale
Vidisha Chirmulay	Yogesh Kulkarni

Software Engineering | 05 Jun 2015 | 4 min

EDI Testing using BizTalk Integration Engine

To implement interoperability, enterprises are implementing integration gates that allow seamless data exchange within or between organizations. BizTalk integration engine is industry-leading integration software that helps organizations implement interoperability. BizTalk web services, including the BizTalk server and BizTalk EDI applications are being extensively discussed in the industry today.

Data exchange occurs in various formats. Communication formats common in healthcare organizations are Health Level 7 (HL7 files), Electronic Data Exchange (EDI files), custom format (txt/XML files) etc. according to the organization’sneed/requirement. Testing various format with the BizTalk Integration engine is the challenge. Moreover, different testing approaches require different testing formats. The current blog explores EDI testing using the BizTalk integration engine.

Typical challenges associated with this are:

Test data generation
Data integrity
Test environment availability

In order to have EDI Testing, two approaches are required to define testing strategies:

EDI Testing – format testing, data testing
Integration Testing – BizTalk integration engine implementation

1 EDI Data Testing

The testing Strategy should include below mentioned testing types:

2 Application Integration Testing – BizTalk

The Application Integration Testing strategy focuses on business requirements and end-to-end testing of the application/system involved in integration. Mentioned below are high-level points that Application Testing should cover:

A separate test environments functionality is provided by BizTalk. This allows QA to conduct testing separately in test environment.
Testing scenarios should focus on business rules validation and verification.
Data exchange between/among systems
Test scenarios across BAM (Business Activity Monitoring)
Test manually retrying orchestration for suspended messages
Test interruptible orchestration by sending interruption message
BPM scenarios focusing on data patterns – in our case EDI837I, P, & EDI 834
Security testing as per compliance rules laid out by HIPAA

To ensure 100% testing coverage, the recommended testing strategy build will be a “Hybrid” testing strategy – EDI Testing & Application Integration testing. An Application Integration testing strategy ensures that data exchange is proper and there is no impact to the business processing. On the other hand, EDI testing ensures that no data is lost & no junk/unwanted data is processed in data exchange.