👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
Sure, but the quality pretty quickly suffers in that you have no regression tests unless you very clearly specify the manual test cases and test steps. These manual tests have to be followed very carefully at least before each new release and deployment.
When I feel very confident about some code I leave out tests but often discover stupid bugs like a boolean being the reverse of what is expected in a specific state. Depending on the difficulty of the deployment process and the critical level of the project, I ramp up the amount of automated tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Don't you use manual testing at all?
Sure, but the quality pretty quickly suffers in that you have no regression tests unless you very clearly specify the manual test cases and test steps. These manual tests have to be followed very carefully at least before each new release and deployment.
When I feel very confident about some code I leave out tests but often discover stupid bugs like a boolean being the reverse of what is expected in a specific state. Depending on the difficulty of the deployment process and the critical level of the project, I ramp up the amount of automated tests.