3 ms·

Cool and all, but wouldn't one prefer db tests?

• lgeorget 7y ago
  Both are useful I'd say. Imagine a plug-in for your IDE that performs the static analysis and catches the syntax errors and some trivial semantic errors (typos in some field's name for instance) each time you save the file. I definitely find value in such a tool.
• gwd 7y ago
  Why use a typed language like Go at all then? Types and static compile-time checking catch different types of errors than tests do. I don't know about you, but I am not smart enough to write bug-free code consistently; I can use as much help as I can get. In any case, it takes quite a bit longer to run my test suite than it does to compile. Unfortunately, I tried to give it a spin, and it said: ERROR: sqlvet only supports projects using go modules for now. Ah well.
• zamalek 7y ago
  That strongly depends on whether you believe that static languages are useless in the face of unit tests, or whether you believe that static languages are improved by unit tests. The dynamic language camp would have no use for a tool like this.