Rent's due today, thank heavens I just got paid.
I don't set up standing orders, got burned once with unarranged overdraft fees, that wasn't a good mont...
I write unit tests and test my own code, but we also have UAT tests that are completed by others independently. Complex systems with lots of moving parts require lots of testing.
But you can validate the business rules with the people that make them: the business or your users?
I get some companies do things pretty fucking backwards and QA as a separate function is harmful, pointless and should be abandoned.
However, I don’t see how anyone from QA is going to physically stop your from testing and validating your code. As a dev, you could be more proactive in understanding what you’re building, why you’re building it, and how to make sure it works and it does what your stakeholders/users need it to do.
You don’t test your own code as well?
I write unit tests and test my own code, but we also have UAT tests that are completed by others independently. Complex systems with lots of moving parts require lots of testing.
Technical testing still leaves a lot of potential issues with business rules, UX etc…
But you can validate the business rules with the people that make them: the business or your users?
I get some companies do things pretty fucking backwards and QA as a separate function is harmful, pointless and should be abandoned.
However, I don’t see how anyone from QA is going to physically stop your from testing and validating your code. As a dev, you could be more proactive in understanding what you’re building, why you’re building it, and how to make sure it works and it does what your stakeholders/users need it to do.
If you don’t, then refer to OP’s post.
Oh I get that. Just sounded like passing all testing responsibilities off to others.