TDD and Version Control
I am currently learning about TDD and trying to put it into practice in my personal projects. I have also used version control extensively on many of these projects. I am interested in the interplay of these two tools in a typical work flow, especially when it comes to the maxim to keep commits small. Here are some examples that come to mind:
Should we mock entities and value objects when doing DDD?
After reading a few articles about Newable vs Injectable objects and how these concepts relate to DDD’s services, entities and value objects, I was left with some doubts about using newables in my code especially in my unit tests.
TDD / one test representing the whole scenario ? or should I split it? [duplicate]
This question already has answers here: How granular should TDD tests be? (5 answers) Closed 11 years ago. While practicing TDD, I came across this specification: A user should be created with its password hashed, be persisted and an activation token should be returned. Should my first unit test, (aiming to begin to test this […]
TDD / one test representing the whole scenario ? or should I split it? [duplicate]
This question already has answers here: How granular should TDD tests be? (5 answers) Closed 11 years ago. While practicing TDD, I came across this specification: A user should be created with its password hashed, be persisted and an activation token should be returned. Should my first unit test, (aiming to begin to test this […]
The Relative Cost Efficiency of (Acceptance) Test Driven Development
I would like to know what the overall impact of resource planning on a software project is, where the requirements and design of the project are driven by automated acceptance tests and unit tests, in contrast to a more “traditional” approach to software development.
The Relative Cost Efficiency of (Acceptance) Test Driven Development
I would like to know what the overall impact of resource planning on a software project is, where the requirements and design of the project are driven by automated acceptance tests and unit tests, in contrast to a more “traditional” approach to software development.
The Relative Cost Efficiency of (Acceptance) Test Driven Development
I would like to know what the overall impact of resource planning on a software project is, where the requirements and design of the project are driven by automated acceptance tests and unit tests, in contrast to a more “traditional” approach to software development.
Who should be responsible to write test cases? [duplicate]
This question already has answers here: test driven development – Who should write the tests? (6 answers) Closed 11 years ago. Should tests in some project be written by the actual person that does the coding (usually senior in our team) or it can be done by junior coders with less experience? testing tdd 12 […]
Writing Tests for Existing Code
Suppose one had a relatively large program (say 900k SLOC in C#), all commented/documented thoroughly, well organized and working well. The entire code base was written by a single senior developer who no longer with the company. All the code is testable as is and IoC is used throughout–except for some strange reason they did not write any unit tests. Now, your company wants to branch the code and wants unit tests added to detect when changes break the core functionality.
Writing Tests for Existing Code
Suppose one had a relatively large program (say 900k SLOC in C#), all commented/documented thoroughly, well organized and working well. The entire code base was written by a single senior developer who no longer with the company. All the code is testable as is and IoC is used throughout–except for some strange reason they did not write any unit tests. Now, your company wants to branch the code and wants unit tests added to detect when changes break the core functionality.