Test plan for manual QA in Magento 2

Magento is a leading digital commerce platform. It is built on open-source technology. 

The platform provides online merchants unparalleled flexibility and control over their online stores' look, content, and functionality. Magento's intuitive Admin features powerful marketing, search engine optimization, and product management tools that give you the power to create sites tailored to your unique business needs. Robust and scalable, Magento offers you a stable, secure, and customizable solution for your growing business.

This article will start with one of the main activities before the initial testing process - creating a test plan.

What is a Test Plan

A test Plan is a document describing software testing scope and activities and is a basis for testing types before the start.

There are a lot of definitions that can be found on the internet. Still, in our opinion, one of the most accurate ones is ISTQB- a document describing the scope, approach, resources, and schedule of intended test activities. It identifies, amongst other test items, the features to be tested, the testing tasks, who will do each job, the degree of tester independence, the test environment, the test design techniques, and entry and exit criteria to be used. And the rationale for their choice and any risks requiring contingency planning.

Types of Test Plans

There are several test plan types. They are:

  • Master Test Plan is a single high-level test plan for a project/product that unifies all other testing plans.
  • Testing Level Specific Test Plans - it is a plan for each level of testing. They are the Unit test plan, Integration test plan, System test plan, and Acceptance Test plan.
  • Testing Type Specific Test Plans - Plans for significant types of testing like performance or security test plans.

Test Plan Template

Each test plan has a separate test plan template. It is the list of what a good test plan should contain:

  • Test Plan identifier (Provide a unique identifier for the document);
  • Introduction (Provide an overview of the test plan, Specify the goals/objectives, and specifies any constraints);
  • Reference (List the related documents, with links to them if available, including the following: project plan and configuration management plan);
  • Test Items (list the test items (software/products) and their versions);
  • Features to be tested (List the features of the software/products to be tested, and provide references to the requirements and Design specifications);
  • Features Not to be tested (List the features that are not tested and the reason why it is like that);
  • Approach (Here, you need to mention the overall approach to testing, and you need to specify the testing levels);
  • Item Pass/Fail Criteria (You need to specify criteria that will be used to determine what points are passed and what are failed);
  • Suspension Criteria and Resumption Requirements (Here, you need to specify the criteria that will be used to suspend the testing activities and testing activities that should be redone after restart of the testing);
  • Test Deliverables (List the test deliverables and links to them if available, including the following: test plan, test cases, test scripts defect/enhancement Logs, Test reports.);
  • Test Environment (You need to specify the properties of the test environment: hardware, software, network, etc.);
  • Estimate (You need to provide a summary of test estimates (cost and effort) and provide a link to the detailed estimation);
  • Schedule (You need to create and provide a detailed summary of the program, specifying key test milestones and provide a link to the exact schedule);
  • Staffing and Training Needs (Here, you need to specify staffing by roles and required skills. Identify training that is necessary to provide those skills, if not already acquired);
  • Responsibilities (It is a list of duties of each team/role/individual);
  • Risks (Here, you need to create a list of the risks that have been identified and specify a mitigation plan);
  • Assumptions and Dependencies (As it is clear from the name, it is a list of beliefs that have been made during the planning and dependencies);
  • Approvals (You need to specify the names and the roles of all persons who must approve the plan and provide a space for signatures and dates.)

Learn more about testing in Magento 2 in the FREE course: