Magento 2 has been released, so we are trying to dig more useful materials related to the new version of the popular ecommerce platform. This time, our attention has been drawn to Alan Kent’s article related to Magento 2 testing, so we’ve also decided to cover this topic on the Firebear blog. For those developers willing to improve the quality of their Magento 2 projects, testing is mandatory; therefore, we propose you to examine the following Magento 2 guide, which is based on the aforementioned article, the official documentation, as well as our own experience related to both the Magento 2 platform and testing.
UPD (11.02.16): Magento 2 code katas and Getting your hands dirty testing Magento 2
You can always move out of MySQL. At least, there are 2 alternatives: MariaDB and Percona. MariaDB is a fork of the MySQL developed by the community under the GNUGPL from the original creators of MySQL. The intents of MariaDB include maintaining high compatibility with MySQL, ensuring a “drop-in” replacement capability with library binary equivalency and matching with MySQL commands and APIs. Percona Server is another MySQL alternative which if free and open source. It offers high scalability, improved performance, useful features, and all the necessary instrumentations. In addition, Percona relies on self-tuning algorithms and supports high-performance hardware. In this post, we gathered all the information necessary to understand whether you should stay with MySQL or move to alternative solutions, such as MariaDB and Percona.