228 reputation
16
bio website
location
age
visits member for 2 years, 8 months
seen Jul 8 at 19:02

Apr
27
awarded  Yearling
Jan
14
awarded  Nice Answer
Feb
29
answered Do we need “obvious” Method Documentation information?
Feb
28
comment Is there a problem with writing an in-memory DAL for testing the BLL/ViewModels?
I was thinking about that, and I think it has to do with the complexity and purpose of the test code. If that piece of code is very simple, and the only purpose of that piece of code is to "pretend" to be the another piece of code for testing, and it's only sensible to use that piece of code for that testing purpose, then I'd say it is unit testing. If it becomes complicated enough that it a) would be useful as a DAL outside of the testing context, or b) would need its own suite of tests, it's integration testing using a complex BLL and a complex DAL. I admit that that is a very broad line.
Feb
28
comment Is there a problem with writing an in-memory DAL for testing the BLL/ViewModels?
I've read around the net about people who use NHibernate using SQLite for "unit" testing, even on stackoverflow. +1 for pointing out that it's really integration testing.
Feb
27
awarded  Scholar
Feb
27
accepted In integration testing, do you use the data access objects for setup and validation or a different data access method?
Feb
27
comment In integration testing, do you use the data access objects for setup and validation or a different data access method?
Thanks for responding again, @TMN, and for being patient with the misunderstanding. I hadn't thought of the round-trip issue. The only downside I can think of to using the ORM for setup and validation would be that some ORM mapping mistakes might be hidden, but separately testing the ORM DAO should cover that. Between the round-trip issue and the ease of use with the ORM, I think that's the answer, certainly for scenarios where legacy data isn't involved. That round-trip issue is enough answer the question. Thanks!
Feb
27
comment In integration testing, do you use the data access objects for setup and validation or a different data access method?
Thanks for your answer, @TMN. Please see my edit to the question and let me know if it's more clear.
Feb
27
revised In integration testing, do you use the data access objects for setup and validation or a different data access method?
Clarified question (I hope!)
Feb
27
comment Business Objects within a Data Access Layer
+1 for proper separation of concerns.
Feb
27
comment Business Objects within a Data Access Layer
You can also look at NHibernate if you want to look into another option.
Feb
27
awarded  Editor
Feb
27
revised In integration testing, do you use the data access objects for setup and validation or a different data access method?
Clarified question
Feb
27
comment In integration testing, do you use the data access objects for setup and validation or a different data access method?
A test of a business logic function that fakes the entire data layer would be a unit test, not an integration test. When you say to "includ[e] it in an integration test," can you clarify what you mean? My question presupposes that I'm writing an integration test.
Feb
24
awarded  Supporter
Feb
24
comment How does bit flipping / complementing work?
1010 means -8 + 2 = 6. You can think of the first bit being "1" as "give me the largest negative number possible", which is -8 for four bits, and then the remaining bits are what you add to it, 2 in this case.
Feb
24
awarded  Teacher
Feb
24
answered How does bit flipping / complementing work?
Feb
22
awarded  Student