What are the steps to reproduce this issue?

1. Open up test file
2. Run a better pest command. Via shortcut or via command palette
3. …

What happens?

Nothing. The integrated terminal gets cleared but there is no feedback

What were you expecting to happen?

Feedback of the tests that should be running

Any logs, error output, etc?

No errors, no logs found

Any other comments?

My terminal is configured to zsh. Running pest manually via the terminal does run.

What versions are you using?

Operating System: Mac OS Ventura
Package Version: v0.1.0

Hey there,

Would you kindly make the extension available on VSX, so we can download it in VSCodium?

Thanks.

What are the steps to reproduce this issue?

1. Install 1.58
2. Run Better Pest on a test file
3. Uses the wrong PHP version in composer

What happens?

Errors out on using wrong PHP version for platform_check.

What were you expecting to happen?

For it to test the file or filter.

Any other comments?

I downgraded to May 2021 (version 1.57) & it works.

What versions are you using?

Mac OS
Better Pest Version: v0.1.0

What are the steps to reproduce this issue?

1. Install Pest and the Laravel plugin for it
2. Create the following test

it('shows the home page', function () {
    get("/")->assertOk();
});

3. Place the cursor on line 2 and run the Better Pest:run command

What happens?

The terminal outputs
No tests executed!

What were you expecting to happen?

For the command to correctly detect the test function that the cursor is within and run that test.

it('expects true is true', function () {
    expect(true)->toBeTrue();
});

Place the cursor on line 2 of this test and run the command, it works as expected.

Summary

Ability to fall back to PHPUnit when Pest isn't installed.

Detailed Description

Before starting to use Pest, I would have the "Better PHPUnit" package installed. I still have projects that use PHPUnit.
Having both installed doesn't really work due to the keyboard shortcuts conflict. If this package could detect whether Pest is installed, it could run pest, otherwise fall back to phpunit.

Maybe this is already possible?

Summary

Does better-pest have a test explorer for vscode?

Detailed Description

Does better-pest have a test explorer for vscode? If not, do you have a suggestion for one to use or could one be added?

Possible Implementation Ideas

What are the steps to reproduce this issue?

1. install pest
2. instal better pest extension
3. run a file/test/suit

What happens?

Yesterday I've been working regulary, and today, the tasks for running tests stopped working.

What were you expecting to happen?

The tests command to appear in terminal

Any logs, error output, etc?

Everything empty.

Any other comments?

I tried restarting the whole extension and nothing happens (delete the extension from vscode and delete the folder manualy)

What versions are you using?

Operating System: Windows 10
Package Version: v0.1.0

What are the steps to reproduce this issue?

1. When configure pest binary using vscode config screen the property better-phpunit.pestBinary appears. The right is better-pest.pestBinary

What happens?

Using wrong property is highlighted right but not work. Switch to working property will not highlight but works.

What are the steps to reproduce this issue?

1. Place in the title of any test a single quote ' for example: check the plan\'s seating limit
2. Execute the test

What happens?

The test does not run

What were you expecting to happen?

That the test runs normally

Any logs, error output, etc?

/bin/bash: -c: line 1: unexpected EOF while looking for matching `''
/bin/bash: -c: line 2: syntax error: unexpected end of file

What versions are you using?

Operating System: Windows 10
Package Version: v0.1.0

What are the steps to reproduce this issue?

1. Setup a minimal Laravel Herd project
   (for more detail follow along: https://youtu.be/w-cebRYZH9E)

What happens?

After installing the VSCode Extension, adding the keyboard shortcuts to my VSCode settings and trying to run a pest with
cmd+k cmd+r the terminal displays the following to happen:

OS and Plugin Version: I am using macOS Ventura 13.5 and the Better Pest v0.1.0 version

Am I missing something obvious or do I have any additional configurations to make?

Thanks in advance
Felix

What are the steps to reproduce this issue?

1. Install extension
2. Focus integrated terminal
3. Press ⌘-K

What happens?

The status bar shows the following message:
"(⌘K) was pressed. Waiting for second key of chord."

What were you expecting to happen?

The terminal screen should be cleared.

Any other comments?

Disabling this extension fixes the issue.

What versions are you using?

Operating System: macOS Ventura 13.2.1
Package Version: v0.1.0

What are the steps to reproduce this issue?

test('it can read config values', function() {
    $this->assertEquals(config('my-package.name'), 'My Package');
}

When running the test using Cmd+K, Cmd+R

What happens

It gives an error Target class [config] does not exist.

What were you expecting to happen?

It should run the test without giving the above error. When I run the test from terminal it runs flawlessly without any error.
I am running this test from within a local package using Orchestra Testbench.

Any logs, error output, etc?

…

Any other comments?

It's actually not picking up tests\Pest.php or even uses(Orchestra\Testbench\TestCase::class) in the file when run thru the extension in vscode (from within a local Laravel package)
However, it picks up both tests\Pest.php and/or uses(Orchestra\Testbench\TestCase::class) in the file when run from the terminal (again from within a local Laravel Package)

What versions are you using?

Operating System: macOS 10.15.7
Package Version: 0.3.1

What are the steps to reproduce this issue?

1. Have Better Pest extension installed
2. Spin up a new laravel project with Breeze into Pest
3. Open up the example test file
4. Run the test using Better Pest's keybinding

What happens?

Terminal is delayed for around 5 seconds, then it opens up and the testing begins.

What were you expecting to happen?

Expected the terminal to open up instantly and begin testing.

Any logs, error output, etc?

Observation 1: If the same terminal stays up, then I run the test again (like using the "run the previous test" command), then the terminal clears up except for the first circle (being emptied), then everything is delayed for about 5 seconds, then the testing begins by then!
Observation 2: There is no delay with pest tests ran through php artisan test at any point in time.

Any other comments?

Workaround: If I run Better PHPUnit to test the pest file, I get the error, but then the response from VSC is back to normal; instantly running the tests using Better Pest's keybinding! That error has to be triggered in order to do something to VSC and make it respond normally to testing!

What versions are you using?

Operating System: 5.19.0-43-generic #44-Ubuntu x86_64 GNU/Linux
Package Version: 0.1.0
VSC Version: 1.79.0

I'm not sure where the problem is, but using Better Pest with lando (docker) on Windows, it fails to filter the test.

NOTE: If I run the full command, same as the Better Pest task is running, in a terminal, everything works as expected, i.e. only one test is run!

This is the officially recommended version to use from https://pestphp.com/docs/editor-setup. Yet it hasnt had updates since October 25, 2020.

• There are pull requests here that are over a year old
• There are issues that have never been resolved
• In VSCode there is the ability to now list tests visually which would be a nice addition to this extension (See: https://marketplace.visualstudio.com/items?itemName=chiefmyron.phpunit-test-workbench)

By the way, I'm the maintainer for the Psalm VSCode plugin (https://github.com/psalm/psalm-vscode-plugin)

@m1guelpf would you be willing to add collaborators? I'd be willing to work on these.

Summary

Add retry test after task is finished.

Detailed Description

Currently when a task is finished, the only option is to close it.

It will be very helpful if there is a retry test too.
So when we finished fixing the test, we don't need to go to test file and run test again, just retry on the terminal output.

Possible Implementation Ideas

Use keyboard key r to retry
Use other keys to close

What are the steps to reproduce this issue?

1. Initialize an empty composer project (with composer init)
2. Install Pest PHP according to documentation
3. Create a Pest test and run the better-pest.run command
4. In the terminal it says: No tests executed!

What happens?

I think Pest requires filters in packages to include underscores, even if they don't have them in the test name.

Given I have this test:

it('is true', function () {
    expect(true)->toBeTrue();
});

When I run better-pest.run, it translates to ./vendor/bin/pest TestFile.php --filter 'is true' in the terminal.

But instead it should be ./vendor/bin/pest TestFile.php --filter 'is_true', with underscores, as that does work.

What were you expecting to happen?

To replace spaces by underscores.

What versions are you using?

Operating System: MacOS
Pest Version: dev-master

Summary

Allow option to open external terminal when running tests

Detailed Description

When running tests on a small screen and VS Code uses its terminal tab, the results can get difficult to read since there is no space in the screen.

An interesting solution possibly would be to allow the users to opt in to run tests in an external terminal so the results will be displayed on a larger window.

Possible Implementation Ideas

Hello,

When run vscode extension this, terminal show end, how to hide it?

The terminal process "/bin/zsh '-l', '-i', '-c' ...
Terminal will be reused by tasks, press any key to close it. 

But when run with termial it not show

Thanks !