| Closing it as deferred by the David Ffrench.
Following the email. David Ffrench
10:35 AM (2 minutes ago)
to Craig, me, Aerogear Hey Camila, You make very good points. Thank you very much for the code examples between the two testing methods using our own tests. Personally, I find it easier to read the tests wrote with assert, likely because I come from a Node.js assert testing background. I can guarantee we are not the first group to debate this topic for Go and this debate is always going to be somewhat subjective. For me, consistency is key. I want to be able to switch to another internal Go project, such as the other Mobile Services and Integreatly and be able to write tests in the same way. Even in OpenShift, there are only 61 references[1] to assert while there are 955 references[2] to the standard testing library. Personally, I would prefer to use your proposed method. However, thinking about the larger picture, taking into account the other projects in cloud services and staying consistent, it is my recommendation to use with the Go standard library in the Mobile Security Service. [1] https://github.com/openshift/origin/search?q=assert&unscoped_q=assert
[2] https://github.com/openshift/origin/search?q=t.errorf&unscoped_q=t.errorf |
