Start work on a new library that can be used to stress-test Regard. (Making this a library so we can easily turn it into a cloud service if needed)
Set up some options for the stress test library
Start work on the actual stress-testing algorithm (sending events to the endpoint)
Periodically (every 10s) write some statistics about how it's going
Generate and send the events to the endpoint
Check for and count errors
Add a command-line version of the stress tester
Fix the startup display
Oops, fixed issue which was stopping us from completing an event
Change test runtime to 60 seconds for now
Try to reproduce the circumstances of the 'negative' bug by adding a routine that adds events for existing users instead of creating new ones.
Include the 'initial' events in the count
Add a check of the underlying event count. This seems to produce a failure when using the Azure table storage engine
The bug is happening only when using Azure storage, so change this test to use Azure storage (it now fails)
Use a reduced event count so that the test will complete in a reasonable time on our servers
Commit the cache before re-reducing (seems to fix negative values bug)
Update query version to force any broken queries to re-run