Net core Test Driven development is significantly different than TDD of MVC project development I described four years ago Unit-тести для ASP.NET MVC and something testing technique I invented by himself Моя CMS для ASP.NET MVC, and it this page I want to describe new pattern of TDD in Net Core.
At common there are no big difference in 3 big competitor test framework xUnit, nUnit and MSUnitTest, because ant operation is possible to make in any framework - Comparisons testing framework, and full list of testing framework see please in this page Comparisons testing framework (wikipedia). Main difference is how to write to log, how to initialize test environment and so on, but if you use one framework than answer to any your questions about another framework you will receive in seconds by googling.
What benefits and disadvantages of TDD?
Any other system from Microsoft what pass TDD pattern is similar. For example look to brand new Visual Studio 2019. Even in simplest moment is not working correctly. For example, look at the screen below, both of my project is uploaded to local GIT, as you can see, but lock not showing and I can not opportunity to track changing my code.
Even I want to add whole solution to GIT, VS2019 not propose me add code to local repository! This is simplest pattern to working with GIT and even it working incorrectly in VS2019 !
In fact, brand new TDD design product, like VS2019 has huge amount of bugs. I see 778 in moment I write this post.
It concerns everything what made in TDD design, not only Visual Studio or operation system. Any library in NET Framework pass all Microsoft test and for Microsoft point of view is high quality software. But look to reality. For example, this is Microsoft converter VB<->C# https://converter.telerik.com/, and trying 50% of normal C# or VB code is finished by crash Microsoft converter!
Not only Microsoft software is terrible, even more stable software not working correctly time on time, even when I write this post, Notepad++ crashed (1) and Notepad++ can not create report about crash (2).
What is TDD design at all in reality? Only spend time? Only formal report for boss? Because without TDD in most case projects has more quality and less amount of bugs and created faster than with testing projects and formal reports.
This is my common doubt about TDD and testing - reality disproves positive result of TDD, testing spend more time than time to software to be testing, TDD no more than alternatives for (1) interacting debugging technique (including remote debugging in real environment) and (2) self-testing application (when application show needed data step-by-step by development. And formal dedicated test project not need all if you working without boss who like a lot of various reports and without huge CI system with mandatory test projects.
But... what is interesting... In some case testing projects has huge benefits and very useful!!!
I upload this project to the public: VB.NET ASP.NET Core 3.1 xUnit Oauth2 test (Project Template for VS2019) - Download from: [MyServer], [Github], [VisualStudio Marketplace]
I show screen of this project in this topic - How Linux Net Core 3.1 daemon (in VB.NET) can read/write data from/to ancient MS SQL 2005
This project I also upload to the public: VB.NET ASP.NET Core 3.1 nUnit Middleware test (Project Template for VS2019) - Download from: [MyServer], [Github], [VisualStudio Marketplace] and some screen you can see in this page How Linux Net Core 3.1 daemon (in VB.NET) can read/write data from/to ancient MS SQL 2005.
... I'm sorry, no time ... to be continue soon ...
|<SITEMAP> <MVC> <ASP> <NET> <DATA> <KIOSK> <FLEX> <SQL> <NOTES> <LINUX> <MONO> <FREEWARE> <DOCS> <ENG> <MAIL ME> <ABOUT ME> < THANKS ME>|