Developing Software Testers
Peer Review for material titled "Developing Software Testers"
User Rating for material titled "Developing Software Testers"
Member Comments for material titled "Developing Software Testers"
Personal Collections for material titled "Developing Software Testers"
Learning Exercises for material titled "Developing Software Testers"
Accessibility Info for material titled "Developing Software Testers"
Search all MERLOT
Click here to go to your profile
Select to go to your workspace
Click here to go to your Dashboard Report
Click here to go to your Content Builder
Click here to log out
Search Terms
Enter username
Enter password
Please give at least one keyword of at least three characters for the search to work with. The more keywords you give, the better the search will work for you.
select OK to launch help window
cancel help

MERLOT II




        

Search > Material Results >

Developing Software Testers

        

Developing Software Testers

Logo for Developing Software Testers
High level strategy/approach document on how to prepare individuals to test software.Outlines major objectives and goals that can lead to quality software, through a standard and systematic approach.  Presented as a learning exercise with instructional goals and methods to evaluate what was learned. This is a class assignment for MSU Education Technology degree.
Material Type: Assignment
Technical Format: PDF
Date Added to MERLOT: January 28, 2012
Date Modified in MERLOT: March 08, 2012
Submitter: Brian Jenks
Keywords: software testing, New software testers, standard approach to software testing

Quality

  • Reviewed by members of Editorial board for inclusion in MERLOT.
    Editor Review
    Very good quality; in queue to be peer reviewed
    avg: 5 rating
  • User review 3.67 average rating
  • User Rating: 3.67 user rating
  • Discussion (3 Comments)
  • Learning Exercises (none)
  • Personal Collections (none)
  • Accessibility Info (none)

About

Primary Audience: College General Ed, College Lower Division, College Upper Division, Graduate School
Mobile Compatibility: Not specified at this time
Technical Requirements: Windows or Mac Operating System; Adobe Reader
Language: English
Cost Involved: no
Source Code Available: unsure
Accessiblity Information Available: no
Creative Commons: no

Connections





QR Code for this Page

Browse in Categories

Discussion

Discussion for Developing Software Testers

Log in to participate in the discussions or Register if you are not already a MERLOT member.

Return to Top of Page
Avatar for Bob Carl
2 years ago

Bob Carl (Student)

This lesson is definitely for a mature audience, but could be used in a secondary setting as well. As far as technology integration, students could use a collaborative means of documenting their results, ensuring they are not duplicating multiple tasks and sharing their finding with their classmates. They could also break down the software and test by sense – what do they hear (or not hear), what do they see (or not see) and is the software able to work with the disabled. Is the software compatible with devices for the disabled? Very good lesson and professionally done!

Time spent reviewing site: 20 minutes

Avatar for Lisa Joseph
2 years ago

Lisa Joseph (Teacher (K-12))

This lesson is definitely for a more mature computer user, and, as the stated, is not for use in a K-12 setting. Some of the content is hard to follow if you do not understand the role of software testing. Would like to know how testers record their findings. Is it documented on a shared document for others to view? It is a little confusing to the layman, but the audience is clearly stated, and I'm sure valuable for those who must evaluate new software.

Time spent reviewing site: 25 minutes

Avatar for Elise Fiechtner
2 years ago

Elise Fiechtner (Teacher (K-12))

This is a great lesson for software testers.  It make so much sense to have everyone on the same page, follwoing the same procedures.  This lesson is important for a department that will actually be required to deal with real issues.

Technical Remarks:

Everything worked well.

Time spent reviewing site: 15 minutes