Skip to content

Commit b5911e3

Browse files
committed
[ci skip-release] README improvements
1 parent 3ff4b89 commit b5911e3

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -346,9 +346,9 @@ when(myMock.foo("bar", 42)) thenAnswer ((v1: String, v2: Int) => v1 + v2)
346346
```
347347

348348

349-
##Mix and match
349+
## Mix and match
350350

351-
###Mixing normal values with argument matchers
351+
### Mixing normal values with argument matchers
352352

353353
Since mockito 1.0.0, when you use the idiomatic syntax, you are not forced anymore to use argument matchers for all your parameters as soon as you use one,
354354
so stuff like this is now valid (not a comprehensive list, just a bunch of examples)
@@ -380,7 +380,7 @@ I'll write a more detailed explanation at some point, but there are more than on
380380
The workaround is quite easy though, just provide a value (or a matcher) for that argument and you are good to go.
381381

382382

383-
##Numeric matchers
383+
## Numeric matchers
384384

385385
A new set of matchers to deal with number comparison were introduced (see [Scalactic tolerance](#tolerance) for aproximation),
386386
the syntax is slightly different to make them more readable, so now we can write stuff like (notice the 'n')
@@ -394,9 +394,9 @@ aMock.method(n <= 5) was called
394394
```
395395

396396

397-
##Scalactic integration
397+
## Scalactic integration
398398

399-
###Equality
399+
### Equality
400400

401401
Since version 1.0.0 the `eqTo` matcher uses the `org.scalactic.Equality[T]` typeclass, this doesn't change anything on the API
402402
and existent code will not be affected, but it allows you to override the standard equality of any class by just providing an
@@ -410,7 +410,7 @@ aMock.method(eqTo(/*some foo instance/*))
410410
```
411411
412412
413-
###Tolerance
413+
### Tolerance
414414
415415
You can use Scalactic's `Spread[T]` to deal with the precision errors in floating points, so you can now write stuff like
416416
```scala

0 commit comments

Comments
 (0)