4 ms·

Hi Philip, You labast the lack of testing tools but one of the other blog posts [1] is about how you built a testing framework. We're just just being kind in

• philip1209 11y ago
  Testing support is basic and, when we started, there were no clear best practices - so we published how we organized our repo. The `@test foo` command basically raises an exception if the result is false. You have to manually register all of the tests and call them individually. setUp and tearDown has to be done manually. The testing library keeps no data about how many tests were run - it just throws an exception if an `@test` encounters a false. It works, but there is no sophistication.
  • idunning 11y ago
    This is partially fixed in Julia 0.5 (or available now as BaseTestNext.jl in Julia 0.4). Its basically a backwards-compatible rewrite of the former Base.Test that adds the notion of test sets - enabling counting tests by default, but also not immediately failing out on the first bad test and even logging.
• tavert 11y ago
  [1] = https://blog.staffjoy.com/test-driven-development-in-juliajk-8b66d3664852 https://blog.staffjoy.com/test-driven-development-in-juliajk... ?
  • SixSigma 11y ago
    Yes, thanks. Seems I didn't finish my post before I hit submit - someone came into the room to collect me and I had to log out quickly. By the time I noticed the edit window was closed.