Binary was using realpath, and targets were sanitized without taking the full path's drive name in account, so this was fixed.

I intend to wait for CI to make sure the test suite still works as expected.

I hope it'll fix #36 🤔

In an effort to improve Pest and its documentation, we would like to collect your experience trying Pest for the first time. Remember, there is no wrong answer 🙂

• What problems did you encounter?

• How did you solve them?

• How familiar are you with PHPUnit & testing in general?

To get the ball rolling, I'll share my first roadblock:

• While converting the TALL preset test suite to Pest, I encountered this TestCaseAlreadyInUse exception:

• I figured I was calling my User class from Pest.php, and moved it back into my test file:

use Illuminate\Foundation\Testing\RefreshDatabase;
use Tests\TestCase;
use App\User;

uses(
    RefreshDatabase::class,
    TestCase::class,
    User::class,
)->in('Feature');

• Beginner level: I've just began learning testing in the last 2 years, but it seemed too complicated to integrate on our old projects. I am now starting my first real TDD project with Pest 👌

Your turn now! What troubles did you experience using Pest?

At long term, I wanna pest to run on its own. Would be cool an page on the website ( like https://vuejs.org/v2/guide/team.html or better ) where people understand the different concerns of the project and the people involved on those concerns.

Curious, what are your thoughts about implementing the standard describe blocks?

Ala?

https://jestjs.io/docs/en/api#describename-fn

Example

describe('my block', function() {
  test('is delicious', function() {
    assertTrue(true);
  });
});

Hi,

I've come across the following bug.

When using a capitalized acronym inside the test's description (e.g. API), when running the test it will be printed lowercase and a space will be added between each characters.

Code sample

it('requires an API key', function () {
    assertTrue(true);
});

This gets printed as:

PASS  Tests\Unit\TranslatorTest
✓ it requires an  a p i key

Tests:  1 passed
Time:   0.03s

Expected result The description should probably be printed as is. If this is not possible, capitalized acronyms at least should be preserved.

Steps to reproduce

1. Create a new dummy test
2. Use a capitalized acronym inside the description (e.g. API)
3. Run the test
4. See that the printed description now shows the acronym as a p i instead of API

Have a nice day.

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Fixed tickets | #143

Summary of the API:

A quick summary of this RFC's API.

extends can be used to extend a method or methods. For extending a method supply the method name and the new value. You can also supply an array of method/value sets for overriding multiple methods or chain extends call.

uses(MyTestCase::class)
    ->extends(
        'createBill',
        fn(string $name) => $this->billService->create($name)
    )
    ->extends([
        'containerProvides' => ['BillService', 'UserService', 'LoginService'],
        'initializeContainer' => function() {
            $container = parent::initializeContainer();
            $container->add(GoogleStorage::class, Mockery::spy(GoogleStorage::class));
        },
    ]);

For calling the parent instance method, simply use self::parent(). Calling static parent methods is currently not supported due to limitations within PHP itself.

with can be used to override a property. For overriding a property, we can use the with method. It works the same way as extends except that it does not support closures, as statements in properties are forbidden.

uses(MyTestCase::class)
    ->with('appName', 'MyAwesomePestApp')
    ->with([
        'useDatabase' => true,
        'databaseMode' => DatabaseMode::TRANSACTION,
    ]);

Fixes #143

| Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | Fixed tickets | #307

This PR introduces a more specific separator for the tests keys to avoid matching a potential folder name. The separator is changed from @ to @@@@ as it has more chance to not match anything in the test file absolute path. Maybe this value could be more complex?

When we are writing tests, we often need to check that values meet certain conditions. And for that, at the time of this writing, we are using PHPUnit syntax using the global helpers: assertEquals, assertTrue, assertFalse, etc.

The problem with this is the number of global helpers that are injected in the global namespace: One function per assertion.

This Pull Request bootstraps the global helper expect, that would offer the same number of assertions of PHPUnit, but using a single global function and a fluent syntax like so:

// old
assertTrue($variable);
// new
expect($variable)->toBe(true);

Fell free to help, and to add methods. All methods should be inspired by: jestjs.io/docs/en/expect.

The IDE completion in PHPStorm can be better on closure based tests.

Problem: The $this variable inside closures don't get autocompletion on PHPStorm by default.

it('foo', function () {
    $this->ass // <-- here.
});

Workaround: Add a type hint just before the $this variable.

it('foo', function () {
    /* @var TestCase $this */
    $this->assertFoo // <-- here.
});

Solution: Develop a phpstorm-plugin that can hint phpstorm about this.

The plugin is now getting a stable release and I think it is time for us to actually add it to the website for user's to easily find it.

JetBrains has support for two different iframes which might be useful in docs

<iframe frameborder="none" width="230px" height="110px" src="https://plugins.jetbrains.com/embeddable/card/14636"></iframe>

<iframe frameborder="none" width="245px" height="48px" src="https://plugins.jetbrains.com/embeddable/install/14636"

ofc. we don't have to use them 👍

| Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | Fixed tickets | #140

This pull request adds team city output support to pest.

A future pr could be added, so the exception stack trace uses collision format.

The issue

As I was trying to setup my environnement, I ended up creating an error in the tearDownAfterClass and the last test from the file/class ended up being displayed twice in the CLI: Once that is has succeeded and a second time that is has failed, but it didn't actually run the test a second it.

   FAIL  Tests\Feature\ExampleTest
  ✓ it can say Hello to the World
  ⨯ it can say Hello to the World

  Exception in P\Tests\Feature\ExampleTest::tearDownAfterClass
  Call to undefined method P\Tests\Feature\ExampleTest::randomError()

  Tests:  1 failed, 1 passed, -1 pending
  Time:   0.11s

I have tried this on a fresh project, and the test doesn't run any code:

expect(true)->toBeTrue();

Note: Make sure to notice at the end of the CLI output, it says "1 failed, 1 passed, -1 pending" so this could be a lead.

Note 2 : I noticed as I was writing this issue that the documentation says to call afterAll(), so maybe I shouldn't even call ::tearDownAfterClass() in the first place ?

How to reproduce:

1. Add the tearDownAfterClass static function in your TestCase. Make sure you generate an error inside of that method :

<?php

namespace Tests;

use Illuminate\Foundation\Testing\TestCase as BaseTestCase;

abstract class TestCase extends BaseTestCase
{
    use CreatesApplication;


    public static function tearDownAfterClass(): void
    {
        static::randomError();
        
        parent::tearDownAfterClass();
    }
}

2. Call your test and check the console output.

In the documentation about the underlying test case, it's mentioned how we can change the default test class from PHPUnit\Framework\TestCase to any other that we may want.

Is there a way, to change the test class after the bootstrap.php file is loaded, besides defining the uses() in every test file?

I have a situation where the test class only becomes available after bootstrap.php file has been processed (I blame WordPress). So I cannot use that class in the Pest.php file (I get an error about it not existing).

The only workaround is adding the uses() function on the top of every test that depends on it, which is kinda tedious, and makes code like

uses(TestCase::class)->in('Integration');
uses(OtherTestCase::class)->in('Unit');

impossible to use.

Is there some sort of 'middleware' that I could use to set the base test class in one place, but after the bootstrapping process?

I'm using Pest v1.22.3.

Hi there 👋

First, love Pest. Thanks for your great work!

I'my trying to detect duplicated queries using https://github.com/beyondcode/laravel-query-detector So I created a beforeEach and afterEach method which check it for each test.

// Pest.php

use BeyondCode\QueryDetector\Events\QueryDetected;
use Illuminate\Foundation\Testing\LazilyRefreshDatabase;
use Illuminate\Foundation\Testing\RefreshDatabaseState;
use Illuminate\Foundation\Testing\TestCase;
use Illuminate\Support\Facades\Event;
use Tests\CreatesApplication;
$beforeEach = function (): void {
    Event::fake([
        QueryDetected::class,
    ]);
};

$afterEach = function (): void {
    $duplicatedQueries = Event::dispatched(QueryDetected::class);
    if ($duplicatedQueries->isNotEmpty()) {
        // ray so we can debug n+1 queries
        ray($duplicatedQueries->all());

        // allow DB refresh on next test becase throwing here will stop pest DB refresh process
        RefreshDatabaseState::$lazilyRefreshed = false;
    }

    Event::assertNotDispatched(QueryDetected::class);
};

uses(TestCase::class, CreatesApplication::class, LazilyRefreshDatabase::class)
    ->beforeEach($beforeEach)
    ->afterEach($afterEach)
    ->in('Feature', 'Unit')
;

It works great!

But after a few hundred tests, it gets stuck. I suspect that asserting/throwing Event::assertNotDispatched(QueryDetected::class); in an afterEach test stops the tearDown / cleaning process after each test and that lead to oom?

If I remove Event::assertNotDispatched(QueryDetected::class); everything runs as usual

Is there a way to assert in afterEach ?

Thanks :)

Given the following test:

it('has emails', function ($email) {
    expect($email)->not->toBeEmpty();
})->with(function() {
    yield 'james' => '[email protected]';
    yield 'taylor' => '[email protected]';
});

I would expect the test description to be it has emails with data set "james".

Instead, the test description is it has emails with ([email protected])

Would it be possible to support description keys for lazy datasets?

| Q | A | ------------- | --- | Bug fix? | no | New feature? | no | Fixed tickets | #...

Because it() sets a description, it will always return TestCall. This also adds a conditional PHPStan return type for test() as we can work out what it returns based on this. 👍🏻

Original PR for 1.x: https://github.com/pestphp/pest/pull/599