Microsoft Dynamics NAV 2009
Microsoft Dynamics ISV Software Solution Test Guidelines
Version 1.0
December 1, 2008
Table of Contents
Introduction
Program Overview
Supported Products Versions
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 and Recommendations
1.1 The ISV solution with managed code must be compiled with the .NET Framework 2.0 or later and must pass the required FxCop tests
1.2 Managed assemblies must be strongly named
1.3 New application objects must use their assigned number range
1.4 The ISV solution must follow standard Microsoft Dynamics NAV version conventions and provide code comments for changed Microsoft Dynamics NAV objects
1.5 Code that calls Web services must access Microsoft Dynamics NAV under the user account of the end user
1.6 Pages and codeunits that are designed to be exposed as Web services must not generate any UI that would cause an exception in the calling code
1.7 Automation objects that run on Microsoft Dynamics NAV Server must not generate any UI
1.8 ActiveX controls should be digitally signed
1.9 The ISV solution should make its version information available.
User Assistance and Product Documentation Requirements and Recommendations
2.1 An ISV solution must include Help that is targeted to the solution user
2.2 The ISV must provide an installation and configuration guide
2.3 ISV solution Help should follow the style guidelines that are described in the Microsoft Dynamics NAV Help Guide.
User Experience Requirements
3.1 The ISV solution must comply with core Windows and Microsoft Dynamics NAV 2009 user experience guidelines
3.2 The ISV solution that restricts the functionality of Microsoft Dynamics NAV must document the restriction
Translation and Localization Requirement
4.1 The ISV solution must separate strings from source code
Technology Configuration and Platform Requirement
5.1 The ISV solution must support the infrastructure that Microsoft Dynamics NAV supports
Installation and Setup Requirements and Recommendations
6.1 The ISV solution installation procedure must be compatible with Microsoft Dynamics NAV
6.2 The ISV solution must correctly register DLLs and COM components.
6.3 The ISV solution must correctly deploy COM components to Microsoft Dynamics NAV Server and to client machines.
6.4 After the ISV solution is installed, the Microsoft Dynamics NAV database must compile without errors.
6.5 The ISV must document the required versions and service packs of all dependent software programs, including Microsoft Dynamics NAV.
6.6 The ISV must document the Microsoft Dynamics NAV license that is required for their application installation.
6.7 The ISV must document the uninstallation procedures.
6.8 The ISV solution must include installable demonstration data.
6.9 Microsoft Dynamics NAV must start without errors after the ISV solution is installed.
6.10 The ISV solution should use the Rapid Implementation Methodology (RIM) to increase setup speed.
Backup and Restore Requirement
7.1 The ISV must include procedures to back up and restore the ISV solution and data if the standard Microsoft Dynamics NAV backup process is insufficient.
Extensibility and Customization Recommendation
8.1 ISVs should document their application extensibility and customization strategy.
Upgrade and Maintenance Requirements
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 and Development Best Practices
1.1 The ISV should follow Microsoft Dynamics NAV architectural guidelines.
1.2 The ISV solution should follow reporting guidelines.
1.3 The ISV solution should follow best practices for Web services.
1.4 The ISV solution should not produce best practice tool errors.
User Experience Best Practices
2.1 The ISV solution should follow additional Microsoft Dynamics NAV 2009 user experience guidelines.
Trustworthy Computing Best Practices
2.1 ISV development staff should complete security and Security Development Lifecycle training.
2.2 The ISV solution should not bypass the standard Microsoft Dynamics NAV security model
Appendix A: User Experience Requirements
Appendix B: Microsoft Dynamics NAV Consistency Verification Test
Appendix C: Standard Microsoft Dynamics NAV Version Conventions
Standard Object Version Convention
Standard Object With Local Functionality Modifications Version Convention
Local Functionality Object Version Convention
ISV Object Version Convention