Microsoft Dynamics GP 10.0 ISV Software Solution Test Guidelines

Microsoft Dynamics GP 10.0
Microsoft Dynamics ISV Software Solution Test Guidelines

May 16, 2007

Table of Contents:

Introduction
This Document
Program Overview 
Contents of the Test Guidelines 
Products Versions Supported 
Types of Solutions 
Retesting 
More Information

Testing Process 

Documentation Requirements
First-Time Software Test Requirements
Software Retest Requirements

ISV Software Solution Requirements and Recommendations
Development Requirements 
1.1 A Managed Code ISV Application Must Be Compiled on .NET Framework 2.0 or Later and Must Pass the Required FxCop Tests .13
1.2 Managed Assemblies Must Be Strong Named
1.3 ActiveX Controls Should Be Digitally Signed
1.4 An ISV Application Should Make its Version Information Available 15
User Assistance and Documentation Requirements
2.1 An ISV Application Must Include Online Help
2.2 The ISV Must Provide an Implementation Guide
2.3 Online Documentation for an ISV Application Should Follow the Style Guidelines in the Microsoft Dynamics GP Integration Guide
User Experience and Usability Requirements 
3.1 A Dexterity-based ISV Application Must Comply With Microsoft Dynamics GP UI Guidelines
3.2 If an ISV Application Restricts the Functionality of Microsoft Dynamics GP, the ISV Must Document the Limitation
Trustworthy Computing Requirements
4.1 A Dexterity-based Application Must Handle Security for Alternate Windows and Reports Correctly
4.2 A Dexterity-based Application Must Not Produce Errors if Security to Alternate Windows Is Not Granted
4.3 A Dexterity-based ISV Application Should Protect Sensitive or Hidden Windows From Being Opened by Shortcuts
4.4 A Dexterity-based ISV Application Should Use the System Password to Protect Sensitive Areas
Technology Configurations and Platform Requirements
5.1 An ISV Application Must Support the Infrastructure That Microsoft Dynamics GP Supports
Setup Requirements
6.1 The ISV Application Must Include Documented Installation Procedures
6.2 The ISV Application Installation Procedure Must Correctly Register DLLs and COM Components
6.3 The ISV Must Document the Required Version and Service Pack of All Dependent Software Programs, Including Microsoft Dynamics GP, for Their Application Installation
6.4 The ISV Must Document the Microsoft Dynamics GP Components Required for Application Installation
6.5 The ISV Application Must Provide Uninstall Procedures, and Uninstalling the Application Must Not Adversely Affect Microsoft Dynamics GP
6.6 The ISV Application Must Include Installable Demonstration Data
6.7 The ISV Application Must Not Adversely Affect Microsoft Dynamics GP After the ISV Application Is Installed
6.8 A Dexterity-based ISV Application Must Use a Chunk File for Installation
6.9 A Dexterity-based ISV Application Must Not Produce Errors if the Database Objects Are Not Installed
6.10 A Dexterity-based ISV Application Must Install Database Objects Automatically
6.11 A Dexterity-based ISV Application Must Install Navigation Automatically
6.12 A Dexterity-based ISV Application Must Install Pathnames Automatically for tables in the 3rd Party Series
6.13 A Dexterity-based ISV Application Must Have a Product ID Assigned by Microsoft Sales Operations
Backup and Restore
7.1 The ISV Must Include Procedures to Back Up and Restore the ISV Application and the Data If Standard Microsoft Dynamics GP Backup Is Insufficient
Extensibility and Customization Requirements 
8.1 The ISV Should Document Its Application Extensibility and Customization Strategy
Upgrade and Maintenance 
9.1 The ISV Must Provide Database Upgrade Scripts
9.2 The ISV Must Use File Versioning for DLLs and COM Components

Best Practice Guidelines 

Design Best Practices
1.1 All ISVs Should Follow Microsoft Dynamics GP Architectural Guidelines
Trustworthy Computing Best Practices
2.1 ISV Application Development Staff Should Complete Security and Security Development Life Cycle (SDL) Training
2.2 The ISV Application Should Not Bypass the Microsoft Dynamics GP Standard Security Model
Development Best Practices
3.1 A Dexterity-based ISV Application Should Minimize the Use of Alternate Windows and Reports
3.2 A Dexterity-based ISV Application Should Register Its Triggers With the Startup Procedure
3.3 A Dexterity-based ISV Application Should Use Dexterity Source Code Control and Should Update the Index File
3.4 A Dexterity-based ISV Application Should Use a Macro to Create the Chunk File
3.5 A Dexterity-based ISV Application Should Follow the Microsoft Dynamics GP Naming Conventions
Reporting Best Practices
4.1 An ISV Application Should Follow the Microsoft Dynamics GP Reporting Guidelines
Translation and Localization Best Practices
5.1 A Dexterity-based Application Should Separate Strings From Source Code
5.2 A Dexterity-based ISV Application Should Follow Best Practices for Writing International Code
5.3 A Dexterity-based ISV Application Should Follow Best Practices for Writing Multi-Lingual Code