|
|
 |
| Rhino Mocks |
 |
-
AssertWasCalled and Methods Called Multiple Times
AssertWasCalled allows you to check if the object's method was called during the test.
Until now, in our tests, we were testing single calls to such methods;
such checks will fail, however, if the method is called multiple times during the test (with the same parameter values).
You can define additional parameters in AssertWasCalled calls that handle this situation.
-
AssertWas[Not]Called and Object Properties
AssertWasCalled and AssertWasNotCalled allow you to check if the object's method was called during the test (or not).
Checking access to object properties depends on their declaration: whether they're ReadOnly, WriteOnly, or read/write.
-
Rhino Mocks's AssertWasNotCalled
AssertWasCalled allows you to check if the given method was called during the test.
AssertWasNotCalled, on the other hand, allows you to check that a method was not called during the test.
-
Rhino Mocks's AssertWasCalled in VB.NET
Using a big new library in any project can be quite daunting.
But, IMO, the best way to learn one is to just start using it.
And then, after a while, the more advanced functions will become apparent. But where to start?
In this text you'll find a gentle introduction to Rhino Mocks
that shows the simplest scenario where the library can be used -
creating object stubs to facilitate testing.
-
First steps with Rhino Mocks (in VB.NET)
Using a big new library in any project can be quite daunting.
But, IMO, the best way to learn one is to just start using it.
And then, after a while, the more advanced functions will become apparent. But where to start?
In this text you'll find a gentle introduction to Rhino Mocks
that shows the simplest scenario where the library can be used -
creating object stubs to facilitate testing.
Top
|
|
|
|
Texts
