This section is about the testing of artifacts that are created during the process of creating software. So when we are talking about artifacts, we are talking about the various elements that are produced by the developers and others in the creative process. There are several types of tests that will need to be run. They include: strategy, plan, test case, script, suite and then last is the test harness. This section will discuss a little about each of these different steps of the testing process.
Test strategy is the first that we are going to talk about and can be more of a high level approach, or more of a general overview. The strategy is the component that is used for the communications with our stakeholders. This would include individuals of the development team, other members of the project and administrators and/ or project managers. It will tell those involved what we are trying to accomplish, goals, methodology types, time requirements, the environment in which the software is being developed. So, there are a lot of pieces to get this particular portion completed. It’s an overview with what specifics as to how to complete the project, as well as evaluative tools to check on your results, for monitoring how well you have met your goals. There is the list of the SMART goals we discussed earlier in this course. If you remember: they were specific, measurable, achievable, realistic and timely. So, the strategy test is written to be very high level in nature and have a lot of specifics to help those involved have a really good idea overall as to what the methods of achieving the goals are, the funding, the timeline, the environment we are working in, the objectives and goals as well as restrictions and evaluations in which we are to work.
The test strategy breaks down and there is also what we call the test plan. This is the systematic step by step of how we are going to accomplish the objectives and meet our goals. So, these procedures will show the general workflow that the developer would follow in order to complete the logical steps. This is what we call the test plan. Then from the test plan, we have what is called a test case.
The requirements from the strategy and plan together in one document where we indicate what actually happens when the testing is going on. This is the part where we are measuring and validating as we meet the customer’s requirements. This is where we are tracking and figuring out the conditions and so this is the test case. In addition to the test case, we also have the test script.
The testing script is the step by step of how to perform the test, and is what the tester will go through and follow. For each of the testing case scenarios, there should be a scripting test. There should be a script to validate to tell us exactly how to go about running the test for the test case.
The collection of all of the artifacts, any other tools, any documentation input, and so on are altogether, collectively referred to as the test harness. All of these elements are important, initiating at test strategy and running down the list all the way to the scripts could be included in the test harness. Any of the input, tools, techniques, and so on would collect altogether under test harness.