3 ms·
For large/ambitious cljs apps I'd recommend unit-testing each devcard somehow. At work we haven't done it and it's a regret - not cool to find an outdated devc
by vemv 9y ago
For large/ambitious cljs apps I'd recommend unit-testing each devcard somehow.
At work we haven't done it and it's a regret - not cool to find an outdated devcard that doesn't work anymore.
(not a flaw in Devcards itself)
- vemv 9y agoIn addition: by testing a devcard you also, of course, are implicitly exercising the underlying code. So instead of writing a test for code X, you can test a devcard using X instead, and kill two birds with one stone. Especially true if you're doing integration-testing, Selenium-style.