开云体育

Hi Kaleb, Regarding "an incomplete but green test is at best misleading and at worst wrong: if a test is green it should be a valid test, and a partial or incomplete test is not valid." ... If I

Hi Kaleb, On Tue, Aug 26, 2014 at 4:48 PM, Kaleb Pederson kaleb.pederson@... [testdrivendevelopment] <testdrivendevelopment@...> wrote: Stop! Go back to where you had the empty

Hi Kaleb, No, but when I get into trouble, I stop, back up and get more precise about how I'm proceeding. There should be no "typical" step size in your practice. Beck stressed the importance of

the pain your coworker was feeling could be down to not refactoring the test itself. Instantiating the class under test multiple times in a test is what I would consider to be duplication In some

No. But I don't follow anything strictly! This varies greatly depending on what I'm working on/how comfortable I am with everything. When working with a new language/framework etc. my steps will

The official rules say to write a test, but only enough of a test to get a failure --- which means "not the whole test." But as to the title question: sometimes you should follow the rules strictly.

Over the last three years I've been doing training on and advocating TDD where I work and a number of people have been striving to learn and use TDD in their daily development :). --- An experience

Hi, Does anyone know of a good unit testing library for testing pdf in .NET? something similar to jPDFUnit? -- *Lior* *Friedman* Agile Consultant - AUT/TDD Expert | Mobile: 972.52.833.3660 |

We've been using Ruby and Cucumber for ATDD/BDD, using PageObject and some other cool Ruby gems with Watir/Selenium drivers. We've found that approach preferable to using Cucumber-JVM or SpecFlow,

I think you'll need: - A good unit-testing library; - A good matcher/fluent-assertions library; and - A good mock library - A good UI-testing framework (whether you plan to test UI) IMHO, I

Definitely JUnit. Also check out Mockito and AssertJ. [testdrivendevelopment] <testdrivendevelopment@...> wrote:

Asim Jalis asimjalis@... [testdrivendevelopment] wrote: Just junit, and perhaps guava libraries to get around some java deficiency. Michal

What are current recommendations for tools in Java?

People have told you about tools, as far as practices go I would recommend Ian Cooper's video TDD Where Did It All Go Wrong, it explains how the original ideas around testing units of behaviour (as in

NUNit (with testcase attributes), FakeItEasy, NCrunch = awesome [testdrivendevelopment] <testdrivendevelopment@...> wrote:

Yes, NUnit is wonderful and Moq. If you’re using Visual Studio the built-in unit test framework is reasonable and well-integrated. And then add – ReSharper. John D. Sent: 22 July 2014 23:00 To:

TDD, or at least the ideas behind it, is a lot older than that. NUnit and SpecFlow are both pretty awesome. There are also a number of good mock tools: NSubstitute, Rhino, Moq, etc. You should play

Hello, I was curious about the current state of TDD. Obviously, it's 10+ years old at this point. I wanted to find out which practices and tools are currently favored for TDD. I'm guessing that these

Hello folks, I created a simple opensource tool for testing user interfaces called FunTester (http://funtester.org), and I would like to hear your thoughts about it. It is a model-based testing

What does close enough mean? Can they be UUIDs and GUIDs and be "close enough"? Or do they need to be *random* and non-repeating? by separating concerns. You have string generation. You have