3 ms·
Engineers should absolutely be writing unit tests and integration tests for their APIs. Personally I find that it brings a lot more integrity and a sense of own
by wefarrell 5y ago
Engineers should absolutely be writing unit tests and integration tests for their APIs. Personally I find that it brings a lot more integrity and a sense of ownership into the process when engineers are required to deliver tests.
I disagree with the problem's that you mention in this article:
Developers aren’t incentivized to prioritize QA testing
Developers are typically evaluated based on the quantity of software they ship, and how fast they ship it.
That's an organizational problem that is not universal and certainly won't be solved by a QA automation tool.
Developers’ job satisfaction goes down when they’re in charge of QA
Expanding upon one of the previous points:, we’ve seen that most developers just don’t enjoy doing QA.
This might be the case for manual testing but for automated testing the opposite is true. Delivering tests along with code increases integrity, makes debugging significantly easier, and helps clearly communicate the intention of each feature. This only works if there is collaboration between the developers and the product owner.
Clearly you have a viable product that works for many organizations, but it's certainly not a one-size-fits-all solution nor a best practice.
- ukd1 5y agoThanks. I agree re unit-tests and integration tests. Mostly we're focused on (and talking about) testing what humans end up using directly - e.g. interfaces to web apps or mobile apps. I think you're wrong re:organizational problems, it's part of it - but most developers (in my expereince) do not want to do QA outside of unit-tests and maybe integration tests. They want to write code, and ship things. Automation, at least traditionally is brittle as well as slow to write, and few love it. Whilst tooling like Cypress does improve things over Selenium, still, I've not met a developer that actually enjoys that kind of testing.