Posted on
A lot of posts talk about writing tests but I feel writing tests for a side project is a real drag, maybe i'm just a very lazy person. What about you?
PS: Any kind of tests. 😇
For further actions, you may consider blocking this person and/or reporting abuse
The top 50 must-have CLI tools, including some scripts to help you automate the installation and updating of these tools on various systems/distros.
Alex Pla Alonso -
NaveenKumar Namachivayam ⚡ -
NaveenKumar Namachivayam ⚡ -
Kailash P. -
Once suspended, devusman will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, devusman will be able to comment and publish posts again.
Once unpublished, all posts by devusman will become hidden and only accessible to themselves.
If devusman is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Usman Suleiman.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community 👩💻👨💻 safe. Here is what you can do to flag devusman:
Unflagging devusman will restore default visibility to their posts.
Top comments (2)
I was not writing any test for any kind of projects before. Then, I realized I'm doing too effort to test something manually to check if it is broke or not. Also, I can't be brave to refactoring or deleting piece of code. So, I decided to write test to improve my productivity and self-confident. I don't force myself to write test for every piece of code but I try to write test for important parts or for parts which are too many times I've made manual test on.
So it does not matter if it's side-project or main-project. It's related about the productivity I think.
I don't want to make manual test over and over any more. :)
I actually test more in side projects