Search Images Videos Maps News Shopping Gmail More »
Web History | Settings | Sign in

About 4,240,000 results
  1. c# - Unit testing with Mocks. Test behaviour not implementation ...

    21 Dec 2010 ... share [g+] share [fb] share [tw]. I always had a problem when unit testing classes
    that calls other classes, for example I have a class that creates ...
    stackoverflow.com/.../unit-testing-with-mocks-test-behaviour-not- implementation - Cached - Similar
  2. unit testing - Should one test internal implementation, or only test ...

    13 May 2009 ... Testing internal implementation is unit-testing, which is another part of ..... The
    more each behavior is tested, the easier it is to recognize not ...
    stackoverflow.com/.../should-one-test-internal-implementation-or-only-test- public-behaviour - Cached - Similar
  3. Unit Test the Behavior, Not the Implementation | Karl Seguin

    25 Mar 2010 ... 7 Responses to Unit Test the Behavior, Not the Implementation. Serhiy Kalinets
    says: April 3, 2010 at 2:21 pm. I am not sure that you're testing ...
    codebetter.com/.../unit-test-the-behavior-not-the-implementation/ - Cached - Similar
  4. Unit testing - Wikipedia, the free encyclopedia

    In this case the unit test, having been written first, acts as a design document
    specifying the form and behaviour of a desired solution, but not the
    implementation ...
    en.wikipedia.org/wiki/Unit_testing - Cached - Similar
  5. Test-driven development - Wikipedia, the free encyclopedia

    In test-driven development a developer creates automated unit tests that define ...
    Passing the tests confirms correct behavior as developers evolve and ... (If it does
    not fail, then either the proposed “new” feature already exists or the test is
    defective.) ... Once this is shown, the underlying functionality can be implemented
    .
    en.wikipedia.org/wiki/Test-driven_development - Cached - Similar
  6. Test Behavior, Not Implementation - P is for Programming

    Test Behavior, Not Implementation. January 25, 2012. While I was reading the
    Ruby Pickaxe book I came across an example of Unit Testing which – in my ...
    www.jacopretorius.net/2012/.../test-behavior-not-implementation.html - Cached - Similar
  7. The evil unit test. | Making Good Software

    27 Jan 2012 ... Unit tests can be evil, I know that sounds harsh, but I think there is a ... Testing the
    implementation and not the behaviour is a waste of time and ...
    www.makinggoodsoftware.com/2012/01/27/the-evil-unit-test/ - Cached - Similar
  8. Jay Fields' Thoughts: Rails: Unit Testing ActiveRecord Validations

    27 Dec 2006 ... There are at least 2 easy ways to unit test the validations of an .... -The 'test
    behaviour not implementation' mantra was born in languages ...
    blog.jayfields.com/2006/12/rails-unit-testing-activerecord.html - Cached - Similar
  9. TDD for unbelievers | Agile Zone

    25 Jun 2011 ... Test behavior, not implementation. Another common belief about unit tests is they
    should test class methods and state transitions, i.e., current ...
    agile.dzone.com/news/tdd-unbelievers - Cached - Similar
  10. TDD Tests are not Unit Tests | Stephen Walther

    11 Apr 2009 ... On the surface, TDD tests are very similar to unit tests. This is not ... If the Add()
    method is not implemented correctly then the unit tests fails (see Figure 1). Figure
    1 – Failing ..... You stub the behaviour of the other unit. Make the ...
    stephenwalther.com/blog/archive/.../tdd-tests-are-not-unit-tests.aspx - Cached - Similar