To conduct proper testing, it is important to do proper planning before the test cycle starts. The following are some guidelines to keep in mind when planning for the testing phase:

• During the planning phase, create a test plan to define the scope, resources, and tools to be used for the testing, and to identify how bugs will be tracked. Establish the criteria for defining S1/S2 and P1/P2 bugs, depending on the business criticality (severity and priorities).
• Dedicate QA resources for each area in a way similar to what we do for the functional analysts and developers. You need them to start on the project right from the beginning in order to understand the requirements and design that is being put in place. Plan the scope of automation testing, and dedicate resources and time to the automated test script.
• Identify the external resources that need to be engaged during testing. For example, testing with banks for checks/electronic payments, positive pay files, EDI trading partners, customers/vendors, and any other parties to whom you send/receive data, such as D&B (credit) and third-party invoice printing. Start engaging them as early as possible, and align their schedules into the project plan.

Building test scenarios and test cases is important for executing a good test plan. The following tips will help you in developing effective testing scenarios:

• Prepare test scenarios and test cases that are parallel to the design and development phase of the project. Review test cases with the business analysts and the business SMEs, as applicable.
• The goal should be to identify and document each scenario in detail in the form of test cases, rather than stay at a very high level. If you don't document the test cases, there is a high chance of missing them during the execution.
• Maintain a traceability matrix with the number of requirements, function specifications, technical specifications, test scenarios, and test-case IDs.
• Identify the test data to be used, and the specific deviations in the data, in order to maximize the coverage of your testing. Say, for example, if a company has four product lines and all are sold differently, you will need to have scenarios that address each product line.