Ana səhifə

Isv software Test


Yüklə 253 Kb.
tarix18.07.2016
ölçüsü253 Kb.



ISV Software Test

Preliminary documentation

October 27th 2010

This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. 

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.  Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only.  MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user.  Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

 

© 2010 Microsoft Corporation.  All rights reserved.



Contents

Introduction 4

Procedure to take the test 4



Test Requirements verified by the Microsoft Platform Ready Tool 5

Component Categories 5

CRM Components 6

Components installed outside of the CRM Framework 8




Introduction


The Microsoft Dynamics CRM ISV software tests ensure that ISV applications work with Microsoft Dynamics CRM without causing system problems or errors upon installation/uninstallation of the software. The test does not validate the correctness or relevance of ISV application functionality.

Passing this software test is one of the requirements to get the Certified for Microsoft Dynamics CRM logo. Additional requirements exist to validate the credibility of the ISV and the relevance of the application. For a full list of requirements and benefits of certification consult the Certified for Microsoft Dynamics information page.



For technical information about CRM extensibility consult the CRM SDK at http://www.crm2011beta.com (Developer section)

Procedure to take the test


All the test cases described in this document are part of the Microsoft Platform Ready self-assessment tool. Register your application and download the self-assessment tool at: http://www.microsoftplatformready.com beginning November 2010. The tool will guide you to the series of steps necessary to test your application and submit results to Microsoft.



Figure 1. Microsoft Platform Ready Tool

Note: The next sections of this document are for information purposes only; they describe the requirements tested by the Microsoft Platform Ready tool.

Test Requirements verified by the Microsoft Platform Ready Tool


ISV applications must be designed to work with Microsoft Dynamics CRM 2011 Online which also ensures compatibility with Microsoft Dynamics CRM 2011 On-Premises. The Microsoft Platform Ready tool will verify that applications that install CRM components do so in a CRM online environment.

Note: Microsoft Dynamics CRM 2011 can also be hosted by a 3rd party and it is responsibility of each hosting vendor to define their own testing programs for solutions that they will allow to host.

Component Categories


Solutions built for Microsoft Dynamics CRM can have different types of components that generally fall into two broad categories: CRM components and External components. It is important to understand each component type as the tool will perform different test accordingly.

CRM Components


  • Built using Microsoft Dynamics CRM Tools/Interfaces

  • Hosted inside the CRM Framework

  • Run inside the CRM Framework

  • Deployed as a CRM solution

  • Valid CRM components are:

    • Data model:

    • Modifications to the CRM User interface

      • Ribbon

      • Forms

      • Sitemap

    • Web Resources such as images, html pages, JScript libraries Analytics

      • Dashboards

      • Charts

      • SRS Reports

    • Processes and code

      • Workflow definitions

      • Dialog definitions

      • Custom plug-in or workflow assemblies

    • Other

      • Translations


External components


  • Built using Microsoft or third party technologies

  • Interact with CRM using published interfaces (SDK)

  • Hosted outside of the CRM Framework

  • Run outside of the CRM Framework

  • Examples:

    • .Net clients

    • Windows Phone clients

    • Web Applications (e.g. Portals)

    • Web Services

The Microsoft Platform Ready test for Microsoft Dynamics CRM will only test that external components interact with CRM using public interfaces. It is responsibility of the ISV to run any additional tests applicable to the technologies that they are employing as outlined in requirement 1.5

Note: External components must work with Microsoft Dynamics CRM Online (through the SDK) and it is responsibility of the ISV to provide hosting of the component (E.g. hosting a portal on behalf of the customer) or corresponding instructions to install/host the component.

The following sections outline the test performed on each component category.


CRM Components

    1. Solution packages have a valid structure, schema and successfully install into CRM

Summary and Intent

All solution packages (.zip) should have a valid directory/file structure and the content of the customization files should conform to the Microsoft Dynamics CRM schema (XSD). The package shall install successfully into the CRM server
How to Comply

  • Do not make any manual modifications to the XML documents generated by Dynamics CRM that would make XSD validation fail. The only nodes that are allowed to be manually modified are:

    • Sitemap

    • RibbonDiffXml

    • Form Navigation
Test Methodology

For applications that provide their own installer (e.g. MSI) the tool will ask ISVs to

  • Install the application using the ISV supplied installer into a clean Microsoft Dynamics CRM 2011 Online organization.

For application that provide solution packages directly the tool will ask to

  • Import the solution package into a clean Microsoft Dynamics CRM 2011 Online organization

  • During installation the system will automatically validate the package.
Criteria for Passing

The tool will verify that the solution(s) package(s) imported successfully into a clean Microsoft Dynamics CRM organization without reporting any file or schema errors.

    1. Application shall uninstall successfully

Summary and Intent

It is highly recommendable that solutions are distributed as “managed” solution which will allow the CRM platform to properly install it, track it and if necessary, uninstall it as an individual piece of software. If the solution is distributed as unmanaged packages or it contains components hosted outside of CRM it is responsibility of the ISV to provide an uninstallation program.
How to Comply

  • Ensure that the application installs into a clean CRM5 environment

  • Ensure that the application uninstalls properly

  • If multiple solutions from the same vendor are meant to coexist into a single organization ensure that all of them install and uninstall appropriately.
Test Methodology

For applications that provide their own installer (e.g. MSI) the tool will ask ISVs to:

  • Run the ISV uninstaller. Verify that the application uninstalled successfully.

For applications that provide solution packages(.zip) the tool will ask ISVs to:

  • Uninstall the solution, uninstall should complete successfully.


Criteria for Passing

The tool will verify that the solution uninstalled successfully without reporting any errors or warning.

    1. Solution Packages contain appropriate solution information and publisher contact information

Summary and Intent

Ensure that all solutions have all required information fields filled in. The information allows users to identify the characteristics of the solution as well as the solution author.
How to Comply

Ensure that the following fields are properly filled in for your solution:

  • Display Name

  • Unique Name

  • Version

  • Description

Ensure that the following fields are properly filled in for the solution publisher

  • Display/Friendly Name

  • Unique Name

  • Description

  • All contact information fields

    • Phone

    • E-mail

    • Web Site

    • Street 1

    • Zip/Postal Code

    • Country/Region

    • State/Province
Test Methodology

The tool will ask the ISV to import the solution package and or run the corresponding installer. The tool will then verify that the solution installed successfully and ensure that the solution and publisher information is recorded in CRM.
Criteria for Passing

The tool will verity that the solution as well as the solution publisher records contain all fields filled in. Contact information provided (e.g. e-mail, telephone, web site address) must be valid and verifiable information.

    1. Client side script uses published APIs to interact with CRM UI components

Summary and Intent

Any customizations that don’t use APIs published in the SDK will likely break when Microsoft Dynamics CRM is upgraded to the next major version. Directly modifying the Document Object Model (DOM) of CRM UI components can destabilize the application and/or completely break it.
How to Comply

  • Always store all Jscript code as a CRM Web Resource and load it using native facilities provided by CRM

  • Always namespace your functions

  • Do not directly access or modify the Document Object Model (DOM) of any CRM UI component/control.

  • Always use client side APIs published in the SDK to interact with CRM components.

  • Always namespace functions in your Jscript libraries to prevent collisions with other vendors.

For more information see the Microsoft CRM SDK
Test Methodology

  • The ISV will attest on the test tool that to the best of his/her knowledge no unsupported calls are used (e.g. no direct manipulation of the DOM).


Components installed outside of the CRM Framework



    1. Components that use additional Microsoft Technologies need to pass corresponding MPR tests.

Summary and Intent

Components hosted outside of the CRM framework that interact with CRM via published APIs need to pass corresponding tests of applicable technologies. For example, a Windows Phone application needs to pass the corresponding Windows Phone tests.
How to Comply

Ensure that the application works with the technologies claimed.
Test Methodology

  • ISVs shall run the corresponding MPR http://www.microsoftplatformready.com/home.aspx tests for each applicable technology. Known to date Microsoft technologies that can interact with CRM are:

    • .Net Applications

    • Windows Phone Applications

    • Windows Server Hosted clients (e.g. Web Applications)

    • Windows Azure Hosted clients

    • Windows 7 Clients

  • To validate interaction with CRM the test tool will ask ISVs to specify the username that will be used during the test and monitor any SDK calls. The tool will then analyze the calls and determine if activity was indeed performed by the user supplied.


Criteria for Passing

  • Each of the tests that is applicable to the technology used need to pass.

  • The test tool shall detect evidence that the ISV application effectively interacted with CRM

Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət