Testing is the Religion - Developers Best Practices

Why Testing is the Religion?

Best Practice 5 - Testing to be followed like a religion

Testing is obligatory after each little or enormous change regardless of how tight calendar you have or you simply changed a little remark inside the code, you have testing due for the changed code.

There is in no way like trust while creating software, regardless of how master or how senior you are in writing source code, you would need to perform testing for every single change you did in the code.

• Tight schedule, no compromise.
• Changed just a comment, still you have to test it.
• Changed just a variable name, testing has to be done.
• If you feel lazy...it's too dangerous.

If you don't want to follow it? You will be in trouble!

Celebrate every bug you find

Indeed, you ought not feel miserable on the off chance that you or another tester finds a bug in your software source code. Following are the enough motivations to praise this essential disclosure:

• Bugs are your enemies, so you have killed one.
• Now your software is having one bug less.
• Mistakes are good as long as they are not repeating.
• What you learn today, prepares you for tomorrow

Same time, don't condemn any developer on the off chance that any bug emerges in his/her code on the grounds that so far in any event I don't have a clue about any developer, who can compose without bug source code on the planet, second this is one reason we have a different stage in SDLC (Software Development Life Cycle) which we call after generation support (or support and upkeep).