davidben
commented
11 years ago Things to do:
- [x] Pick a unit testing story.
- How abou vows? Mozilla seems to use it for BrowserID, so it can't be completely insane?
- Although, I really don't understand what's the point of these "BDD" frameworks that want me to chunk up tests in these weird ways.
- The client is using this Mocha thing which is... also weird in ways, but at least we'd be using the same one?
- [x] Unit test some of the simpler functions
- [x] Split up the subscriber into two parts. One managers inner demons, the other maintains the save/prepare queues and has a single addMessage function.
- [ ] Mock up the database to test all the edge cases in stitching together save queue and the database
- [ ] Split out sockjs dependency from the connection manager as that too has complex query-stitching logic to test.
- [ ] Stress error handling too.
And on the other axis
- [ ] Figure out how to do integration tests or something for inner demon state and save queue state and all that.
No, seriously, you really need them.