开云体育

It is, though you could easily replace that with any cache implementation. Most web server caches are global/static by design, though. The main point is the separation of concerns and use of

Hi Steve. Thanks for the links. I had a look at the blog and unless I am mistaken it is still just using a static cache internally - HttpRuntime.Cache. Am I missing something?

I used this approach at a company-that-shall-not-be-named, years ago. I started with 2 unit tests for my group's part of the system. A week later I was up to 10, and my co-workers started seeing that

Wow. I knew a programmer who was dinged by her manager because she wasn't creating enough bugs. They expected a certain number of bugs per some number of lines of code to be found in code-review and

I would avoid the statics, replace the references to the repositories with interfaces, and also split the responsibility to cache or access data into two pieces, so that each can be tested (and

Hello Harvis I have quite a few articles on my blog and website about applying TDD to embedded systems software development. There's my book too :-) More specifically, I have a series of three

Hi David, I assume you meant me and the discussion in the other thread. To me the biggest negative side-effect is the difficulty in testing. I believe this is a real issue. It is not just that there

I just want to add that you might need to convince your coworkers to keep unit tests passing. If they are further convinced of the usefulness of writing tests, then you can show them up how helpful

Thanks Russ. That is exactly the way I am going to start. Amazingly I even met some resistance to that approach - "it will be inconsistent with the rest of the application", "someone new coming

David, I'm interested to read this discussion, but what I'm missing is an explanation of what kinds of problems are being caused by the current architecture. Presumably the remainder of the team

How much code control does the organization exert? Do you have regular code reviews? My experience is that the best way is to start small. Make one class testable at a time without touching the

As far as code smells go, some people just seem to have blocked noses! Anyway, thanks everyone for your answers. I'm glad to see that I am on the right track - now I just have to convince everyone

Or there might not be any convincing enough smells, yet! If not, bide your time, watch for smells as the code scales, and when convincing smells appear, then make the case for refactoring it

David Burstin wrote: This is a "pattern" from the book "working with legacy code" - it's good because it's (relatively) non-invasive and allows you to put your legacy code under test for further

Not having seen the code my gut tells me that this is probably what I would do. Just create a wrapper API that lets you use the cache in a more OO way and then write a concrete implementation that

http://pragprog.com/book/jgade/test-driven-development-for-embedded-c http://pragprog.com/book/lotdd/modern-c-programming-with-test-driven-development

Hi folks, I've got a question around design for a legacy project that I am working on in c#. This project uses some repository classes that internally act as caches, retrieving data from internal

在 Tue, 04 Jun 2013 00:10:26 +0800，Esko Luontola <esko.luontola@...> 写道: Any good example of TDD used in embedded system developing especially with RTOS. I'm a new guy with TDD, now what

Kathy Van Stone wrote on 3.6.2013 18:55: Here is my recommendation for people wanting to learn it: https://github.com/orfjackal/tdd-tetris-tutorial -- Esko Luontola www.orfjackal.net

I gave a lightning talk on Test Driven Development. Obviously I could not go into details, but I was wondering if there is a (current) good link to send people for more information? I've been a bit