Tests for repeatAt
this.attrs.nextRunAt is calculated based off the repeatAt property
Documentation
Careful to not run the job repeatedly at that exact minute
Merge pull request #81 from nwkeeley/feature/job-repeatAt

Feature/job repeat at
add example project structure
Release 0.6.17
Fixed complete event being emitted before asynchronous jobs are finished
Fixed issue where jobs would continue being processed after agenda is explicitly stopped
Implemented job.isRunning()
Adjustment to use _processInterval instead of _stopped
Merge pull request #87 from snez/master

2 bugfixes
Release 0.6.18
clean up computeNextRunAt
Create database indexes when initializing Agenda instance
remove agenda-test.js file
add more timeout to jobs for travis
Release 0.6.19
Added jsHint globals, fixed semi-colons, test fix.

What started as a simple "Let's see what jsHint issues arise"
made me find a couple things.

One section was missing semi-colons, which I added (which is
just a styling change).

After fixing globals and the semi-colons, I found a section that
was referencing a variable that wasn't actually set.  I saw in
a similar test created it before starting the increment, which I
blindly copied into the test.

Tests passed before and after the changes.  These are all styling
changes.
Added beginings of integration tests.

So this adds a few tests using the child_process.fork() method,
in the attempt to recreate starting/ restarting conditions that
may occur for a service or application.

These have been broken into each job assignment method.

.each()
  - Ensures jobs do not get re-ran after restart.
  - Ensures array names still have jobs ran.

.schedule()
  - Ensures on startup future jobs do not get ran.
  - Ensures jobs scheduled before current time get ran.
  - Ensures array names still have jobs ran.

.every()
  - Ensures job gets ran as soon as possible.

There are a few nitpicks here that I still have, such as using
path.join() to ensure this can be tested in non-Unix enviroments.

Seeing as this uses Make, I am not 100% sure how useful
cross-compatibility is, not to mention I haven't validated that
the rest of the codebase uses path.join() either.