Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Thursday September 17, 2009
07:14 AM

Testing Remote Client Scheduling

[ #39638 ]

Imagine a client (Java)/server (Perl) set up. The client reads data from the server and based on the data it receives, it writes data back to the server. The client is running on a remote host and we can't run it locally. If the client receives data which indicates a major amount of writes, it schedules the writes for a time when server load is lowered.

What we were thinking of is having acceptance tests which conceptually do this:

  1. Load a bunch of fixture data into server
  2. Notify client that data is available via a particular host:port
  3. Block until client has processed data
  4. Verify that correct data is available in server

This didn't look to hard, but with the "schedule later in the day" part, acceptance tests could block for hours. That sucks. What's the best way to test this when viewing the client as a black box?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.