Planning for Testing

Planning for Testin

Testing inevitably requires considerable resources. The efficient use of these resources requires careful scheduling and effective management. We will focus on the technical aspects of planning and scheduling of various test activities. We’ll set about determining what needs to be done at the technical level, who can do it and when this should be done.

We will propose the ways of obtaining estimates, and at the same time we will not go into details about scheduling. Planning at the technical level is driven by templates, which are created as needed by developers. We will describe the hierarchy of test plans and correlate them with standard templates, using IEEE 829 standard Test Plan Template. We will also discuss the inclusion of risk analysis in the test planning process. By the way, if you want to know more about testing and related processes, get in touch with qa consulting companies from Ukraine, namely Cherkassy city.

A fundamental testing process can be summarized as follows: test early, test often, test enough. We will define a more detailed process in which a testing phase is envisaged for each development stage (Analysis, Testing, Development, Testing, Coding, Testing). We’ll also consider a generalized set of steps in which we define the basic tasks that are performed at each of these development stages. In addition, we will discuss testing from management / resource allocation perspective, describe various aspects of testing and report how to reach a compromise between these aspects, namely how to balance tradeoffs along them.

Overview of the development process

Any process is a continuous sequence of actions that brings you closer to an end. Most software design books, as well as software designers themselves, emphasize four major activities within a software development process (consequent to the completion of systems’ engineering and before the first deployment of the software):

1. Analysis – at this stage the focus is on understanding the problem and formulating requirements for different components of the software system.
2. Design – at this stage, the focus is on solving problems in software.
3. Implementation – at this stage, the focus is on translating the project into program codes.
4. Testing – at this stage, the focus is on ensuring that inputs to the software product produce expected results as the requirements specify.

To continue reading this article, please, follow this link…..