开云体育

Hi Rakesh, First off I think it's good to clarify what your actual business requirements are - is the REST API *really* part of your business requirements or is this actually an infrastructure thing?

I'm so sorry I got your name wrong. Don't know what I was thinking

Hi Debasish, my strategy is to let the fw call me, and avoid dependencies on the framework in my code. It was fairly successful in a project one year ago. Our entry point was a single servlet, that

hmm, I responded this morning but my reply hasn't shown up yet! Copying my reponse: Hi Matteo, an approach that like that would have consequences for how to use the REST framework. For example, lets

actually, thinking this through, I can see other issues. Lets say use case A returns object Foo for a GET and use case B returns object Bar for a GET. A generic GET method in one super controller

Hi Matteo, an approach that like that would have consequences for how to use the REST framework. For example, lets take Spring MVC. The traditional approach is to create a controller for a specific

rakesh.mailgroups@...> wrote:

Hi, I'm building a new system and I want to get it 'right'. What does right mean? It means I want to test my business rules against just Java classes. This approach has been advocated by Uncle Bob (I

http://www.san-gregorio-de-polanco.com/bmeueps/zzwdi.tjuh?az 3/28/2013 2:13:55 PM 3/28/2013 2:13:55 PM

first introduced to it in Michael Feathers Work. but I'm not sure if it has a special section is his "Working with Legacy system": book or was it in a later video session i saw. A very useful

JeffGrigg wrote: I think thats not such a bad approach. We use it quite a lot: 1. write dirty code of what you "want to do" (aka "spike") 2. observe the result 3. write automatic tests on anything

For a pragmatic answer: Write the code. Run it. Observe the result. Validate that the result is "reasonable." [...whatever the heck THAT means!!!] Put the result in your test as an assertion. Then

Hi Folks. I hope you find this class useful - it is recorded live in my five days TDD master class. focus is on .NET, but Java and C++ devs will find it helpful as well. the cost is about half the

Excellent you're just the man to write it. When you do I promise to shout from the roof tops (ok perhaps just twitter) singing your praises :-) Cheers Mark martinsson.johan@...> wrote: -- Cheers

Ok I'll keep that one in mind for the next TDD course. I do think that that the community lacks a distilled written up kata about just test smells that allows you to learn a lot about them in a

Excellent resource. I can't use it directly as it's with java people but it gives me a good idea for places to look the next time. Apart from the expertise in test analysis in the videos.

martinsson.johan@...> wrote: There are a number of simple examples of how difficulties in the test drive a change in the code in Mauricio Aniche's book.

I have a whole list here http://artofunittesting.com/unit-testing-review-guidelines/ and videos of test smells here http://artofunittesting.com/test-reviews/ martinsson.johan@...> wrote: --

If you google smelly code on this list you will find I asked this question a few months ago and got some good advice. If that doesn't help ping me offline. Cheers Mark martinsson.johan@...>

Hi everyone, I've been asked to teach test smells Thursday (!) and I'm looking for a piece of test code that has a good number of them in order to use it for identifying and then removing the test