In the Test Plan, you will document those risks Risk Team member lack the required skills for website testing.
This chapter covers the following topics: In the same way that a network designer would be foolish to specify equipment or make technical recommendations without prior knowledge of customer requirements, a test engineer would be misguided to attempt writing a test plan without first understanding the triggers, scope, motives, and expectations for the test initiative.
By rushing ahead and skipping this critical step, you who should write a test plan missing the mark in your testing, focusing on the wrong types of tests, or capturing erroneous results.
This will waste precious time and resources as you continuously redefine your test plan; add, remove, or modify equipment to your lab topology; rerun your test cases; and generate reports.
Taking time to identify the objectives and outline an assessment is critical before you ever step foot into the lab. Only after the following questions are answered should you begin to write a detailed test plan or build a lab topology: What are the test triggers?
Who is requesting the test and what are their motives? How much testing is necessary and what constitutes success? What is the impact of test failure and what are the known risks? What are the resources people, lab equipment, and test tools required to execute the test?
As discussed in Chapter 2, "Testing Throughout the Network Lifecycle," a complimentary relationship between network testing and design functions exists in organizations that execute enterprise architecture effectively.
We explained how structured testing complements and validates design deliverables, by providing examples of the different types of test requests that you can expect throughout the network's lifecycle.
This chapter will begin to fill in the practical details of what is necessary to build an effective approach toward different types of test requests.
It begins with a suggested approach for assessing and scoping a test project, and offers guidance and best practices for the following considerations: How to identify test case scenarios How to develop a lab prototype How to choose the proper test tools necessary to execute the different types of tests How to write a detailed test plan As with most technical undertakings, there is no absolute right way to approach systems testing.
We do not promote ours as the only way to conduct successful testing. However, this is a proven method that will improve your chances of getting it right the first time.
Motivations for Different Types of Testing The first step in assessing the objective and scope of a test effort is to understand the reasons for why it was requested, and the motives of the people or organization that requested it.
In some instances, your client may be able to clearly tell you why they want testing and what they expect from testing, while others may only be able to tell you that their proposed deployment "is critical to the business and must be tested.
Following are some of the most common triggers and motivations associated with the different types of testing. Proof of Concept Testing Proof of concept POC testing is normally conducted during the Plan Phase of a new network design, or prior to the introduction of a new technology or service into an operational network.
A network architect will often request that a POC test be completed to ensure that a new product or technology will work as expected in the context of their design.
Successful POC testing is often the criteria for purchasing or moving into the low-level design LLD phase of a project, and in some cases POC testing is a mandatory milestone to be completed before purchasing approval will be granted.
In general, POC testing should be conducted systematically but persist only as long as necessary to prove that a proposed solution will work as expected. An exception to this general rule is when POC testing is used as a means to differentiate between similar products as part of a "bake-off" test.
These types of tests often require extensive scale and feature testing in order to provide the necessary data to differentiate between competing products.
Network Readiness Testing Network readiness testing is often included as part of a network assessment to determine whether a production network can meet the needs of a new application or service, and to identify any gaps that may hinder it. This type of testing is commonly conducted prior to deploying a Cisco Unified Communications UC solution, to help an enterprise determine whether its network will be able to meet the stringent requirements associated with real-time applications.
Network readiness testing for UC often involves test tool injection and measurement of synthetic application traffic across a live network to predict how the actual application will perform when network elements are running in steady-state conditions, during day-to-day operations.
Success criteria for this type of testing is easy to define because the SLA requirements with respect to delay, jitter, and loss are well understood for UC applications. Careful planning and coordination is often necessary when this type of network readiness testing is conducted so that production service disruption can be avoided.
Design Verification Testing As the name suggests, this type of testing occurs during the Design Phase of a network's lifecycle.Before you begin to write test questions, you need to determine which type of test format you are going to utilize.
The most common test formats include multiple choice questions, true or false questions, fill in the blank questions and open-ended questions. To integrate testing in a sprint, you should know the risks and use test design techniques that cover those risks, writing only useful test cases.
Tip 4: Regression Test Sets In the same context as tip 3 you can think of regression tests sets. When to test The test plan should show how the stages of the testing process, such as component, integration and acceptance, correspond to stages of the development process.
For those of us who have adopted an iterative, incremental development strategy, incremental testing is a natural fit. A clear and continuous communications plan during this process is necessary to maintain an accurate test timeline.
Once the goals, objectives, and test scenarios are clearly stated and acknowledged by the stakeholders, you should be able to define success criteria, execute the tests, deliver the results, and exit the engagement.
The validation summary report should include: A description of the validation project, including the project scope All test cases performed, including whether those test cases passed without issue.
But, if you have unit testing in place, you write the test, write the code and run the test. Writing tests takes time but the time is compensated by the less amount of time it takes to run the tests; You need not fire up the GUI and provide all those inputs.