As Matt says, embedded systems are not easy to work with. The only way we have been able to automate them is create a device simulation, and this only manages to simulate a subset of the code.
which is best way for capture and reply in embedded system testing?
As Matt says, embedded systems are not easy to work with. The only way we have been able to automate them is create a device simulation, and this only manages to simulate a subset of the code.
/embedded/ software testing?
that can be extremely challenging, and I'm afraid we don't know what you mean here.
If you can drive the device through inputs and outputs (plugged in to a cable) then you can drive it as sort of a black box. Another option is to use a simulator and drive the laptop. Good luck; tell us more about the device and I can give a better answer.
/embedded/ software testing?
that can be extremely challenging, and I'm afraid we don't know what you mean here.
If you can drive the device through inputs and outputs (plugged in to a cable) then you can drive it as sort of a black box. Another option is to use a simulator and drive the laptop. Good luck; tell us more about the device and I can give a better answer.
As Matt says, embedded systems are not easy to work with. The only way we have been able to automate them is create a device simulation, and this only manages to simulate a subset of the code.