I need to perform integration testing of Laboratory Automation System (LAS) and an analyzer (hardware), where data is communicated through a serial port (RS232). The analyzer is physically not available neither is the simulator.
Under these condition what are the options to test the communication messages between the two.
Well if you don't have all of the necessary hardware to actually test that the functionality is correct (ie the analyzer or simulator) then you can really only test the communication one way. You can't really test the response because whatever you're talking to won't be able to respond in the same manner as the hardware you're supposed to be sending the command to.
We get this from time to time in my shop and what we actually do is we'll connect from one computer to another. On the computer you'll be sending to, open HyperTerminal (from Accessories>Comunication) on Windows and then set up all the proper communication settings for Serial. Oh yeah, when you're setting it up you'll need to select a COM connection over a modem connection.
That should do it. When you communicate with it you should see the information come through on HyperTerminal.
[ QUOTE ]
OOOH! Is RS-232 still around? At one time I knew that baby inside out and backwards, but it is so long ago ...
[/ QUOTE ]
YEAH! I KNOW! I thought the same thing before I started here. In our case, we will work with a lot of custom devices that still work on RS-232, but we also actually build new product that also still integrates with RS-232. Mostly I think it's for compatibility, but there are cases where the devices are being used in secure environments where they will use RS-232 over Ethernet just to further ensure the security of the data being sent over the wire.
It's amazing, really. Just for your amusement, we also use RS-422.