From 5151c5d750f4147db9ff8b429cf16c5d1068c8e7 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:06:09 +0100 Subject: [PATCH 01/13] Create whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester --- ...ong-with-i-dont-write-any-tests-i-am-not-a-tester | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester new file mode 100644 index 0000000..f0a49fa --- /dev/null +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester @@ -0,0 +1,12 @@ +--- +authorName: Peter Gfader +authorGithubUsername: peitor +issue: 149 +title: What’s Wrong With: “I don’t write any tests since I am not a tester”? +--- +# {{page.title}} + + + +*By {{page.authorName}}* + From 6438a49138f3551770ebeeb87191bba4880dd387 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:15:26 +0100 Subject: [PATCH 02/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester --- ...h-i-dont-write-any-tests-i-am-not-a-tester | 82 +++++++++++++++++++ 1 file changed, 82 insertions(+) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester index f0a49fa..3d23870 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester @@ -6,7 +6,89 @@ title: What’s Wrong With: “I don’t write any tests since I am not a tester --- # {{page.title}} +"Not a tester, so what are you then?" you might ask. +Being that offending is generally not helpful. +Unless you try to catch the attention as I do in this blog post 😉 +Let’s digest the situation in detail. +A friend of mine attended my [Scrum Developer class](https://www.scrum.org/courses/professional-scrum-developer-training) and caught fire during the "Testing" module where we talk about Code Quality, Testing, Test-First approaches, TDD and more. +Boom! After that class he was on a mission to convince everyone that TDD is the only way to do things. + +The 1st day back at work he talked about improving the team and trying TDD and got the following statement from his colleague: +Henri (made up name): "I don’t write any tests since I am not a tester". + +I know he handled the situation quite well, but he asked me for advice. + +One thing to consider is the underlying question to this, which might be: +"How do we get people to change their behavior?" +So here are my thoughts. + +**Yourself First** +First of all, think about things to consider for yourself: +* Why is the practice or tool that you are suggesting any better than the current way of doing things? +* Can you explain the value in the proposed change? +* Can you lead by example? +* Do you have enough patience and skills to teach others? +I would try to work on yourself before trying to change others. + + + +**Roles?** +I see that a lot of people are focused on their role, forgetting the bigger picture of the team and purpose of the work they are doing. +I would ask these questions: +* Are we one team that focuses on the Sprint Goal? + In a Scrum context there is no “tester”, “programmer” or “architect”, we are all professional engineers that deliver value through collaboration. +* No matter what, do we stand together and support each other? +* Are we doing whatever is necessary to deliver a usable product every Sprint? + + +**Done?** +Henri: "I don’t write any tests since I am not a tester". +Ask: "How do you know when you are done?" + +What is on our Definition of Done? +How can we build a usable, tested and fully integrated product increment every Sprint? +Are we doing that already? Why not? + + +**Tests are as important as documentation** +Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since documentation only documents how the software **might** work. +We learned too often that documentation gets out of sync too easily. +I blogged about the ["Why are *automated tests* so important?"](http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html) on my personal blog. + + + +**Quality** +Quality is everyone’s responsibility in a Scrum Team. There is no QA Team in a Scrum context, which means the whole Scrum team is responsible for delivering high quality software that works and is fully tested. + +Quality attributes that are important: +* Does it work at all? + Huh! +* Does it work well? +* Is it deployed and use-able? + Are the users able to access it? +* Is it useful? +* Is it successful? +* Does it make the impact we wanted to achieve? + -> Yes! Value is key + + +**Tests are code** +Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. + +Get test infected in 3 days in my Scrum Developer class! +Recently I did a a video interview where I ask my students 3 questions about the Developer class. +Check it out here https://www.youtube.com/watch?v=oLxBV4hPMkU + + + +**Still not willing to write tests?** +Ask: +* How can You help? +* What can You do? +You can always get them coffee. + +Show support. We are in this together. *By {{page.authorName}}* From 90925f9a306cab7759d7ba27a6a2af971736e2c6 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:16:20 +0100 Subject: [PATCH 03/13] Rename whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester to whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ... whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename articles/{whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester => whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md} (100%) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md similarity index 100% rename from articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester rename to articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md From a6269e63512d69c4c7a4acde890cefa5785e8930 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:18:10 +0100 Subject: [PATCH 04/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...-dont-write-any-tests-i-am-not-a-tester.md | 67 ++++++++++--------- 1 file changed, 34 insertions(+), 33 deletions(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 3d23870..1a4e0bd 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -6,9 +6,9 @@ title: What’s Wrong With: “I don’t write any tests since I am not a tester --- # {{page.title}} -"Not a tester, so what are you then?" you might ask. -Being that offending is generally not helpful. -Unless you try to catch the attention as I do in this blog post 😉 +"Not a tester, so what are you then?" you might ask. +Being that offending is generally not helpful. +Unless you try to catch the attention as I do in this blog post 😉 Let’s digest the situation in detail. A friend of mine attended my [Scrum Developer class](https://www.scrum.org/courses/professional-scrum-developer-training) and caught fire during the "Testing" module where we talk about Code Quality, Testing, Test-First approaches, TDD and more. @@ -30,10 +30,11 @@ First of all, think about things to consider for yourself: * Can you lead by example? * Do you have enough patience and skills to teach others? I would try to work on yourself before trying to change others. - + + -**Roles?** +**Roles?** I see that a lot of people are focused on their role, forgetting the bigger picture of the team and purpose of the work they are doing. I would ask these questions: * Are we one team that focuses on the Sprint Goal? @@ -42,53 +43,53 @@ I would ask these questions: * Are we doing whatever is necessary to deliver a usable product every Sprint? -**Done?** -Henri: "I don’t write any tests since I am not a tester". -Ask: "How do you know when you are done?" - +**Done?** +Henri: "I don’t write any tests since I am not a tester". +Ask: "How do you know when you are done?" + What is on our Definition of Done? How can we build a usable, tested and fully integrated product increment every Sprint? Are we doing that already? Why not? - + -**Tests are as important as documentation** -Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since documentation only documents how the software **might** work. -We learned too often that documentation gets out of sync too easily. -I blogged about the ["Why are *automated tests* so important?"](http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html) on my personal blog. - - +**Tests are as important as documentation** +Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since documentation only documents how the software **might** work. +We learned too often that documentation gets out of sync too easily. +I blogged about the ["Why are *automated tests* so important?"](http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html) on my personal blog. -**Quality** -Quality is everyone’s responsibility in a Scrum Team. There is no QA Team in a Scrum context, which means the whole Scrum team is responsible for delivering high quality software that works and is fully tested. + +**Quality** +Quality is everyone’s responsibility in a Scrum Team. There is no QA Team in a Scrum context, which means the whole Scrum team is responsible for delivering high quality software that works and is fully tested. + Quality attributes that are important: -* Does it work at all? +* Does it work at all? Huh! * Does it work well? -* Is it deployed and use-able? +* Is it deployed and use-able? Are the users able to access it? -* Is it useful? +* Is it useful? * Is it successful? -* Does it make the impact we wanted to achieve? +* Does it make the impact we wanted to achieve? -> Yes! Value is key - -**Tests are code** -Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. - -Get test infected in 3 days in my Scrum Developer class! -Recently I did a a video interview where I ask my students 3 questions about the Developer class. -Check it out here https://www.youtube.com/watch?v=oLxBV4hPMkU + +**Tests are code** +Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. + +Get test infected in 3 days in my Scrum Developer class! +Recently I did a a video interview where I ask my students 3 questions about the Developer class. +Check it out here https://www.youtube.com/watch?v=oLxBV4hPMkU -**Still not willing to write tests?** +**Still not willing to write tests?** Ask: * How can You help? * What can You do? You can always get them coffee. - -Show support. We are in this together. - + +Show support. We are in this together. + *By {{page.authorName}}* From 7d7e75803266c087373720747733be4ebb36d3a8 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:19:22 +0100 Subject: [PATCH 05/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...ng-with-i-dont-write-any-tests-i-am-not-a-tester.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 1a4e0bd..d9a0049 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -23,17 +23,16 @@ One thing to consider is the underlying question to this, which might be: "How do we get people to change their behavior?" So here are my thoughts. -**Yourself First** +**Yourself First** + First of all, think about things to consider for yourself: * Why is the practice or tool that you are suggesting any better than the current way of doing things? * Can you explain the value in the proposed change? * Can you lead by example? * Do you have enough patience and skills to teach others? I would try to work on yourself before trying to change others. - - **Roles?** I see that a lot of people are focused on their role, forgetting the bigger picture of the team and purpose of the work they are doing. I would ask these questions: @@ -77,11 +76,6 @@ Quality attributes that are important: **Tests are code** Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. -Get test infected in 3 days in my Scrum Developer class! -Recently I did a a video interview where I ask my students 3 questions about the Developer class. -Check it out here https://www.youtube.com/watch?v=oLxBV4hPMkU - - **Still not willing to write tests?** Ask: From 4717484a3101e7eba788b2a018c42cab9a1179de Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:20:43 +0100 Subject: [PATCH 06/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...i-dont-write-any-tests-i-am-not-a-tester.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index d9a0049..78365bd 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -23,8 +23,7 @@ One thing to consider is the underlying question to this, which might be: "How do we get people to change their behavior?" So here are my thoughts. -**Yourself First** - +## **Yourself First** First of all, think about things to consider for yourself: * Why is the practice or tool that you are suggesting any better than the current way of doing things? * Can you explain the value in the proposed change? @@ -33,7 +32,7 @@ First of all, think about things to consider for yourself: I would try to work on yourself before trying to change others. -**Roles?** +## **Roles?** I see that a lot of people are focused on their role, forgetting the bigger picture of the team and purpose of the work they are doing. I would ask these questions: * Are we one team that focuses on the Sprint Goal? @@ -42,7 +41,7 @@ I would ask these questions: * Are we doing whatever is necessary to deliver a usable product every Sprint? -**Done?** +## **Done?** Henri: "I don’t write any tests since I am not a tester". Ask: "How do you know when you are done?" @@ -51,14 +50,14 @@ How can we build a usable, tested and fully integrated product increment every S Are we doing that already? Why not? -**Tests are as important as documentation** +## **Tests are as important as documentation** Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since documentation only documents how the software **might** work. We learned too often that documentation gets out of sync too easily. I blogged about the ["Why are *automated tests* so important?"](http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html) on my personal blog. -**Quality** +## **Quality** Quality is everyone’s responsibility in a Scrum Team. There is no QA Team in a Scrum context, which means the whole Scrum team is responsible for delivering high quality software that works and is fully tested. Quality attributes that are important: @@ -73,11 +72,12 @@ Quality attributes that are important: -> Yes! Value is key -**Tests are code** -Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. +## **Tests are code** +Are you a coder?? Yes? +Tests are code. So write some tests, especially so that you can sleep better at night. -**Still not willing to write tests?** +## **Still not willing to write tests?** Ask: * How can You help? * What can You do? From 3c0a2baf50c92b7266a4bbc2328812ef9a84a505 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Fri, 2 Nov 2018 21:21:07 +0100 Subject: [PATCH 07/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...hats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 78365bd..28377a8 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -80,7 +80,8 @@ Tests are code. So write some tests, especially so that you can sleep better at ## **Still not willing to write tests?** Ask: * How can You help? -* What can You do? +* What can You do? + You can always get them coffee. Show support. We are in this together. From 4bb24da92c24b181f0ce6286baf3692e07121706 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Sun, 4 Nov 2018 16:32:44 +0100 Subject: [PATCH 08/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 28377a8..b28b30f 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -8,7 +8,7 @@ title: What’s Wrong With: “I don’t write any tests since I am not a tester "Not a tester, so what are you then?" you might ask. Being that offending is generally not helpful. -Unless you try to catch the attention as I do in this blog post 😉 +Unless you try to catch the attention as I do in this article 😉 Let’s digest the situation in detail. A friend of mine attended my [Scrum Developer class](https://www.scrum.org/courses/professional-scrum-developer-training) and caught fire during the "Testing" module where we talk about Code Quality, Testing, Test-First approaches, TDD and more. From 03ab779408d5102effb0b620618e667c5a20f47f Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Tue, 6 Nov 2018 12:45:54 +0100 Subject: [PATCH 09/13] Update whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md --- ...th-i-dont-write-any-tests-i-am-not-a-tester.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index b28b30f..d0786e3 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -49,13 +49,22 @@ What is on our Definition of Done? How can we build a usable, tested and fully integrated product increment every Sprint? Are we doing that already? Why not? + +## **Fast Automated Feedback** +Tests send you a message. They send you a message now and in 5 years from now. They tell you: +**Is the code working as it is expected or not?** +This fast feedback is very valuable if you are working on your product, either by changing it, fixing a bug or by adding a new feature. +Ask: "How do you know our product works in 5 years?" + + ## **Tests are as important as documentation** -Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since documentation only documents how the software **might** work. +Documentation is needed, and one good way to document how software **must** work are tests. I emphasize **must**, since written documentation only documents how the software **might** work. We learned too often that documentation gets out of sync too easily. -I blogged about the ["Why are *automated tests* so important?"](http://blog.gfader.com/2010/10/why-are-automated-tests-so-important.html) on my personal blog. + + + - ## **Quality** Quality is everyone’s responsibility in a Scrum Team. There is no QA Team in a Scrum context, which means the whole Scrum team is responsible for delivering high quality software that works and is fully tested. From 02c0023ba638994a11de03538730aaad75cb955f Mon Sep 17 00:00:00 2001 From: Christian Abegg Date: Tue, 20 Nov 2018 15:46:23 +0100 Subject: [PATCH 10/13] Update articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md Co-Authored-By: peitor --- ...whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index d0786e3..71ff788 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -11,7 +11,7 @@ Being that offending is generally not helpful. Unless you try to catch the attention as I do in this article 😉 Let’s digest the situation in detail. -A friend of mine attended my [Scrum Developer class](https://www.scrum.org/courses/professional-scrum-developer-training) and caught fire during the "Testing" module where we talk about Code Quality, Testing, Test-First approaches, TDD and more. +A friend of mine attended my Scrum Developer class and caught fire during the "Testing" module where we talk about Code Quality, Testing, Test-First approaches, TDD and more. Boom! After that class he was on a mission to convince everyone that TDD is the only way to do things. The 1st day back at work he talked about improving the team and trying TDD and got the following statement from his colleague: From 146f1f06f7e7f04a8c714dd902a5ff14dac2d146 Mon Sep 17 00:00:00 2001 From: Christian Abegg Date: Tue, 20 Nov 2018 15:46:35 +0100 Subject: [PATCH 11/13] Update articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md Co-Authored-By: peitor --- ...whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 71ff788..b0ab8f5 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -15,7 +15,7 @@ A friend of mine attended my Scrum Developer class and caught fire during the "T Boom! After that class he was on a mission to convince everyone that TDD is the only way to do things. The 1st day back at work he talked about improving the team and trying TDD and got the following statement from his colleague: -Henri (made up name): "I don’t write any tests since I am not a tester". +"I don’t write any tests since I am not a tester". I know he handled the situation quite well, but he asked me for advice. From 6ced1c4b42a8837527aa0759ad49bfbf764559c6 Mon Sep 17 00:00:00 2001 From: Christian Abegg Date: Tue, 20 Nov 2018 15:46:45 +0100 Subject: [PATCH 12/13] Update articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md Co-Authored-By: peitor --- ...whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index b0ab8f5..3109f8f 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -42,7 +42,7 @@ I would ask these questions: ## **Done?** -Henri: "I don’t write any tests since I am not a tester". +Colleague: "I don’t write any tests since I am not a tester". Ask: "How do you know when you are done?" What is on our Definition of Done? From 04674fe845191ae4252ca56aa10f0c8be66281e6 Mon Sep 17 00:00:00 2001 From: Peter Gfader Date: Wed, 21 Nov 2018 11:40:48 +0100 Subject: [PATCH 13/13] Added feedback from Adiran and Rolf Added 2 points from Adrian and point from Rolf about Devs write tests --- ...-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md index 3109f8f..68fab86 100644 --- a/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md +++ b/articles/whats-wrong-with-i-dont-write-any-tests-i-am-not-a-tester.md @@ -85,7 +85,14 @@ Quality attributes that are important: Are you a coder?? Yes? Tests are code. So write some tests, especially so that you can sleep better at night. + +## **Another 2 reasons for automated tests** +1. You help your Team. You support development with a very fast feedback loop. You will find tests covering small units very helpful as they allow to develop logic quickly and with high confidence. +Developers that design, code, test and drive their implementation with tests are much faster in developing software. +2. You help to reduce regression issues: Did you break any major functionality? Bigger tests that cover entire "user scenarios" are especially helpful here. + + ## **Still not willing to write tests?** Ask: * How can You help?