Magento 2 Development Workshop Learn More

Manual QA in Magento 2 for Beginners

10 lessons

Introduction into Magento 2 Testing

Introduction

This new testing course is intended for all people who are interested in testing of Magento 2 platform and testing in general. This can be helpful for all QA engineers with different seniority

About Magento

Magento is a leading digital commerce platform. It is built on open source technology. Magento provides online merchants with unparalleled flexibility and control over the look, content, and functionality of their online stores. Magento’s intuitive Admin features powerful marketing, search engine optimization, and product management tools that give you the power to create sites that are tailored to your unique business needs. Robust and scalable, Magento offers you a stable, secure, and customizable solution for your growing business.

Test Methodology

Any QA engineer can perform various testing methodologies: automation, manual, load & performance, functional, etc.

Automation testing

It is a type of testing where verification, bug tracking and analysis of the received results are done by the QA engineer with tools for creating automation script.

Manual testing

It is a process in development of the product where verification and bug tracking are made by the QA engineer by recreation or modulation of the actions made by the customer user.

Load testing

It is a type of testing of the website or mobile app where QA engineer is modulating situations to analyze the system on requested time of response.

Performance testing

It is type of testing when QA engineer is modulating situations when specified amount of users is using site/app.

Functional testing

It is testing by QA engineers of the specified scenarios by the client that are done by the customer user.

Glossary

We can use the glossary to further lessons of this course:

  1. Bug Report - it is a document, where any user is reporting the issue in layout or in behaviour of any kind of functionality;
  2. Test Case - it is a set of conditions and variables under which QA engineer will determine whether a system under test satisfies requirements or works correctly;
  3. Test Plan - it is a document describing software testing scope and activities;
  4. Checklist - it is a list of all the things that you need to do, information that you want to find out, or things that you need to take somewhere, which you make in order to ensure that you do not forget anything;