Accessibility

Functionality Standards for Fireworks Extensions

This document contains the minimum set of functionality guidelines used by the Fireworks team when testing a Fireworks extension for Macromedia approval. To obtain Macromedia approval an extension must adhere to this set of standards in addition to the basic requirements and style guidelines.

Test Plan

The following testing guidelines help you debug your extensions. Although you may not have access to both a Macintosh and a Windows system, please follow as much of the test plan as you can. Always perform the installation and compatibility tests, no matter what kind of extension you're testing.

Be sure to test your extension in a variety of scenarios. It may work in exactly the case it was designed for but fail miserably in another case. Due to the scope and variety of possible extensions, this test plan does not thoroughly cover every way in which an extension can be tested, nor does it necessarily reflect the testing process that is performed at Macromedia. Treat this plan as a starting point, a minimum standard that your extension should be able to pass, and perform further tests as appropriate.

After you submit your extension to Macromedia for certification, it will be further tested by the Fireworks Quality Assurance (QA) team.

QA will send you a list of any problems encountered; you can then fix the problems and resubmit the extension. However, you're expected to do thorough testing before submitting the extension; don't rely on Macromedia to do all your testing.

After you perform the steps listed in Preparing to test and Testing installation, follow the appropriate test plan for your extension's type:

Testing asset extensions
Testing commands

In addition to the test plans for asset extensions and commands, if your extension has a SWF movie user interface, you must perform one of the test plans listed below. Follow the appropriate test plan for your extension type.

Testing SWF Movie dialog extensions
Testing SWF Movie floating panel extensions

Preparing to test

After completing an extension or fixing a bug, follow these steps to prepare to test your extension:

  1. Install the extension in either of the following ways:
    • Use the Extension Manager.
    • Place the files in the appropriate subfolder in the Macromedia Fireworks MX folder.
  2. Quit and restart Fireworks if you installed without the Extension Manager, or if prompted to do so by the Extension Manager.

Testing installation

To make sure that you can install your extension on all platforms, perform these tests for all extensions:

  1. Install on both Macintosh and Windows.
  2. Verify that the installation works correctly when installing while Fireworks is running:
    • If the extension is an asset extension or a SWF movie floating panel extension, the Extension Manager should prompt the user to restart Fireworks before the functionality becomes available.
    • If the extension is a JSF command or a simple SWF command or SWF movie dialog, the Extension Manager should not prompt the user to restart Fireworks.
  3. Verify that the installation worked correctly:
    • Make sure all files, including Help files (if any), are installed in proper folders, and that they show up in the Fireworks user interface, if applicable.
  4. Run virus-checking software to verify lack of infection before and after using the extension.

Testing Asset Extensions

Perform these tests if your extension is an asset extension such as a Style, Texture, Pattern, Library, or Dictionary.

  1. Launch Fireworks and go to the location where the extension is accessed in the Fireworks user interface ( i.e. if it is a style go to the Styles panel, if it is a dictionary, go to the Spelling settings dialog, etc.).
  2. Make sure the asset has been added to the user interface and has not disturbed the original Fireworks user interface.
  3. Use the asset within Fireworks and make sure that it behaves as expected (e.g., if it is a texture, apply it to the fill of an object, if it is a button library, use the button in a document).
  4. Now uninstall the extension from Fireworks.
    • Make sure that when the extension is uninstalled from the application, the asset is removed from the Fireworks user interface and that the Fireworks user interface returns to its original state.
    • Make sure all files that were installed with the extension have been removed from the application folder.

Testing Commands

Perform these tests if your extension is a JSF command or a SWF movie command:

  1. Launch Fireworks. Do not create or open a document.
  2. Try to run the command with no document open.
    • Make sure that no javascript errors are generated when the command is run without a document open.
    • Make sure that appropriate error dialogs appear informing the user that a document must be open to run the command.
  3. Now create a new document or open an existing document. Try to run the command with no selection made.
    • If the command requires a selection, make sure that no javascript errors are generated when the command is run without a selection made.
    • If the command requires a selection, make sure that the appropriate error dialogs appear informing the user that a selection must be made.
    • If the command does not require a selection, make sure that the command behaves as expected.
  4. If the command requires a selection, apply the command to the different types of selections (e.g., vector paths, groups, hotspots, slices, bitmap selections, masks). Make sure that the command behaves as expected with each type of selection.
  5. Now uninstall the extension from Fireworks.
    • Make sure that when the extension is uninstalled from the application, the command is removed from the Fireworks Commands menu.
    • Make sure all files that were installed with the extension have been removed from the application folder.

Testing SWF Movie Dialog Extensions

Perform these tests if your extension is a command that has a SWF movie dialog user interface:

  1. Make sure that the SWF window opens to the correct size to display the movie.
  2. Verify that the command name appears in the title bar.
  3. Make sure that the SWF movie window cannot be resized.
  4. Right mouse click on the SWF movie window. Verify that the standard SWF context-sensitive menu is disabled.
  5. Verify that you can run the command from the Run Script menu item found in the Commands menu.
  6. Verify that you can add and use shortcuts to the commands through the keyboard shortcuts dialog.
  7. Verify all spelling and grammar for the text that is visible to the user.
  8. Verify that all controls in the dialog work as expected.
  9. Verify that you can copy from and paste to all value fields in the dialog.
  10. Verify that the value fields accept only valid entries that are relative to their functionality (e.g., numbers, letters, numbers & letters, all text characters).
    • Make sure that if a user does enter invalid characters into a value field, the error handling is understandable to the user (i.e., the invalid characters should not be accepted, the invalid characters should be changed to valid characters, or appropriate error dialogs should tell the user of the invalid character entry).
  11. Make sure that clicking the Apply or OK button applies the command as expected.
  12. Make sure that clicking on the Cancel button closes the dialog without applying the command.
  13. On Windows make sure that the close box in the SWF title bar closes the movie without applying the command.

Testing SWF Movie Panel Extensions

Perform these tests if your extension is a command that is a SWF movie floating panel:

  1. Verify that the command panel can be launched from the Windows menu.
  2. Make sure that the SWF panel opens to the correct size to display the movie.
  3. Verify that the command name appears in the title bar of the panel.
  4. Make sure that the SWF movie window cannot be resized.
  5. Right mouse click on the SWF movie window. Verify that the standard SWF context-sensitive menu is disabled.
  6. Verify that you can add and use shortcuts to the commands through the keyboard shortcuts dialog.
  7. Verify the spelling and grammar for the text that is visible to the user.
  8. Verify that all controls in the panel work as expected, whether the panel is docked or undocked.
  9. Verify that you can copy from and paste to all value fields in the dialog.
  10. Verify that the value fields accept only valid entries that are relative to its functionality (e.g., numbers, letters, numbers & letters, all text characters).
    • Make sure that if a user does enter invalid characters into a value field, the error handling is understandable to the user (i.e., the invalid characters should not be accepted, the invalid characters should be changed to valid characters, or appropriate error dialogs should tell the user of the invalid character entry).
  11. On Windows make sure that the close box in the SWF title bar closes the movie without applying the command.