If is not tested, is not finished. For me QA and Devs must be best friends, their edge cases help us find edge solutions and in the end, the users have the best product possible.
And let's be honest, sometimes QA peers come with some bugs that are just, mind-blowing and I love that mindset.
Testing is the only way we can ensure a quality code. If is it easily broken maybe we need to check it out!
Yes, what I mean is always self-test. But occasionally, be meticulous, careful, and thorough like a true tester. And learn to think, reason like a tester while self-testing instead of having a 'happy case first' mindset during developing
Sometimes or...always.
If is not tested, is not finished. For me QA and Devs must be best friends, their edge cases help us find edge solutions and in the end, the users have the best product possible.
And let's be honest, sometimes QA peers come with some bugs that are just, mind-blowing and I love that mindset.
Testing is the only way we can ensure a quality code. If is it easily broken maybe we need to check it out!
Yes, what I mean is always self-test. But occasionally, be meticulous, careful, and thorough like a true tester. And learn to think, reason like a tester while self-testing instead of having a 'happy case first' mindset during developing
Totally agree with this. Always thoroughly test all of your work - manually. I usually find lots of stuff that QA miss