Return to Answer

Just one thing- Test to confirm it does not work.

Test with a mindset to confirm it does not work in atleast 3 different cases.If as a developer one does not understand atleast 3 different ways to break his own code, he does not understand his own code well. Look for the weaknesses in your own code as if it's of somebody else.It will not only help the tester in getting a working, solid piece of code , it will greatly enhance your knowledge & reputation as a developer within the team in long term where ever you work.

Your reputation will proceed you wherever you go as a solid developer!

Just one thing- Test to confirm it does not work.

Test with a mindset to confirm it does not work in at least 3 different cases.If as a developer one does not know at least 3 different ways to break his own code, he does not understand his own code well.

Look for the weaknesses in your own code as if it's of somebody else.It will not only help the tester in getting a working, solid piece of code , it will greatly enhance your knowledge & reputation as a developer within the team in long term where ever you work.

Your reputation will proceed you wherever you go as a solid developer!

Just one thing- Test to confirm it does not work.

Test with a mindset to confirm it does not work in atleast 3 different cases.If as a developer one does not understand atleast 3 different ways to break his own code, he does not understand his own code well. Look for the weaknesses in your own code as if it's of somebody else.It will not only help the tester in getting a working, solid piece of code , it will greatly enhance your knowledge & reputation as a developer within the team in long term where ever you work.

Your reputation will proceed you wherever you go!

Just one thing- Test to confirm it does not work.

Test with a mindset to confirm it does not work in atleast 3 different cases.If as a developer one does not understand atleast 3 different ways to break his own code, he does not understand his own code well. Look for the weaknesses in your own code as if it's of somebody else.It will not only help the tester in getting a working, solid piece of code , it will greatly enhance your knowledge & reputation as a developer within the team in long term where ever you work.

Your reputation will proceed you wherever you go as a solid developer!

Have 3 amigos.

The 3 Amigos (in case you don't know)is a meeting where the Business Analyst presents a business requirement coupled with test scenarios (collectively called a “feature”) for review by a member of the development team and a member of the quality assurance team. This helps to build an shared understanding between all 3 of them.

Make sure your develop the feature as per this shared understanding and cover these test scenarios as part of unit testing up to possible extent.

I found this very helpful to have open conversation between Developer & tester to divide which part to cover on unit level(developer) & integration/end to end test level(tester).

Just one thing- Test to confirm it does not work.

Test with a mindset to confirm it does not work in atleast 3 different cases.If as a developer one does not understand atleast 3 different ways to break his own code, he does not understand his own code well. Look for the weaknesses in your own code as if it's of somebody else.It will not only help the tester in getting a working, solid piece of code , it will greatly enhance your knowledge & reputation as a developer within the team in long term where ever you work.

Your reputation will proceed you wherever you go!