Material Detail

Developing Software Testers

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.

Rate

Quality

More about this material

Comments

Log in to participate in the discussions or sign up if you are not already a MERLOT member.
Bob Carl
Bob Carl (Student)
6 years ago

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
Lisa Joseph
Lisa Joseph (Teacher (K-12))
6 years ago

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
Elise Fiechtner
Elise Fiechtner (Teacher (K-12))
6 years ago

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