Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 20 Jan 2014 21:49:20 +0000 (UTC)
From: "Evan Reynolds (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12689873.1390248499411.36400.1390254560187@arcas>
In-Reply-To: <JIRA.12689873.1390248499411@arcas>
References: <JIRA.12689873.1390248499411@arcas>
Subject: [jira] [Updated] (SCXML-189) Event Replay Scheduler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SCXML-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evan Reynolds updated SCXML-189:
--------------------------------

    Attachment:     (was: ReplayScheduler.java)

> Event Replay Scheduler
> ----------------------
>
>                 Key: SCXML-189
>                 URL: https://issues.apache.org/jira/browse/SCXML-189
>             Project: Commons SCXML
>          Issue Type: New Feature
>            Reporter: Evan Reynolds
>            Priority: Minor
>
> It can be very hard to unit test state machines that have timers. It can also be hard to replay events in a timely fashion - you hit the timer, and unless you're willing to wait, you can't test.
> This is a timer class that I used that acts as a normal event dispatcher. But instead of firing events on a normal schedule, it makes a call available to register the current time. If you call that with new time values, it will fire off any events that have been started that need to be fired off.
> So to use this to replay events, simply register the time the event happened, then fire the event. All timers will then take care of themselves. To use it to unit test events, you can go into a state with a timer, call the register time method to move the clock up until the timer should fire, and watch to see what happens.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)