Download the PHP package lag/colonel-smoker-bundle without Composer
On this page you can find all versions of the php package lag/colonel-smoker-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download lag/colonel-smoker-bundle
More information about lag/colonel-smoker-bundle
Files in lag/colonel-smoker-bundle
Package colonel-smoker-bundle
Short Description The Colonel helps you to check the smoke in your application
License MIT
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 colonel-smoker-bundle
Colonel Smoker Bundle
The Colonel Smoker is an expert in smoke. He can even tell if your application is smoking before deploying it to production.
The Colonel Smoker find the URLs of your Symfony application (only Symfony is supported now) and looks for 500 errors.
Main features :
- helps providing requirements parameters for your dynamic URLs
- uses the routes declared in the Symfony routing by default
- check for response code
- check if the resulted html contains dynamic data from your entity
The goal is to ensure that each urls in your application does not contains critical errors. It is especially designed for application which have pages with complex and dynamic data to display.
This bundle relies on Symfony service injection. If your are not familiar with this, you can read documentation here
Installation
Configuration
Usage
-
First generate the URL cache :
- Then run the smoke tests :
If you use the Symfony WebServer bundle, dont forget to run
bin/console server:start --env=test.
How it works
The Colonel Smoker will read the configuration and use the Symfony routing to build the urls of your application. Urls are stored in a cache. Then he calls each urls and analyze the response to find 500 errors. But it can tests more like if the html contains some static or dynamic values.
For example, if your application handles articles, the Colonel Smoker can check if the page displaying the article contains the article title.
Documentation
Reference Configuration
The Colonel relies on the Symfony DomCrawler component and the Goutte client.
Known Issues
In dev environment, we call the Symfony Client to many times when having the server on the same machine (when using the Symfony web server for example), the cache miss to retrieve value and throws an exception. It causes some build failures. A patch is in progress to avoid this.
Road map
- [ ] Add an option to set a timeout in tests to avoid error with the cache
- [ ] Add a check to see if the web server is running
All versions of colonel-smoker-bundle with dependencies
ext-dom Version *
doctrine/doctrine-bundle Version ^1.9
doctrine/orm Version ^2.6
fabpot/goutte Version ^3.2
symfony/config Version ^4.1
symfony/console Version ^4.1
symfony/dependency-injection Version ^4.1
symfony/filesystem Version ^4.1
symfony/http-kernel Version ^4.1
symfony/options-resolver Version ^4.1
symfony/property-access Version ^4.1
symfony/routing Version ^4.1
symfony/yaml Version ^4.1
twig/twig Version ^2.5