Download the PHP package browserstack/browserstack-local without Composer
On this page you can find all versions of the php package browserstack/browserstack-local. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download browserstack/browserstack-local
More information about browserstack/browserstack-local
Files in browserstack/browserstack-local
Package browserstack-local
Short Description PHP bindings for BrowserStack Local
License MIT
Homepage https://github.com/browserstack/browserstack-local-php
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package browserstack-local
browserstack-local-php
PHP bindings for BrowserStack Local.
Installation
Installation is possible using Composer.
If you don't already use Composer, you can download the composer.phar binary:
curl -sS https://getcomposer.org/installer | phpThen install the library:
`php composer.phar require browserstack/browserstack-local`Install all depenedencies:
php composer.phar install
Test the installation by running a simple test file, check out example.php in the main repository.
Example
Arguments
Apart from the key, all other BrowserStack Local modifiers are optional. For the full list of modifiers, refer BrowserStack Local modifiers. For examples, refer below -
Verbose Logging
To enable verbose logging -
Folder Testing
To test local folder rather internal server, provide path to folder as value of this option -
Force Start
To kill other running Browserstack Local instances -
Only Automate
To disable local testing for Live and Screenshots, and enable only Automate -
Force Local
To route all traffic via local(your) machine -
Proxy
To use a proxy for local testing -
- proxyHost: Hostname/IP of proxy, remaining proxy options are ignored if this option is absent
- proxyPort: Port for the proxy, defaults to 3128 when -proxyHost is used
- proxyUser: Username for connecting to proxy (Basic Auth Only)
- proxyPass: Password for USERNAME, will be ignored if USERNAME is empty or not specified
Local Proxy
To use local proxy in local testing -
- localProxyHost: Hostname/IP of proxy, remaining proxy options are ignored if this option is absent
- localProxyPort: Port for the proxy, defaults to 8081 when -localProxyHost is used
- localProxyUser: Username for connecting to proxy (Basic Auth Only)
- localProxyPass: Password for USERNAME, will be ignored if USERNAME is empty or not specified
PAC (Proxy Auto-Configuration)
To use PAC (Proxy Auto-Configuration) in local testing -
- pac-file: PAC (Proxy Auto-Configuration) file’s absolute path
Local Identifier
If doing simultaneous multiple local testing connections, set this uniquely for different processes -
Additional Arguments
Binary Path
By default, BrowserStack local wrappers try downloading and executing the latest version of BrowserStack binary in ~/.browserstack or the present working directory or the tmp folder by order. But you can override these by passing the -binarypath argument. Path to specify local Binary path -
Logfile
To save the logs to the file while running with the '-v' argument, you can specify the path of the file. By default the logs are saved in the local.log file in the present woring directory. To specify the path to file where the logs will be saved -
Contribute
Testing is possible using PHPUnit.
To run the tests, run the command: phpunit
Reporting bugs
You can submit bug reports either in the Github issue tracker.
Before submitting an issue please check if there is already an existing issue. If there is, please add any additional information give it a "+1" in the comments.
When submitting an issue please describe the issue clearly, including how to reproduce the bug, which situations it appears in, what you expect to happen, what actually happens, and what platform (operating system and version) you are using.
Pull Requests
We love pull requests! We are very happy to work with you to get your changes merged in, however, please keep the following in mind.
- Adhere to the coding conventions you see in the surrounding code.
- Include tests, and make sure all tests pass.
- Before submitting a pull-request, clean up the git history by going over your commits and squashing together minor changes and fixes into the corresponding commits. You can do this using the interactive rebase command.
