10b, c, d & 8c
Summative testing
The minister's wife has turned out to be very computer literate. She was able to perform complete, systematic summative testing of the completed product. This meant that I could concentrate on the more technically rigourous testing that was required by the functional specification. The combined effort of mine and her work has been sufficient to ensure that the multimedia product works as intended.
User tester
I gave her the product on a CD-ROM so she could browse through it at home in her usual surroundings, no doubt the minister himself had a look. She found the following mistakes and listed them on some note-paper and handed them to the following day. Because these were simple problems such as "bad links" and errors more obvious to the user they were valuable findings yet, at the same time, very easy to resolve. She also gave me very good overall feedback and suggested a good future improvement (a contact form). I will discuss this feedback more fully in my evaluation.
My testing
Below is a list of the testing tasks I carried out:
- W3C XHTML Validation for each page
- W3C CSS Validation
- JavaScript function testing
- Adobe Flash XML-based slideshow testing
- Podcast testing
The XHTML Validation was the first and the longest of all four tests. I used the official w3.org validator to make sure that every page was valid XHTML. This ensures that the multimedia product will function correctly on any internet browser available - thus meeting the functional requirements. Below is a screenshot of this:
The CSS validation contained a number of errors. These were quickly resolved as the majority of them were left-over defunct attributes. Below is a screenshot of the errors before they were resolved.
The JavaScript for injecting the verse of scripture, the Flash XML slideshow and the "HWEC Local Links" navigational list was tested on two different Linux distributions: Fedora Core 6 and Ubuntu 7.04. Both worked. This is because JavaScript is built-in to all decent web browsers. The exception being the text only browser Lynx which is not 'multimedia' compatible as it's name implies. This is not of much concern to us in this "multimedia" unit, however is still appears logical - meeting the functional specification's testing requirements.
The two audio files contained within version 3.0 were tested on three seperate machines. The podcasting solution using iTunes was also a success. The link automatically opened iTunes and navigated the iTunes Store to find the HWEC Sermons podcast pictured below:
The thorough testing I have performed of the multimedia product ensures that it works as intended.
« BACK | Back to top | NEXT »
