Reverse the order of the routes

why? because reasons!

by default, express route definitions are "first-in wins".
that means when you're building an app you want to start with
specific routes and then declare increasingly generic routes.

however, test stubs typically want to be declared in the reverse
order. that is to say, a general stubbing is made at the top
of an example group so that it can cascade downward (to nested
example groups), whereas nested example groups typically want
to declare more specific routes to facilitate the specific
needs of the test.

lib/covet.coffee

@@ -18,7 +18,9 @@ module.exports =
         else
           res.send(400)
 
-      stubbedRoutes.push(_(app.routes[stubbing.verb]).last())
+      newRoute = _(app.routes[stubbing.verb]).last()
+      app.routes[stubbing.verb] = [newRoute].concat(_(app.routes[stubbing.verb]).initial())
+      stubbedRoutes.push(newRoute)
       res.send(201)
 
     app.delete config.routes.resetRoutes, (req, res) ->

spec/lib/covet_spec.coffee

@@ -161,3 +161,24 @@ describe 'covet', ->
             expect(res.statusCode).to.equal(400)
             done()
 
+    describe "overriding routes", ->
+      beforeEach (done) ->
+        post 'covet/routes',
+          verb: 'get'
+          path: '/bunnies/:id'
+          response:
+            json:
+              name: "Default Bunny"
+        , ->
+          post 'covet/routes',
+            verb: 'get'
+            path: '/bunnies/3'
+            response:
+              json: BUNNY
+          , ->
+            done()
+
+      it 'gets the more-specifically-stubbed bunny', (done) ->
+        get "bunnies/3", (body) ->
+          expect(body).to.deep.equal(BUNNY)
+          done()