A test plan is a document that describes the testing strategy, objectives, schedule, resources, and deliverables for validating software quality. It helps determine the effort needed for testing. Developing a good test plan involves analyzing the product, designing a test strategy, defining objectives and criteria, planning resources and environment, and estimating schedule and deliverables.
A table of specifications is a two-way chart that describes the topics covered by a test and the number of items or points associated with each topic. It ensures a fair and representative sample of questions and allows the teacher to focus on key areas based on importance. Developing a table involves choosing measurement goals and domains, breaking domains into independent concepts and procedures, and constructing the table.
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
396 views
Lesson 4 - Planning A Written Test
A test plan is a document that describes the testing strategy, objectives, schedule, resources, and deliverables for validating software quality. It helps determine the effort needed for testing. Developing a good test plan involves analyzing the product, designing a test strategy, defining objectives and criteria, planning resources and environment, and estimating schedule and deliverables.
A table of specifications is a two-way chart that describes the topics covered by a test and the number of items or points associated with each topic. It ensures a fair and representative sample of questions and allows the teacher to focus on key areas based on importance. Developing a table involves choosing measurement goals and domains, breaking domains into independent concepts and procedures, and constructing the table.
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
Chapter II: Development and Administration of Test
LESSON 4: PLANNING A WRITTEN TEST
Planning a Written Test
A Test Plan is a detailed document that describes the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform testing for a software product. Test Plan helps us determine the effort needed to validate the quality of the application under test.
The following things make us write a good test plan:
Product Analysing. Design the Test Strategy Define the Test Objectives. Define Test Criteria. Resource Planning. Plan Test Environment. Schedule & Estimation. Determine Test deliverables.
WHY DO WE NEED TO DEFINE THE TEST OBJECTIVES OR LEARNING
OUTCOMES TARGETED FOR ASSESSMENT? Let’s student set learning goals easily and helps students learn more effectively. Instructors have a clear direction while making assessment decisions, gives a program level overview of learning across courses and years.
WHAT ARE THE OBJECTIVES FOR TESTING?
The overall goal of each assessment is to get a better understanding of the candidates. This can be obtained by testing how a person responds and performs in different situations. The assessment type that is used most frequently is the selection assessment.
WHAT IS A TABLE OF SPECIFICATION?
A Table of Specifications is a two-way chart which describes the topics to be covered by a test and the number of items or points which will be associated with each topic. Sometimes the types of items are described, as well. The purpose of a Table of Specifications is to identify the achievement domains being measured and to ensure that a fair and representative sample of questions appear on the test. Teachers cannot measure every topic or objective and cannot ask every question they might wish to ask. A Table of Specifications allows the teacher to construct a test which focuses on the key areas and weights those different areas based on their importance. A Table of Specifications provides the teacher with evidence that a test has content validity, that it covers what should be covered.
WHAT ARE THE GENERAL STEPS IN DEVELOPING A TABLE OF
SPECIFICATION? Tables of Specification typically are designed based on the list of course objectives, the topics covered in class, the amount of time spent on those topics, textbook chapter topics, and the emphasis and space provided in the text. In some cases a great weight will be assigned to a concept that is extremely important, even if relatively little class time was spent on the topic. Three steps are involved in creating a Table of Specifications: 1) choosing the measurement goals and domain to be covered, 2) breaking the domain into key or fairly independent parts- concepts, terms, procedures, applications, and 3) constructing the table.