Reputation
439
Next privilege 500 Rep.
Access review queues
Badges
2 7
Newest
 Nice Answer
Impact
~16k people reached

  • 0 posts edited
  • 0 helpful flags
  • 183 votes cast
Jan
27
comment What's the point of running unit tests on a CI server?
Running it on a different configuration is also important if the developer hard-coded something that should be configuration-driven. One of our developers committed a suite of unit tests that all referenced a CSV file on his desktop.
Jan
27
comment What's the point of running unit tests on a CI server?
We have CI on our development, staging (pre-prod) and production (master) builds, with unit test execution. If someone breaks the build, this needs to happen long before the code is promoted to master.
Nov
27
awarded  Nice Answer
Oct
4
awarded  Yearling
Oct
3
awarded  Nice Answer
Oct
9
comment Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I think what he's saying is, you don't necessarily have to reproduce the issue in order to investigate a fix for it. And assuming you track it down and find a fix, you'll then know the conditions to set up on the test server to reproduce. At that point you'd even know how to set up the previous code - set it up, verify that it's reproducible, deploy the fix, verify that it's fixed.
Jul
2
comment C# Minimal SQL Database
I don't remember if SQL CE has a separate runtime or not. SQLite doesn't, but it can be a little tricky to set up with a .NET project.
Apr
26
comment Hardware running gpl code
How did you determine that it is running Linux?
Apr
4
comment where to use web services
Q: "Should I use web services?" A: "Only if you want to use your data somewhere besides the system where it's produced."
Mar
29
comment Is it OK to have multiple asserts in a single unit test?
I've seen cases where multiple asserts were used instead of RowTest (MbUnit) / TestCase (NUnit) to test a variety of edge-case behaviors. Use the proper tools for the job! (Unfortunately, MSTest doesn't seem to have a row-test capability yet.)
Mar
27
comment Should Repositories return IQueryable?
If you're just going to use an IQueryable, then why would you even use a repository? Repositories are intended to hide implementation details. (Also, WCF Data Services is quite a bit newer than most of the solutions I've worked on in the past 4 years that used a repository like this... So it's not likely that they'll be updated anytime soon just to make use of a shiny new toy.)
Mar
27
revised Should Repositories return IQueryable?
added 199 characters in body
Mar
27
comment Should Repositories return IQueryable?
@MikeBrown The point of this question - and my answer - is that you want to expose the behavior or the advantages of IQueryable without exposing the IQueryable itself. How are you going to do that, with the built-in API?
Mar
26
revised Should Repositories return IQueryable?
added 852 characters in body
Mar
26
comment Should Repositories return IQueryable?
If I didn't want to expose the built-in query API, yes.
Mar
26
answered Should Repositories return IQueryable?
Mar
26
comment Is the average number of bugs per loc the same for different programming languages?
I think your edit (Update:) is the core of the problem. Or, as Mark Twain said, there's three kinds of lies: Lies, Damn Lies, and Statistics.
Mar
20
comment What should a test method test?
Also, keep in mind that putting multiple, dissimilar tests in one method (first approach) will not fully exercise your classes - as soon as one of them fails, the rest of the assertions in that test method do not even run.
Mar
13
comment How do I handle having so many SQL queries?
@LieRyan As long as you're operating on the IQueryable, this is possible in LINQ as well.
Mar
12
awarded  Yearling