Skip to content

Commit e277fe4

Browse files
committed
install Pest
1 parent bcb4d8b commit e277fe4

File tree

2 files changed

+50
-1
lines changed

2 files changed

+50
-1
lines changed

composer.json

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@
2929
"require-dev": {
3030
"mockery/mockery": "^1.4.3",
3131
"orchestra/testbench": "^6.19|^7.0",
32+
"pestphp/pest": "^1.22",
3233
"phpunit/phpunit": "^9.3.0",
3334
"spatie/test-time": "^1.2.2"
3435
},
@@ -48,7 +49,10 @@
4849

4950
},
5051
"config": {
51-
"sort-packages": true
52+
"sort-packages": true,
53+
"allow-plugins": {
54+
"pestphp/pest-plugin": true
55+
}
5256
},
5357
"extra": {
5458
"laravel": {

tests/Pest.php

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
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+
}

0 commit comments

Comments
 (0)