Quality Assurance is a crucial part of any development process before deployment. It is important to be able to find new types of bugs, which are often quite unpredictable; it’s better to prevent the issue than to solve it. Better preventing the issue than solving it. For that, there is a great tool – Exploratory Testing.

What is Exploratory Testing? Why do I need it and how will Exploratory Testing help me? This article will answer these questions no matter what your role is – QA Engineer, Developer, Designer, or Business Analyst.

The Magento Functional Testing Framework was presented by Tom Erskine during the contribution day following MageTestFest, held in Amerfoort in November of the previous year. Currently under heavy development, it has already seen 2 releases and has reached version 2.0.3.

Many testing tools are overly complicated. For a while, we searched for an automated testing framework that would meet our needs. We tried a lot of frameworks like Selenide and CasperJS but they were not exactly what we’ve been looking for. Not so long ago, we’ve discovered a tool Codeception and I want to introduce you to it.

It is important to keep your online store updated to the latest Magento version, as it has the most recent improvements, security updates, and other fixes. And every time such upgrade is performed, the website should be carefully tested to make sure that all issues or conflicts are fixed after the upgrade.

Today we want to share with you our test cases after Magento upgrade that we normally use testing Magento stores.