7 ms·
You're definitely that good. I hear you, and I know exactly how this feels. I've worked for two companies in the past year and a half, both with teams of ~5-1
by aye 12y ago
You're definitely that good. I hear you, and I know exactly how this feels.
I've worked for two companies in the past year and a half, both with teams of ~5-10 developers, and nobody at either company was/is using any sort of automated tests. It's definitely frustrating -- not to mention lonely -- especially when you're immersed in a culture (hello HN) that's pimping a new test runner every two weeks.
I like testing for one and a half reasons: to capture the software requirements, and to change the software easily when those requirements change. If you've got one test, that's better than zero.
You don't have to set up your own Jenkins server -- Travis CI should do the trick nicely, and it's super easy to set up (although I know you're not supposed to say that kind of thing).
Here's a thought: Could you persuade the CTO to let you add the tests as a submodule to the project repo?
- viredfox 12y agoNone of the cloud CI would work for us: we have an inhouse hosted git server (the CTO does not trust open source, in general). So to do automated testing, I'd have to set up a Jenkins server on my own.
- webmaven 12y agoThat's strike two against him. Have you had the conversation with him about why he feels that way about open source? The attitude about cloud services is more understandable, though inconvenient. However, I think you may be laboring under a misapprehension: You don't need to have a CI server to run tests automatically, you can have a test suite running locally and trigger it with a pre-commit hook (so you can't actually commit if a test fails).