Download the PHP package dbstudios/analyst without Composer
On this page you can find all versions of the php package dbstudios/analyst. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dbstudios/analyst
More information about dbstudios/analyst
Files in dbstudios/analyst
Package analyst
Short Description A feature testing library inspired by GitHub's Scientist
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 analyst
Analyst
A PHP feature testing library inspired by GitHub's Scientist.
Please be aware, this README is a work in progress, and may contain incomplete information.
Installation
How do I analyze?
Let's pretend that you have a large web application, and are in the process of changing the way you verify user permissions when accessing a page.
That's it! The run method of Experiment will always return the result from your control. Both your control and
your candidate will be run, and Analyst will record what happened to both blocks of code. In the next section, we'll
take a look at what you can do with that information.
Publishing Experiment Results
Testing multiple code paths is pretty useless if we don't do anything with the information we get from our experiment.
That's where publishing comes into play. All you need to do is implement that publish method in a custom Experiment
class.
Now, if we were to rewrite our earlier user permission example to use our custom MyExperiment class, it would look
like this.
In the above example, we created our own Experiment implementation, named MyExperiment. In it, we made sure we had
a database connection (using PHP's PDO class), and wrote data to it using the publish method. Then, when we ran
our experiment within our controller example, all we needed to do was provide the extra arguments to the create static
method of MyExperiment (which we implemented ourselves to allow for the additional constructor argument).
After every experiment is run, Analyst will always call the publish method of the experiment used to do our analysis.
Our options aren't limited to simple database inserts. You might decide to log the data to a file using a library like
Monolog, or you might send it off to a cloud service. It's up to you!
