THIRD PARTY DEVELOPMENT TESTING/WORKING WITH DEVELOPERS

Our reports become a way for you to manage your relations with an external developer. You can annotate the reports, and the developer can then annotate them as well. Here is an example of an annotated testing report.

In the first segment for the report, two items are listed and the developer has marked them "FIXED."

Operational Problems:

1. The links for Chapters 17, 18, 20, and 22 do not work. When clicked on, we get the message that "Microsoft PowerPoint Viewer Cannot open the specified file."

2. Slide 15-8 has the text, "& a few recommendation:", rather than "& a few recommendations:".

The next segment shows a few items where the publisher has marked them, "OK AS IS."

Documentation:

1. The minimum system specs are listed in the license agreement as well as the README file or User's Guide. <OK AS IS – DM>
   
   
2. The specs in the license agreement say that 800x600 is the required resolution, but this is not stated in the User's Guide. We tested the program in 640x480 and did not encounter any problems. <OK AS IS – DM>
   
   
3. There is bad pagination in the manual. Sometimes the chapter headers are placed at the bottom of the page rather than the top of the next. <FIXED>

Sometimes, there is some discussion, or some give and take between the developer, the publishers and Hudson. A table can be a good way to show what items are fixed, which ones the publisher has dropped, and what items are still open. Click to see a product check list from a complex product with a lot of back and forth. The developer has fixed some items, was unable to replicate one item, and marked others as "No change," meaning they don't agree with our report. No decision has been reached on that item by the publisher yet. The ones marked "No change per ***" are the ones where the publisher has agreed to leave the item as is.