I'm in the process of writing a personal 'pet-project' with some
basic CRM functionality
I intend to use it in the future to demonstrate 'proofs - of
concept' for a number of things like programming practices and
general extensions that could be used on our 'works' CRM.
Obviously it won't include any 'real' business logic from my day
job, but I will probably implement some common business rules.
I've got it to a state that some of the basic requirements are
met, but now I can see that I need to implement testing.
Yes I know I'm late in introducing the testing, but testing is
something I've tried before and I'm finding it hard to do TDD.
Why testing now then ? Well .. did I mention I want to reproduce
'similar' behaviour in WPF and in ASP.net MVC ?
What I've been doing so far is writing some functionality in WPF, then, when it 'works'... implement the
same in MVC.
But now I'm adding 'more', the manual testing is getting ...
tedious... unreliable... time-consuming.
So the tests I'm talking about are really User Acceptance tests rather than Unit Tests
What I'm intending to do is
- write specs using SpecFlow, this will 'drive' the tests
- implement the 'step-definitions' using
-
- Selenium
for targetting the MVC implementation in
-
- White
for targetting the WPF implementation
To be honest I've already started on the Selenium part, I'm using page objects and
it looks really promising.
I'll post code and more info on another day, this was just to
get down some of my intentions.
Facebook
Linkedin