Go, being a relatively new language doesn’t have a standard or best practice for mocking and testing.  We’re big into CI and unit testing and in order to do it right you need the right testing infrastructure in place.   Although golang’s standard library testing infrastructure requirements: partial mocking 3rd party & standard library mocking library


We have been playing around with some new languages here and have really taking a liking to the new GoLang project from Google. We have enjoyed the philosophy behind the project, the expertise and thought that went into ts development as well as the ease of implementation and ability to perform and scale. As a

photo (4)

We have always had the mentality at Socialize to not only do our best to test production products (especially critical ones) with coverage from an engineering perspective but more importantly understand that having information and transparency into general metrics within the company can keep each employee and manager from having to second guess themselves or

tl;dr: Check the Socialize JS Testing Framwork Out on GitHub At Socialize we believe that it is hard to move a product forward if those developing for it are constantly looking backwards chasing down bugs. Lacking the confidence that each change made to the code base will not create new problems elsewhere pulls innovation for