Conflict Between the In-Box Manual and Dreamweaver

 

Summary

Dreamweaver 4's Clean Up HTML function does not operate precisely as defined in the specifications. The manual states that when performing a clean up of the HTML code, the <font> tags' attributes are all renamed as <font> , such that <font color="red"> would become <font font="red"> . The program does, however, correctly retain the code as <font color="red"> . This fault in the manual makes it difficult to distinguish whether the program or the manual is correct, and requires a user to contact technical support or verify the coding standards with the W3 organization.

Application Description

Macromedia Dreamweaver is an application for creating and maintaining websites. A demo version is available on their official website. Here is a picture of the general layout of the Dreamweaver application, with a menu showing where the Clean Up HTML function we are working with can be found:

Test Design

This example demonstrates the use of Specification-based testing (or Spec-based testing). When Spec-based testing, the tester analyzes the program's performance based on what the specifications state.

For this presentation, we have chosen a function in Dreamweaver to focus on, the Clean Up HTML function. Similarly, we could have chosen any other function simply by going through the index of the Using Dreamweaver 4 specification manual included in the Dreamweaver box.

On page 347 of the Using Dreamweaver 4 specification manual, it tells us that the Clean Up HTML function is used to:

“remove empty tags, combine nested <font> tags, and otherwise improve messy or unreadable HTML code.”

To perform this test, we will create an HTML document based on the specifications. We will then run the Clean Up HTML function and observe the changes to the HTML document. We expect that the changes to the document should be exactly the same as they are outlined on page 347 of the manual.

We expect the function to:

Performing the Test

  1. Open Dreamweaver and create a new HTML document using File->New.
  2. Select the Show Code and Design View:

  3. Paste this HTML code into the HTML document.
  4. Choose Commands->Clean Up HTML from the top horizontal menu and choose the following checked options, then click 'OK'.

  5. Compare the results with the specifications manual.

Results/Relevance

  

As we can see, Dreamweaver has made 4 changes to our HTML file. Let's compare these changes to the specifications:

In this case, we would have a very important decision to make: Do we go by the specifications? According to the specifications, the program made two errors. According to HTML 4.0 standards, however, the program performed correctly.

This is why Specification testing can be damaging to a testing environment. Often people who have had nothing to do with either the development or the testing of the product write the specifications. Similarly, specifications, especially with large programs, can be significantly out-of-date. As we can see here, the specifications did not match the functionality of the program and can lead users to be confused about how it works. The program did perform correctly, as all of the changes Dreamweaver made conform with the W3's HTML 4.0 specifications, whereas the manual did not.

Similar Tests/Additional Notes

Following this format, you can choose and test any of the functions in Dreamweaver and compare them to the manual.

Configuration Notes

Testing Macromedia's Dreamweaver v4.0 on:

Created 26 May 2004 for the CSTER

All images and written material ©Copyright Sam Oswald 2004

This work is licensed under the Creative Commons Attribution-ShareAlike License.
To view a copy of this license, visit
http://creativecommons.org/licenses/by-sa/2.0/
or send a letter to
Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305,
USA.