Has anyone had good success with building test automation solutions for EDI test teams? Would love to hear any general or specific suggestions/feedback from you.
My company (large health insurance company) is particularly interested in test automation for the 835/837 transactions. Major current challenges for manual testers include:
- generating 837 X12 test data to pass into the claim engines, and
- validating the resulting 835 data.
They are open to either fully automated or semi-automated solutions, and require a solution in place in 3-4 months.
I appreciate any ideas or suggestions or things to consider/be careful of.
Thanks in advance for your thoughts!!!!!
One of my former co-workers in a previous life (probably one of your competitors) used an Access database to facilitate some of what you are looking for. He used the database to do the very things you describe. That is, generating data and validating the resulting data. By no stretch of the imagination was it an easy task, but over the course of a number of years, he was able to build up a number of databases that would serve the purposes of the test team.
I don't have any great recommendations other than for you to consider how to link the original 837 data and the resultant 835 data. That's the trick. A good Access application developer should be able to get you close to where you would like to be.
I work for a Health Care ASP (communications platform) and do a lot of testing with EDI (claims, e&b, etc). I do mostly performance related stuff (lots of EDI over web services and mq-series), but have built some of my own tools. Do you have specific questions?