How I improved my confidence, code quality and became a better developer

Manual testing was always an underrated part of my development. I worked under pressure to deliver fast, stable and predictable code. Usually, there was no time for writing valid test cases and test plans. Instead, any excuse was a good reason to skip …


This content originally appeared on DEV Community and was authored by Chris Witko

Manual testing was always an underrated part of my development. I worked under pressure to deliver fast, stable and predictable code. Usually, there was no time for writing valid test cases and test plans. Instead, any excuse was a good reason to skip it.

Lack of testing caused stress and anxiety. Every time I tried to deploy my code, I used to ask myself numerous, repeatable questions, e.g. did I miss some regression in the code? Didn't I forget to update environment variables, update config files, remove unnecessary comments from the code, and I could produce a list of many more serious questions.

Many companies need to iterate fast. Manual testing is often left behind. Popular combo (Google Doc + Excel) bring mess, confusion, and lack of control during the whole process. It does not help teams keep peace of mind during the development and release process.

We built ManualTesting.dev, a simple and powerful tool, to help my team and people like me write code, test it, and deliver on time with confidence.

So, if you have a list of test cases to review every time you deploy your code, or you have a checklist to review before a release, or you need a place to store user cases, new feature requirements and create test scenarios based on them, then this tool is for you.

And, as a developer, if you are looking for ways to deliver better code, control what to test and deploy, have peace of mind, reduce stress and anxiety, then this tool is for you as well. 😌

PS. "Any new application must be manually tested before its testing can be automated." — found it on the Internet.


This content originally appeared on DEV Community and was authored by Chris Witko


Print Share Comment Cite Upload Translate Updates
APA

Chris Witko | Sciencx (2022-02-15T08:25:08+00:00) How I improved my confidence, code quality and became a better developer. Retrieved from https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/

MLA
" » How I improved my confidence, code quality and became a better developer." Chris Witko | Sciencx - Tuesday February 15, 2022, https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/
HARVARD
Chris Witko | Sciencx Tuesday February 15, 2022 » How I improved my confidence, code quality and became a better developer., viewed ,<https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/>
VANCOUVER
Chris Witko | Sciencx - » How I improved my confidence, code quality and became a better developer. [Internet]. [Accessed ]. Available from: https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/
CHICAGO
" » How I improved my confidence, code quality and became a better developer." Chris Witko | Sciencx - Accessed . https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/
IEEE
" » How I improved my confidence, code quality and became a better developer." Chris Witko | Sciencx [Online]. Available: https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/. [Accessed: ]
rf:citation
» How I improved my confidence, code quality and became a better developer | Chris Witko | Sciencx | https://www.scien.cx/2022/02/15/how-i-improved-my-confidence-code-quality-and-became-a-better-developer/ |

Please log in to upload a file.



There are no updates yet.
Click the Upload button above to add an update.

You must be logged in to translate posts. Please log in or register.

Related Posts