The ISTQB definition of the Test Plan is a document describing the scope, approach, resources and schedule of intended test activities. It also identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, 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. It is a record of the test planning process.
If you need to create a Test Plan for your Salesforce Testing phase then it would be good practice (you are ensuring quality after all!) to follow the IEEE Standard for Software Documentation. This is a standard that will assist in determining what should be included within your Salesforce Test Plan:
Test Plan Identifier
- A unique identifier
- Introduction
- Summary of the items and features to be tested
- Need for and history of each item (optional)
- References to related documents such as project authorization, project plan, QA plan, configuration management plan, relevant policies, relevant standards
- References to lower level test plans
Test Items
- Test items and their version
- Characteristics of their transmittal media
- References to related documents such as requirements specification, design specification, users guide, operations guide, installation guide
- References to bug reports related to test items
- Items which are specifically not going to be tested (optional)
Features to be Tested
- All software features and combinations of features to be tested
- References to test-design specifications associated with each feature and combination of features
Features Not to Be Tested
- All features and significant combinations of features which will not be tested
- The reasons these features won’t be tested
Approach
- Overall approach to testing
- For each major group of features of combinations of featres, specify the approach
- Specify major activities, techniques, and tools which are to be used to test the groups
- Specify a minimum degree of comprehensiveness required
- Identify which techniques will be used to judge comprehensiveness
- Specify any additional completion criteria
- Specify techniques which are to be used to trace requirements
- Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadline
Item Pass/Fail Criteria
- Specify the criteria to be used to determine whether each test item has passed or failed testing
- Suspension Criteria and Resumption Requirements
- Specify criteria to be used to suspend the testing activity
- Specify testing activities which must be redone when testing is resumed
Test Deliverables
- Identify the deliverable documents: test plan, test design specifications, test case specifications, test procedure specifications, test item transmittal reports, test logs, test incident reports, test summary reports
- Identify test input and output data
- Identify test tools (optional)
Testing Tasks
- Identify tasks necessary to prepare for and perform testing
- Identify all task interdependencies
- Identify any special skills required
Environmental Needs
- Specify necessary and desired properties of the test environment: physical characteristics of the facilities including hardware, communications and system software, the mode of usage (i.e., stand-alone), and any other software or supplies needed
- Specify the level of security required
- Identify special test tools neededIdentify any other testing needs
- Identify the source for all needs which are not currently available
Responsibilities
- Identify groups responsible for managing, designing, preparing, executing, witnessing, checking and resolving
- Identify groups responsible for providing the test items identified in the test plan.
Test Items Section
- Identify groups responsible for providing the environmental needs identified in the Environmental Needs section
- Staffing and Training Needs
- Specify staffing needs by skill level
- Identify training options for providing necessary skills
Schedule
- Specify test milestones
- Specify all item transmittal events
- Estimate time required to do each testing task
- Schedule all testing tasks and test milestones
- For each testing resource, specify its periods of use
Risks and Contingencies
- Identify the high-risk assumptions of the test plan.
- Specify contingency plans for each
Approvals
- Specify the names and titles of all persons who must approve the plan.
- Provide space for signatures and dates
The Salesforce Test Plan that you create does not have to follow the above exactly nor use the same terminology as you will need it to be specific to your own company, but you should at least consider if you are covering the above areas.
A Certified Salesforce Administrator, Salesforce Einstein Analytics and Discovery Consultant, ISTQB® Certified Tester Advanced Level, Jitterbit Foundations and Jitterbit Core Certified QA Test Automation Manager who is also an experienced creative all-rounder with enthusiasm and the proven ability to understand client needs and deliver satisfying solutions. A thirst for new technology and modern Quality Assurance and Testing techniques keeps me aspiring to learn at every opportunity. My current role is at Publicis Sapient who are an official Salesforce Platinum Partner. Publicis Sapient provide Salesforce expertise and strategic thinking that enables organisations to transform their business to Cloud-based technology.