i am not understanding this statement in Test Driven Development “Test code requires maintenance as well as production code”Disadvantages of Test Driven Development?Is it feasible to introduce Test Driven Development (TDD) in a mature project?Test driven development bookBash and Test-Driven DevelopmentExperiences with Test Driven Development (TDD) for logic (chip) design in Verilog or VHDLWhat are good examples of *perfectly acceptable* approaches that do not use/need/require test driven development?How can you ensure secure coding with Test Driven Development?Is there a workable approach to use Test Driven Development in a COBOL application?Is Test Driven Development the same as Test Driven Design?Meteor test driven development
What is the reason for cards stating "Until end of turn, you don't lose this mana as steps and phases end"?
Just how much information should you share with a former client?
Piece of chess engine, which accomplishes move generation
How to innovate in OR
Is it okay for me to decline a project on ethical grounds?
Why does the Rust compiler not optimize code assuming that two mutable references cannot alias?
Do 3/8 (37.5%) of Quadratics Have No x-Intercepts?
If the Moon were impacted by a suitably sized meteor, how long would it take to impact the Earth?
Rampant sharing of authorship among colleagues in the name of "collaboration". Is not taking part in it a death knell for a future in academia?
What are the closest international airports in different countries?
Why is my fluorescent tube orange on one side, white on the other and dark in the middle?
How does a poisoned arrow combine with the spell Conjure Barrage?
How to store my pliers and wire cutters on my desk?
What is a good example for artistic ND filter applications?
What clothes would flying-people wear?
How can Paypal know my card is being used in another account?
Do the books ever say oliphaunts aren’t elephants?
Is there an antonym (a complementary antonym) for "spicy" or "hot" regarding food (I DO NOT mean "seasoned", but "hot")?
Semen retention is a important thing in Martial arts?
how to understand the error info "Illegal parameter number in definition of reserved@a. ...t2+cdots+sqrt2}}_n项 , cdots 收敛.$}"
Is SecureRandom.ints() secure?
Do we need to "Bulkify" Flows?
How can I kill my goat?
How does the Thief's Fast Hands feature interact with mundane and magical shields?
i am not understanding this statement in Test Driven Development “Test code requires maintenance as well as production code”
Disadvantages of Test Driven Development?Is it feasible to introduce Test Driven Development (TDD) in a mature project?Test driven development bookBash and Test-Driven DevelopmentExperiences with Test Driven Development (TDD) for logic (chip) design in Verilog or VHDLWhat are good examples of *perfectly acceptable* approaches that do not use/need/require test driven development?How can you ensure secure coding with Test Driven Development?Is there a workable approach to use Test Driven Development in a COBOL application?Is Test Driven Development the same as Test Driven Design?Meteor test driven development
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
what is the meaning of this below statement, by Joosep Simm
Test code requires maintenance as well as production code....
test code grows linearly with production code. All lines of code require maintenance, which means cost. The cost is easiest to acknowledge when a change to existing functionality is made. The tests have to be modified as well as production code. This becomes a problem when multiple tests execute the same line of production code. This usually happens when there are too many high-level tests. The highest level test is an end-to-end test, which starts by invoking the GUI and goes all the way down to the data storage level. But it’s not only the highest-level test that can cause problems.
tdd
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
add a comment |
what is the meaning of this below statement, by Joosep Simm
Test code requires maintenance as well as production code....
test code grows linearly with production code. All lines of code require maintenance, which means cost. The cost is easiest to acknowledge when a change to existing functionality is made. The tests have to be modified as well as production code. This becomes a problem when multiple tests execute the same line of production code. This usually happens when there are too many high-level tests. The highest level test is an end-to-end test, which starts by invoking the GUI and goes all the way down to the data storage level. But it’s not only the highest-level test that can cause problems.
tdd
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38
add a comment |
what is the meaning of this below statement, by Joosep Simm
Test code requires maintenance as well as production code....
test code grows linearly with production code. All lines of code require maintenance, which means cost. The cost is easiest to acknowledge when a change to existing functionality is made. The tests have to be modified as well as production code. This becomes a problem when multiple tests execute the same line of production code. This usually happens when there are too many high-level tests. The highest level test is an end-to-end test, which starts by invoking the GUI and goes all the way down to the data storage level. But it’s not only the highest-level test that can cause problems.
tdd
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
what is the meaning of this below statement, by Joosep Simm
Test code requires maintenance as well as production code....
test code grows linearly with production code. All lines of code require maintenance, which means cost. The cost is easiest to acknowledge when a change to existing functionality is made. The tests have to be modified as well as production code. This becomes a problem when multiple tests execute the same line of production code. This usually happens when there are too many high-level tests. The highest level test is an end-to-end test, which starts by invoking the GUI and goes all the way down to the data storage level. But it’s not only the highest-level test that can cause problems.
tdd
tdd
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
edited Mar 27 at 1:52
VoiceOfUnreason
24.6k2 gold badges23 silver badges54 bronze badges
24.6k2 gold badges23 silver badges54 bronze badges
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
asked Mar 26 at 20:40
Saad BilalSaad Bilal
1
1
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38
add a comment |
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38
add a comment |
1 Answer
1
active
oldest
votes
Test code requires maintenance as well as production code
People might assume that they never have to read/adapt/improve test code after it has been written, except when the corresponding production code changes or the underlying feature needs to be enhanced.
That quote tries to give reasons to explain what that assumption "We don't have to improve our test code (independently of the production code)!" is wrong.
The point is: there are very specific requirements for test code. It should help you:
- to really test your production code and
- to quickly identify bugs
In other words: it is essential that your test code is also easy to read and maintain over time.
This means that after you are done developing and testing a feature, it can be worthwhile to improve your test code. To ensure that it didn't turn into hard to read spaghetti/legacy code that will give headaches in the future!
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55365855%2fi-am-not-understanding-this-statement-in-test-driven-development-test-code-requ%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Test code requires maintenance as well as production code
People might assume that they never have to read/adapt/improve test code after it has been written, except when the corresponding production code changes or the underlying feature needs to be enhanced.
That quote tries to give reasons to explain what that assumption "We don't have to improve our test code (independently of the production code)!" is wrong.
The point is: there are very specific requirements for test code. It should help you:
- to really test your production code and
- to quickly identify bugs
In other words: it is essential that your test code is also easy to read and maintain over time.
This means that after you are done developing and testing a feature, it can be worthwhile to improve your test code. To ensure that it didn't turn into hard to read spaghetti/legacy code that will give headaches in the future!
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
add a comment |
Test code requires maintenance as well as production code
People might assume that they never have to read/adapt/improve test code after it has been written, except when the corresponding production code changes or the underlying feature needs to be enhanced.
That quote tries to give reasons to explain what that assumption "We don't have to improve our test code (independently of the production code)!" is wrong.
The point is: there are very specific requirements for test code. It should help you:
- to really test your production code and
- to quickly identify bugs
In other words: it is essential that your test code is also easy to read and maintain over time.
This means that after you are done developing and testing a feature, it can be worthwhile to improve your test code. To ensure that it didn't turn into hard to read spaghetti/legacy code that will give headaches in the future!
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
add a comment |
Test code requires maintenance as well as production code
People might assume that they never have to read/adapt/improve test code after it has been written, except when the corresponding production code changes or the underlying feature needs to be enhanced.
That quote tries to give reasons to explain what that assumption "We don't have to improve our test code (independently of the production code)!" is wrong.
The point is: there are very specific requirements for test code. It should help you:
- to really test your production code and
- to quickly identify bugs
In other words: it is essential that your test code is also easy to read and maintain over time.
This means that after you are done developing and testing a feature, it can be worthwhile to improve your test code. To ensure that it didn't turn into hard to read spaghetti/legacy code that will give headaches in the future!
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
Test code requires maintenance as well as production code
People might assume that they never have to read/adapt/improve test code after it has been written, except when the corresponding production code changes or the underlying feature needs to be enhanced.
That quote tries to give reasons to explain what that assumption "We don't have to improve our test code (independently of the production code)!" is wrong.
The point is: there are very specific requirements for test code. It should help you:
- to really test your production code and
- to quickly identify bugs
In other words: it is essential that your test code is also easy to read and maintain over time.
This means that after you are done developing and testing a feature, it can be worthwhile to improve your test code. To ensure that it didn't turn into hard to read spaghetti/legacy code that will give headaches in the future!
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
answered Apr 2 at 12:46
GhostCatGhostCat
107k17 gold badges105 silver badges180 bronze badges
107k17 gold badges105 silver badges180 bronze badges
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
add a comment |
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
I would argue that test will help to quickly identify bugs, because if this is a logic bug (not a spelling, missing value mistake), then the test will be written following "bug" logic.
– Fabio
Apr 6 at 2:15
add a comment |
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55365855%2fi-am-not-understanding-this-statement-in-test-driven-development-test-code-requ%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Without any formating, it is not clear what parts of your question are the “statement” you say you are confused by, and your own commentary.
– Don Simon
Mar 26 at 20:47
Please edit your question to format it properly. What is that your do not understand? The part of sentence reported in the title?
– Marco Torchiano
Mar 26 at 21:04
And please clarify if the provided answer goes in the right direction and is helpful for you.
– GhostCat
Apr 6 at 4:38