Repository navigation
Create behavior concern tests #152
Description
Activity
Definitely interesting. I think we should do a little exploratory hacking to validate the approach. My concern is that it becomes difficult to inject things required by the business logic. Things like injecting auth credentials, etc.
yup. absolutely, the point here is not to test custom business logic, but to test default standard behavior of REST api that was generated by redbeard.
as for injecting the credentials,
doubleagenthas you covered:const { app, itBehavesLikeCRUDResource } = require('../helper'); describe("/users route", () { beforeEach(function * () { const user = yield new User({... }).save(); const token = yield generateToken(user); app.defaultHeaders = { Authorization: `Bearer: ${token}` }; }); itBehavesLikeCRUDResource(app); });
Ooooh, fancy. Yeah, looks like that'll work.
after the controllers and routers are uniformed and auto-generated, we can also start generating tests as well. something like this:
eventually we could split those into specific concerns like,
itListsThingsProperly,itCreatesNewRecordsCorrectly, etc.