hexops
Achieve 100% test coverage
Will need to make our testing suite much less verbose for this. Ideally we will just perform some Vecty operations in the test suite (e.g. RenderBody) and get an output list of strings or something non-verbose of exactly which DOM operations occurred.
Things we should also ensure we have tests for:
- [ ] Add testing for 'idiomatic way to pass child component lists into an element's constructor' #78
- [ ] #167
- [ ] #249 (
RenderInto/RenderIntoNode)
@pdf FYI I haven't finished yet but I do have a quite extensive change to move us over to a nicer test suite that is more data-driven and just produces a list of expected vs. gotten DOM operations & will make it much easier to test correct behavior in Vecty without writing crazy verbose DOM mocking code. Just wanted to let you know so you don't do anything too extensive in the test suite any time soon :)
Actually I had some spare hours, so I moved the entire test suite over and sent https://github.com/gopherjs/vecty/pull/178 :)
Still todo here is adding more tests to achieve 100% coverage, but it should be a lot easier once that PR is merged.