Quality Assurance is a crucial part of any development process before the deployment. It is important to be able to find new types of bugs, which are often quite unpredictable. 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.

Hello, I will be glad to share with you a few interesting tools that I use in QA work to make developer’s life a little bit more difficult.

As we all know developer’s life is hard. But we have QA to make it harder. We try to find problems or break something that developer has created. Let me tell you about tools that help me with it in manual web application testing.

Magento Functional Testing Framework was presented by Tom Erskine during contribution day which followed MageTestFest, which took place in Amerfoort in November last year. Right now it’s under heavy development, there were already 2 releases and it reached version 2.0.3.

Most of the testing tools are too complicated. For a long time we’ve been looking for an automatic testing framework to 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.