Open joshuagruenstein opened 8 years ago
I think there are solutions to test across a wide range of browsers. I think I've seen a little badge in a README that showed individual browsers passing or failing, which would be nice.
Travis charges for private repos
We can use the Karma test runner to test across multiple browsers. I'm like Jasmine as an assertion library.
What are some of the unit tests tests that you are considering? We can check to see if a number of examples that encompass all of the smooth functionality render in the predictable way. However, do you have any ideas for more fine grained tests? Ex. testing the req
function by giving it the URL for a predictable API
We can do templating tests, pipe tests for all three types, guard tests, handler tests, model tests, request tests, and minimorph tests to start. I think for a small library like snooze, 100% coverage is a reasonable goal.
Is it necessary to test minimorph? I assume that the original library is tested. Do we need to test their code? Can we steal their tests?
I've been rewriting minimorph pretty aggresively, so yeah we definitely need to test it.
Just curious, what have you rewritten?
Most of what I've been done has been cutting things down, and rewriting after to fill in the holes. MorphDOM is 530 lines, Minimorph is 120. However, I have completely rewritten attribute morphing.
Letting you know @truell20, legit rewriting Battlecode 2019 in snooze rn.
stop
for fun or for real?
@truell20?