How do I know when to use test-based testing or false testing?

Question

What are the scenarios, areas of the application / system, etc. best suited for "classic" state-based testing and mock objects?

Answer 1

You must use mocks for dependencies. I do not think it is either; Usually, you create mocks for dependencies, set expectations on them (regardless of whether they are calls or states), and then start the device under test. Then you check his condition and check the expectations for bullying after that.

Answer 2

I'm going to tackle this in terms of TDD / BDD, where tests run designs.

, , , , . Mocks Are not Stubs , .

, mockobjects Mock Roles, not Objects. book.

, , "" (, / ), . xUnit Test Patterns .

, / . , , , . MVC, , , , , , (, /), / . , - , / . , , mockobjects , .

, , , , 90% IoC/mocking/DIP - (ICustomerRepository/CustomerRepository), .

Answer 3

mock- , .

Answer 4

, , , , , . .

-, , , , ..

, , -, Model/View/Controller-or-Presenter, Presenter First (Google it), . , /.

Answer 5

. Mockist vs Classic TDDers.
.. , , . Mocks ; , , IO ( , DB, ), .., .

Answer 6

TDD'er, , . , , . - , , .

, . , , , .

- , "" unit test , "" unit test. , / , mocks-stub, .

- . " ?", .