How Automated Tools are used for EDI testing?
I would like to know, how automated tools in general and WinRunner in particular can be used for EDI testing?
What feature of WinRunner is to be used to test EDI Transactions, both Inbound and Outbound?
Re: How Automated Tools are used for EDI testing?
For performance issues please see http://www.qaforums.com/Forum34/HTML/001190.html
On the functionality side, let's examine winRunner (or any automated testing tool's) basis in the scientific method. YOu have initial conditions, a hypothesis to test against, steps to reproduce and any control factors. For each step there is an expected result. In the case of WinRunner, the majority of the types of tests that it is used for check for expected results in a graphical user interface, so the main question to ask is how you initiate an EDI transaction and verify that one has taken place (successfully or not).
My assumption (and you know what assuming gets you) is that your Windows based PC that runs WinRunner is not initiating the EDI transaction, so you will likely be ioperating in a terminal emulated environment to initiate and check the results of the EDI transaction. WinRunner can certainly operate end user interfaces, includign terminal eumlators. WinRunner can synchronize it's behavior as a user, waiting for certain information to appear on a screen bfroe continuing, and WinRunner can watch for certain information to appear and validate that information against a known good source to check to see whether a transaction has completed successfully or not.
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes