TDD stands for Test-Driven Development, or Test-Driven Design. It is the practice of writing a unit test before writing code to satisfy it, in what is known as the Red-Green-Refactor cycle.
3
votes
1answer
98 views
How to deal with the notion of time in UI/Integration tests
There are some well-known techniques for dealing with the notion of time in unit tests. These allow you to write unittests that always work with a specific time so the outcome of the test is ...
-1
votes
0answers
23 views
Doing e2e testing with native applications [closed]
I come from a web background and one of my projects in school requires me to build a native windows application. I am not very familiar with writing GUI applications in MSVS and was looking for a tool ...
0
votes
0answers
53 views
Test Driven Development vs Behavior Driven Development [duplicate]
I am a developer for 3 years and preparing to dive in TDD but then I heard about BDD and the world is talking about it. I don't know which is suitable for which time? Is BDD only applicable for ...
14
votes
7answers
715 views
When should I write integration tests?
According to rules of TDD unit tests are written before production code, but what about Integration tests that exercises interaction between concrete (non mocks) wired objects?
Should they be written ...
2
votes
1answer
119 views
Can you apply agile/TDD in all circumstances?
I'm not against agile/TDD and use it under most circumstances. However, in some circumstances I feel it doesn't work well.
For example, the other day I was building a fairly complex data processing ...
3
votes
3answers
374 views
How do you unit test a User Interface? [closed]
I use JavaScript with JQuery for a Rails application. I have some dynamic behaviour in this one. As a Ruby developper, I like TDD/BDD, specialy with RSpec. For the moment, I test my JavaScript ...
29
votes
7answers
1k views
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 ...
0
votes
1answer
217 views
Designing new application from scratch, TDD, MVC, OOD based [duplicate]
I'm about to improve my skills in all that is related to designing applications from scratch using proper OOD principles, involving MVC pattern and using TDD approach to do it.
I have a project for ...
5
votes
3answers
279 views
Who should be responsible to write test cases? [duplicate]
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?
8
votes
5answers
391 views
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 ...
2
votes
4answers
499 views
How to practice ATDD if design is not yet emerged from TDD?
Despite being very stakeholders friendly, ATDD aimed to provide a "stop" line when a feature has just been done. This avoids wasting time to add non-focused (and sometimes useless) code.
That's why ...
1
vote
1answer
181 views
TDD / one test representing the whole scenario ? or should I split it? [duplicate]
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 ...
1
vote
1answer
249 views
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 ...
0
votes
1answer
140 views
Is it worth writing a unit test for a DTO with the most basic getter/setters? [duplicate]
The advantage is it protects your DTO against future "enhancements" ?
2
votes
0answers
172 views
How do I test this?
I've attempted test first in Ruby on Rails using Test Unit and RSpec.
I'm wondering how to do test first in situations that are more closely tied to the OS/filesystem.
Problem: Building a USB stick ...
