| 1 |
<?php |
| 2 |
|
| 3 |
/* |
| 4 |
|-------------------------------------------------------------------------- |
| 5 |
| Test Case |
| 6 |
|-------------------------------------------------------------------------- |
| 7 |
| |
| 8 |
| The closure you provide to your test functions is always bound to a specific PHPUnit test |
| 9 |
| case class. By default, that class is "PHPUnit\Framework\TestCase". Of course, you may |
| 10 |
| need to change it using the "uses()" function to bind a different classes or traits. |
| 11 |
| |
| 12 |
*/ |
| 13 |
|
| 14 |
// uses(Tests\TestCase::class)->in('Feature'); |
| 15 |
|
| 16 |
/* |
| 17 |
|-------------------------------------------------------------------------- |
| 18 |
| Expectations |
| 19 |
|-------------------------------------------------------------------------- |
| 20 |
| |
| 21 |
| When you're writing tests, you often need to check that values meet certain conditions. The |
| 22 |
| "expect()" function gives you access to a set of "expectations" methods that you can use |
| 23 |
| to assert different things. Of course, you may extend the Expectation API at any time. |
| 24 |
| |
| 25 |
*/ |
| 26 |
|
| 27 |
expect()->extend('toBeOne', function () { |
| 28 |
return $this->toBe(1); |
| 29 |
}); |
| 30 |
|
| 31 |
/* |
| 32 |
|-------------------------------------------------------------------------- |
| 33 |
| Functions |
| 34 |
|-------------------------------------------------------------------------- |
| 35 |
| |
| 36 |
| While Pest is very powerful out-of-the-box, you may have some testing code specific to your |
| 37 |
| project that you don't want to repeat in every file. Here you can also expose helpers as |
| 38 |
| global functions to help you to reduce the number of lines of code in your test files. |
| 39 |
| |
| 40 |
*/ |
| 41 |
|
| 42 |
function something() |
| 43 |
{ |
| 44 |
// .. |
| 45 |
} |
| 46 |
|
