2,679 reputation
1113
bio website
location
age
visits member for 2 years
seen Jan 17 at 11:02

Nov
12
awarded  Yearling
May
1
awarded  Good Answer
Jan
28
awarded  Enlightened
Jan
17
awarded  Custodian
Jan
17
reviewed Approve suggested edit on What should I ask a prospective client during initial meeting?
Jan
13
awarded  Nice Answer
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
Oh I agree that integration tests CAN exercise bad data and how faults are handled, my point was that in my experience, that isn't what integration tests do - YMMV though - I'd also say that hitting every exceptional combination in an integration test is very, very hard - I like integration tests, but less tests testing huge swathes of code (and I say testing loosely) would not give me the same confidence of detailed unit tests though I do think they are important to have (just not as a replacement).
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
Indeed, especially as "polish it later" never seems to actually happen - every review I do where a developer pushes the "it needs to go out, we'll do it later" when we all know, that's not going to happen - technical debt = bankrupt developers in my opinion.
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
And from experience, it's rarely bugs in the happy path that are the problem!
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
Code coverage != tested - aside from bugs cancelling each other out, what about scenarios you've never thought about? Integration testing is fine for happy path testing but I rarely see adequate integration testing when things aren't going well.
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
Depends on what you're testing - are you testing business features (acceptance tests)? Are you testing integration (integration tests)? Are you testing what happens when you click a button (behaviour tests)? Are you testing algorithms (unit tests)?
Jan
13
comment Is it sufficient to use acceptance and integration tests instead of unit test?
I personally think acceptance tests are the most important, behaviour tests are important when testing things like communication, reliability and error cases and unit tests are important when testing small complex features (algorithms would be a good example of this)
Jan
13
answered Is it sufficient to use acceptance and integration tests instead of unit test?
Jan
10
answered Violating SQL principles
Jan
10
comment Cascading “Deleted” records that aren't really deleted
It was a while ago so I'm not 100% sure but I think 4 developers, 3 testers and 1 analyst.
Jan
10
comment Cascading “Deleted” records that aren't really deleted
Duplicating the tables isn't a problem if the audit tables are automatically deployed and kept in sync - same with code, all we had to do was provide an injector at the data layer to switch between the audit tables and the live tables - all queries stayed the same.
Jan
9
answered Cascading “Deleted” records that aren't really deleted
Dec
30
comment what kind of functions and/or classes are impossible to unit test and why
Argh - nothing worse than unit test asserts that have no resemblance to business requirements and are just the output at a given time - mocks that are setup to be called 3 times for example? Why 3? Because it was 3 the first time the test was run /rant :)
Nov
12
awarded  Yearling
Nov
1
answered what would be the best data structure for my situation