This is a school assignment outlining objectives for software testers, providing short answers to directed questions. The subject matter includes the identification of a need, learning and instructional objectives, critical thinking skills, evaluations, methods, motivation, audience, and technology needs from a developer's point of view.
It's a three page PDF document that can be used as a supplement in a classroom setting.
Type of Material:
Stand alone assignment.
As a handout for an introductory level software testing class.
As a handout for a CE course in software development.
Adobe Acrobat Reader, Internet browser.
Identify Major Learning Goals:
a. Using existing software design requirements, testers learn to create detailed test scripts that describe each test step, and the expected result(s).
b. Testers record their software results, and understand where information is saved for future review.
c. Testers learn how to accurately and efficiently identify, report and retest software defects.
d. Each involved test team member understands what needs to be accomplished and completed before approval can be granted on their tested software.
Identify the target audience.
Target Student Population:
Upper college level, working professionals, beginning graduate students (there isn't much technical jargon).
Prerequisite Knowledge or Skills:
Understanding of computers and operating systems, web browsers, and other software used to interface/access business data and content.
Some background in usability testing/software development; basic understanding of project management.
The document thoroughly covers the attributes of good software testers. It's very straightforward and parts of it can be used even for professional work.
The document should be updated (some references to the Windows system (XP), are dated; Opera isn't the most common browser but it's used and should be listed.
The assignment isn't wrapped around a learning module.It would be more helpful if it's used in a context of a complete tutorial on basic software testing, for example, or a usability course.
It would help to include a sample flowchart for software testing.
Potential Effectiveness as a Teaching Tool
The document is a starting point for a software tester and can be used in a classroom discussion.
The material would be more helpful if it's part of a learning module, if the author adds examples and resources. Otherwise, it's too limited for broad use.
Ease of Use for Both Students and Faculty
PDFs are easy to upload, send, share, or print.
Please add a set of questions/additional discussion topics. Please include examples, case studies, and resources.
Other Issues and Comments:
Overall this is a good start at preparing materials. Consistency in delivery, uniqueness of information (instead of including the professor's questions), and adequate details could be added, along with questions or a quiz for better classroom or self-use.
This standalone document can be updated with resources (links), interactive activities, debriefings after an assignment is complete, and case studies.
It's a minor point but the formatting could be streamlined (different bullets distract from the content).
Search by ISBN?
It looks like you have entered an ISBN number. Would you like to search using what you have
entered as an ISBN number?
Searching for Members?
You entered an email address. Would you like to search for members? Click Yes to continue. If no, materials will be displayed first. You can refine your search with the options on the left of the results page.