Re:Pointers to ATDD applied in a Legacy environment
- --- In firstname.lastname@example.org, Jussi Mononen <jussi.mononen@...> wrote:
>From test automation point of view the question is whether the current architecture allows you to write tests through some API instead of GUI. ATDD works best if you can write most of tests agains some API and only write some tests through UI.
> On 08/31/2010 03:44 PM, alexis.hui@... wrote:
> > How legacy is "legacy"? I have successfully done ATDD in three
> > environments that can be considered legacy depending on your definition:
> Hmm, ~2-300 000 LoC without unit tests, mixed platform and UI written in
> C/C++/Java/PHP/Perl ...
However, in many legacy systems UI and domain code is so badly mixed together that you end up writing all your tests through fragile UI. I have seen this path too many times. It usually does not work. The solution is to eventually refactor the architecture in a way it allows you to write more and more tests without UI.