Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • +1 for not your only source of tests - although I was really tempted to downvote for referring to old-fashioned Ant :) Commented May 16, 2012 at 15:18
  • @gnat: The PHP template for jenkins still relies on Apache Ant jenkins-php.org for build automation Commented May 16, 2012 at 15:27
  • But that still doesn't explain, with TDD, how I create the test that requires writing the code for the property. Commented May 16, 2012 at 15:31
  • @Chad: You don't need to have a 100% code coverage to have valid TDD, if your core logic is tested and your interface behave as expected you have a pretty good chance that these properties are covered. If you still really want to test thoses, you could test that the output contains the description value. (still using web development as example) To achieve that you could mock the request that will return a predictable content and then check for specific parts by traversing the sections you want to test (do the content of div#user .description = expected value) Commented May 16, 2012 at 15:40
  • 1
    @gnat, that makes no sense. That's not TDD at all. Commented May 17, 2012 at 16:07