Is there any smooth way to test the Pike Protocols, for instance for client/server applications where you need to be asynchronous or to spawn off subprocesses?
Is it possibly to design such a setup?
What do you want to test? Is it some kind of scripted delays to test odd orders?
Generally speaking, it's just a matter of writing a test client and server and run them from the testsuite. I don't see much that can be reused. Possibly a convenience function to find an unused port.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-12-09 19:14: Subject: client-server/agent testsuite
Is there any smooth way to test the Pike Protocols, for instance for client/server applications where you need to be asynchronous or to spawn off subprocesses?
Is it possibly to design such a setup?
/ Mirar
For instance HTTP server and client in the variations {sync,async,threaded} {http,https}.
Can you run asynchronous and threaded stuff from the testsuite?
I would also like some sort of centralized port/socket generator... But that's not a big problem.
/ Mirar
Previous text:
2003-12-09 20:52: Subject: client-server/agent testsuite
What do you want to test? Is it some kind of scripted delays to test odd orders?
Generally speaking, it's just a matter of writing a test client and server and run them from the testsuite. I don't see much that can be reused. Possibly a convenience function to find an unused port.
/ Martin Stjernholm, Roxen IS
Can't see why it wouldn't work. You can always write the tests in separate programs (see e.g. src/modules/files/socktest.pike). When you start writing elaborate tests like that you probably want to have them separate anyway.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-12-09 20:59: Subject: client-server/agent testsuite
For instance HTTP server and client in the variations {sync,async,threaded} {http,https}.
Can you run asynchronous and threaded stuff from the testsuite?
I would also like some sort of centralized port/socket generator... But that's not a big problem.
/ Mirar
Yes, why not... Speaking of which, shouldn't the test-all-modules test be a separate script?
And one more thing, it's getting very tricky to read out which test(s) failed. Maybe a renovation of the testsuite output would be in order?
I can think of a testsuite program that outputs stuff that a parent program handles and formats, to be able to handle segfaults and other nastiness.
/ Mirar
Previous text:
2003-12-10 02:28: Subject: client-server/agent testsuite
Can't see why it wouldn't work. You can always write the tests in separate programs (see e.g. src/modules/files/socktest.pike). When you start writing elaborate tests like that you probably want to have them separate anyway.
/ Martin Stjernholm, Roxen IS
pike-devel@lists.lysator.liu.se
-
Martin Stjernholm, Roxen IS ＠ Pike developers forum -
Mirar ＠ Pike developers forum