![]() ![]() squishrunner directs the AUT to perform whatever actions the test script specifies.Īll the communication takes place using network sockets which means that everything can be done on a single machine, or the test script can be executed on one machine and the AUT can be tested over the network on another machine. With the hook in place, squishserver can query AUT objects regarding their state and can execute commands on behalf of squishrunner. The hook is a small library that makes the AUT's live running objects accessible, and allows communication with squishserver. squishserver starts the instrumented AUT on the device, which starts the Squish hook. The test script is executed by the squishrunner tool, which in turn connects to squishserver. Squish runs a small server, squishserver, that handles the communication between the AUT and the test script. The ability to do remote testing is particularly useful for testing AUTs that run on multiple platforms and for testing AUTs that run on embedded devices. For example, it makes it easier to store the test scripts in a central location and to perform remote testing on different machines and platforms. In addition to insulating Squish and test scripts from AUT crashes, running the AUT and the test script in separate processes brings other benefits. In such cases, the test script will fail gracefully and log an error message. This ensures that even if the AUT crashes, it should not crash Squish. One fundamental aspect of Squish's approach is that the AUT and the test script that exercises it are always executed in two separate processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |