Open Software Testing Labs

Testimonials/feedback by educators and students who have used the courseware

Testimonials of the educators who have used the courseware:

"It's a really a very good set of exercises. The coursework is very interesting and very easy for the students to start with. Thanks a lot for letting us use them."

Dr. Rashid Ahmad, National University of Sciences and Technology, Pakistan, July 2011

"It's a really serious and realistic set of exercises. Thanks for letting me use them. My students are enjoying them."

Natalia Silvis-Cividjian, University of Vrije, Netherlands, June 2011

"At Aalborg University[, Denmark], we used four of the coursework parts for exercise sessions following four relevant lectures in the testing part of a course on Testing and Verification. The coursework is detailed in its instructions and thus easy for the students to start working with. The students generally like the step by step instructions and the hands-on experience that the exercises give."

Ulrik Nyman, Assistant Professor, Department of Computer Science, Aalborg University, Denmark, May 2011

Testimonials of students who have learnt using the courseware

Selected feedbacks from the students of the course Software Testing (SENG 437) course, University of Calgary, in Winter 2010:

Feedbacks on Lab 1:
I think this lab was helpful to get started with testing of software. Also, the first type testing we did was ad-hoc testing which is what we are familiar to, so it is easy to get the head around. And for the manual functional testing also he gave us all possible cases, so that is really nice way to get us started and make us understand that how we should do the testing for the next assignments. Even for the bug reporting tool, there was a trial test product ready to fool around before we start on the assignment. That is what I really like that get familiar and then work towards the assignment.
The lab was a nice introduction into different testing strategies.Overall I am very happy with the way this lab has turned out. I learned a lot, both about teamwork, working in general, and software testing, and look forward to the next lab and assignment.
The lab was very well organized and thought out. I found the instructions fairly easy to follow and it provided an interesting way to practice writing defect reports and hunting for bugs.I felt like I gained so much by first writing my bug reports and then critiquing someone else’s. Receiving criticism on my bug reports was also very helpful. Overall all I felt that the lab was a very helpful tool in introducing me to the different testing methods.It provided a well encapsulated introduction to defect tracking that is easy to extrapolate for larger scale software systems. This lab was a very good introduction to some different strategies for testing software and to reporting defects in a proper way.
Feedbacks on Lab 2:
This lab was fun. It took advantage of methods that threw unusual exceptions which we could not allowto bubble up to the system level. It made us do real black-box testing because we could not access the source code, expect by reversing the byte-code, which we did not do. It strengthened our teamwork skills and our ability to delegate tasks and commit to deadlines. In all, it was a good real-world experience and we can use this as an example when interviewing for employment.
The lab was easy to follow, and the expectations were straightforward. The instructions introducing test project setup were clear and helpful. We like how every detail to start the lab was provided and how the lab document walked through the sample test creation. Screen shots were helpful in confirming the steps of the lab.
This lab was a great way to introduce JUnit and Javadoc for those who are not extremely familiar with it. The instructions were very straight forward and easy to follow and it did a great job explaining how to use JUnit. The lab itself was a great way to get us in the mind set of testing because we are not able to see the code itself.
Feedbacks on Lab 3:
At a recent presentation with Smart Technologies, X asked them how many people, what percent of the budget, and what software testing paradigm do they use. The representative, who is a coder, said, “Um, we have a guy who does that.” These labs are definitely going to help us in industry.
We gain experience in using two different types of testing tools and gained appreciation in doing good testing.
The calculation part is a good way to apply what we have been doing in the lectures and practicing here.
Feedbacks on Lab 4:
The lab was a nice look at how GUI testing can be carried out effectively, while still using elements of our non-GUI-specific testing knowledge.It was good to see a new testing tool, especially an automated GUI tester because we haven’t worked with one before.
Feedbacks on Lab 5:
This was a fun lab to end the course off with. The previous lab was difficult and error prone, but this lab gave us experience with a testing ability that we can bring to the table when search for employment. Before this course we had not heard of mutation testing. Thank you for this experience.
Overall we both learned a lot from this lab. We encountered some difficulties, mostly with getting Eclipse working, however we overcame all the challenges we came across.
We learned a lot from this laboratory, however there were a few things that were most important. The biggest obstacle to mutation testing is getting high mutation score accuracy. This is due to the presence of equivalence mutants. These affect the mutation score negatively, and the accuracy of the score becomes very poor. Mutation testing seems like a valuable testing tool to learn about, however for it to be truly effective, a more efficient testing tool, that does not take excessively long to run should be used.

Page updated

Google Sites

Report abuse