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
In this post, we are going to talk about different Magento tools for testing, audit and code analysis. There are 3 major groups of testing: Unit, Functional and Integration. They all have their goals, so you should know their major features to choose the most suitable for your issue. Of course, there are extensions and services developed to perform testing, audit and code analysis for Magento, but let’s start from the theoretical aspect of the problem.
The first major software testing method is a unit testing. Its main goal is to determine if individual parts of source code and different sets of program modules work correctly. This testing method relies on units as the smallest testable parts of an application. A unit could be an individual function, an entire module or interface. The gradation depends on a programming type. Each test case should be independent from the other cases. Substitutes such as mock objects, method stubs, fakes, and harnesses are usually used in order to assist testing a module in isolation. By performing unit tests, you can get all the necessary information required to understand that code behaves as intended. You set apart each part of the program and find out if individual parts work as expected.