Zumba Tech

[...] . Since only a portion of our data is in Mongo while the remaining is in MySQL, limiting a test case to work with one datasource or another is too limiting. Workarounds The first workaround we [...]

[...] an issue. With the use of Github, a partner can fork our testing repo at any time, write a test case for the issue they are having, and submit a pull request. We can then verify by reproducing the [...]

[...] : Symbiosis. Symbiosis is a PHP library that allows for easy integration of an event driven plugin system to any PHP project. It also allows the event system to be used stand-alone from the plugin [...]

[...] In many instances, having a plugin system (even for closed-source applications) is a convenient and safe approach to adding [...]

[...] Symbiosis is now more flexable to implement. Our next steps will be to improve the plugin system to be more (and less) coupled to the event system. See the full changeset: https:// [...]

[...] I won’t cover here. What I will cover is once you have your plugin included, how to use our event system to call it. We have several uses for plugins for our cart system. Chief among them is [...]

[...] for easy integration of an event driven plugin system to any PHP project. It also allows the event system to be used stand-alone from the plugin system. Plug Me In In a previous post, I described how [...]

[...] . Our next steps will be to improve the plugin system to be more (and less) coupled to the event system. See the full changeset: https://github.com/zumba/symbiosis/pull/15/files [...]

[...] Github pull requests. We use this internally, but it is also the most common mechanism for open source projects to get community contributions on Github. We think it’s a great way to encourage code [...]

[...] some time doing simple tools to gain in long term. You can see what annotations, some open source projects and few lines of code are able to do. Use it! As I told in the annotations post, it is a [...]

[...] . If you want to make a pull request, even better. :) You are welcome to check our other open source projects on https://github.com/zumba. [...]

[...] Recently we started a new API application in CakePHP 2.2 and put some code and unit tests. When we put the code in Jenkins CI to a continuous integration we setup the code coverage and [...]

[...] regression errors. We simply write a plugin, register the event, and can concentrate the unit tests on the plugin callbacks themselves. [...]

[...] , you’d have to chain a cleanup method after the test case is run. Also, as opposed to unit tests, the failed test will not pinpoint in the code where the error happens, so you’d need to [...]

[...] use composer as their dependency manager. Before you can make anything work, you need to run composer install. This is where the magic happens. Phpcs Dependency First, we need a development dependency [...]

[...] as well. We’ve included a way of installation either via a git submodule, download, or a composer install. The project has 100% code coverage in PHPUnit tests, and we feel comfortable with it’s [...]

[...] and unit tests. When we put the code in Jenkins CI to a continuous integration we setup the code coverage and in the reports we got couple CakePHP core files as not covered. Our application doesn’t [...]

[...] either via a git submodule, download, or a composer install. The project has 100% code coverage in PHPUnit tests, and we feel comfortable with it’s stability. You can see more [...]

[...] does not rely on the user session. For some time we just serialized the cart using the PHP serialize() function and stored it in a binary field in a MongoDB collection. It worked very well [...]