mediashare / shell-psysh
An interactive shell for modern PHP.
v0.12.10.11
2025-07-16 11:59 UTC
Requires
- php: ^8.0 || ^7.4
- ext-json: *
- ext-tokenizer: *
- nikic/php-parser: ^5.0 || ^4.0
- symfony/console: ^7.0 || ^6.0 || ^5.0 || ^4.0 || ^3.4
- symfony/var-dumper: ^7.0 || ^6.0 || ^5.0 || ^4.0 || ^3.4
Requires (Dev)
Suggests
- ext-pcntl: Enabling the PCNTL extension makes PsySH a lot happier :)
- ext-pdo-sqlite: The doc command requires SQLite to work.
- ext-posix: If you have PCNTL, you'll want the POSIX extension as well.
Conflicts
- symfony/console: 4.4.37 || 5.3.14 || 5.3.15 || 5.4.3 || 5.4.4 || 6.0.3 || 6.0.4
- dev-main / 0.12.x-dev
- v0.12.10.x-dev
- v0.12.10.11
- v0.12.10.8
- v0.12.10.7
- v0.12.10.6
- v0.12.10.5
- v0.12.10.4
- v0.12.10.3
- v0.12.10.2
- v0.12.10.1
- v0.12.10
- v0.12.9
- v0.12.8
- v0.12.7
- v0.12.6
- v0.12.5
- v0.12.4
- v0.12.3
- v0.12.2
- v0.12.1
- v0.12.0
- 0.11.x-dev
- v0.11.22
- v0.11.21
- v0.11.20
- v0.11.19
- v0.11.18
- v0.11.17
- v0.11.16
- v0.11.15
- v0.11.14
- v0.11.13
- v0.11.12
- v0.11.11
- v0.11.10
- v0.11.9
- v0.11.8
- v0.11.7
- v0.11.6
- v0.11.5
- v0.11.4
- v0.11.3
- v0.11.2
- v0.11.1
- v0.11.0
- v0.10.12
- v0.10.11
- v0.10.10
- v0.10.9
- v0.10.8
- v0.10.7
- v0.10.6
- v0.10.5
- v0.10.4
- v0.10.3
- v0.10.2
- v0.10.0
- v0.9.12
- v0.9.11
- v0.9.9
- v0.9.8
- v0.9.7
- v0.9.6
- v0.9.5
- v0.9.4
- v0.9.3
- v0.9.2
- v0.9.1
- v0.9.0
- v0.8.18
- v0.8.17
- v0.8.16
- v0.8.15
- v0.8.14
- v0.8.13
- v0.8.12
- v0.8.11
- v0.8.10
- v0.8.9
- v0.8.8
- v0.8.7
- v0.8.6
- v0.8.5
- v0.8.4
- v0.8.3
- v0.8.2
- v0.8.1
- v0.8.0
- v0.7.2
- v0.7.1
- v0.7.0
- v0.6.1
- v0.6.0
- v0.5.2
- v0.5.1
- v0.5.0
- v0.4.4
- v0.4.3
- v0.4.2
- v0.4.1
- v0.4.0
- v0.3.5
- v0.3.4
- v0.3.3
- v0.3.2
- v0.3.1
- v0.3.0
- v0.2.1
- v0.2.0
- 0.1.x-dev
- v0.1.12
- v0.1.11
- v0.1.10
- v0.1.9
- v0.1.8
- v0.1.7
- v0.1.6
- v0.1.5
- v0.1.4
- v0.1.3
- v0.1.2
- v0.1.1
- v0.1.0
- dev-develop
This package is auto-updated.
Last update: 2025-07-20 04:56:38 UTC
README
Overview
The Shell Tester is a tool for testing shell scripts and commands. It allows you to define test cases, execute them against your code, and verify the results.
Getting Started
- Navigate to the
test/shell-tester
directory. - Review existing test cases: Examine the files in this directory to understand how tests are structured and written. The tests typically involve running a command or script, capturing its output, and asserting that the output matches an expected value.
- Write new test cases: Create new files in this directory, following the existing pattern.
Test Case Structure
Each test case consists of the following elements:
- Command/Script to Execute: The command or script that you want to test.
- Expected Output: The output that you expect the command or script to produce.
Contributing
- Fork the repository.
- Create a new branch for your changes.
- Add your test cases to the
test/shell-tester
directory. - Ensure that your test cases pass by running the test suite (details on how to run the test suite would go here if a testing framework was used).
- Submit a pull request.
Example Test Case
# This is an example test case. # It tests the `ls -l` command. command: ls -l expected_output: - total 4 - -rw-r--r-- 1 user group 1024 Jan 1 00:00 file1.txt - -rw-r--r-- 1 user group 2048 Jan 1 00:00 file2.txt
Note: The exact format of the test case may vary depending on the specific testing framework used.
Further Information
- [Link to documentation (if available)]
- [Link to issue tracker]