blackfire / player
A powerful web crawler and web scraper with Blackfire support
Installs: 14 622
Dependents: 0
Suggesters: 0
Security: 0
Stars: 485
Watchers: 37
Forks: 64
Open Issues: 15
Type:project
Requires
- php: >=8.2
- blackfire/php-sdk: ^2.0
- doctrine/annotations: ^2.0
- fakerphp/faker: ^1.10
- guzzlehttp/guzzle: ^6.1
- maltyxx/images-generator: ^1.0
- mtdowling/jmespath.php: ^2.2
- nyholm/psr7: ^1.5
- psr/log: ^1.0
- sentry/sentry: ^3.12
- symfony/console: ^6.0
- symfony/css-selector: ^6.0
- symfony/dom-crawler: ^6.0
- symfony/event-dispatcher: ^6.0
- symfony/expression-language: ^6.0
- symfony/filesystem: ^6.0
- symfony/http-client: ^6.2
- symfony/property-access: ^6.2
- symfony/serializer: ^6.2
- symfony/var-dumper: ^6.0
- symfony/yaml: ^6.0
- webmozart/glob: ^4.6
- webmozart/path-util: ^2.3
Requires (Dev)
- symfony/finder: ^6.0
- symfony/phpunit-bridge: ^6.0
- symfony/process: ^6.0
- dev-master / 1.33.x-dev
- v1.31.0
- v1.30.0
- v1.29.0
- v1.28.1
- v1.28.0
- v1.27.0
- v1.26.0
- v1.25.0
- v1.24.0
- v1.23.0
- v1.22.0
- v1.21.0
- v1.20.0
- v1.19.0
- v1.18.0
- v1.17.0
- v1.16.0
- v1.15.0
- v1.14.0
- v1.13.0
- v1.12.0
- v1.11.0
- v1.10.1
- v1.10.0
- v1.9.3
- v1.9.2
- v1.9.1
- v1.9.0
- v1.8.2
- v1.8.1
- v1.7.0
- v1.6.1
- v1.6.0
- v1.5.1
- v1.5.0
- v1.4.1
- v1.4.0
- v1.3.0
- v1.2.1
- v1.2.0
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.1
- v1.0.0
- v0.16.0
- v0.15.1
- v0.15.0
- v0.14.0
- v0.13.0
- v0.12.0
- v0.11.0
- v0.10.0
- v0.9.0
- v0.8.2
- v0.8.1
- v0.8.0
- v0.7.0
- v0.6.0
- v0.5.0-alpha-5
- v0.5.0-alpha-4
- v0.5.0-alpha-3
- v0.5.0-alpha-2
- v0.5.0-alpha-1
- v0.4.6
- v0.4.5
- v0.4.4
- v0.4.3
- v0.4.2
- v0.4.1
- v0.4.0
- v0.3.0
- v0.2.0
- v0.1.0
This package is auto-updated.
Last update: 2023-06-05 07:23:43 UTC
README
Blackfire Player is a powerful performance testing application. It provides a nice DSL to crawl HTTP services, assert responses, and extract data from HTML/XML/JSON responses.
Read more about how to download and use Blackfire Player.
Usage
Use blackfire-player
with Docker.
Working directory is expected to be at /app
in the container.
Example running a scenario located in my-scenario.bkf
file:
docker run --rm -it -e BLACKFIRE_CLIENT_ID -e BLACKFIRE_CLIENT_TOKEN -v "`pwd`:/app" blackfire/player run my-scenario.bkf
Note
BLACKFIRE_CLIENT_ID
and BLACKFIRE_CLIENT_TOKEN
environment variables
need to be properly exposed from the host in order to be able to use the Blackfire
Profiler integration.
You may also add a shell alias (in .bashrc
, .zshrc
, etc.) for convenience.
alias blackfire-player=docker run --rm -it -e BLACKFIRE_CLIENT_ID -e BLACKFIRE_CLIENT_TOKEN -v "`pwd`:/app" blackfire/player
Then, after sourcing your RC file, you can use blackfire-player
as if it was
the binary itself:
blackfire-player --version blackfire-player list blackfire-player run my-scenario.bkf