I'm new to TDD, and the first question that came to my mind is whether unit tests should be applied for each component developed. I ask for this, since I noticed that unit testing takes a lot of time, especially when some changes to the requirements are provided. So, could you suggest something like TDD best practices regarding unit testing?
A brief description of TDD, expressed in three rules :
: http://jamesshore.com/Agile-Book/test_driven_development.html
: http://www.growing-object-oriented-software.com/
-
,
. , , . , , , : " ". . , - , , , , , , , , , . 2 , , , .
. , , , . .
, , , - , , , , , . .
TDD , . unit test, , . , :
, .
Tests lead to the development of your code. TDD is really everything to determine the desired behavior of your software, the fact that everything it checks is a good side effect.
A good essay on TDD is available here.
Source: https://habr.com/ru/post/1754009/More articles:Как применить другое правило проверки в соответствии с типом полиморфной ассоциации (Rails)? - ruby-on-railsВиброзвонок телефона Android не прекращает использовать метод отмены - androidAccess audio samples from a linear telephone - linuxFacebook: Is there a way to verify that I have certain permissions? - facebookString Format to show a currency with two decimal places only if there are decimal numbers (.net) - stringНевозможно преобразовать из HttpContextBase в HttpContextBase - c#C ++: How to link the library located in my project folder? - eclipseHow to cite a document with multiple authors using natbib - latexAnonymous function in an array - functionConfirm Close Colorbox - javascriptAll Articles