1. VISUAL STUDIO 2010 TEAM SYSTEM CAPABILITIES WITH DYNAMICS AX Advisor - Simanta Mitra Client - Shawn Hanson & Dave Froslie (Microsoft) Group - Dec10-08 Ian Dallas Jacob Grimm Yuriy Gritsenko Matt Smith

2. PROJECT PLAN Problem Users & Use Cases Assumptions Limitations Deliverables System Description Requirements Constraints Risks Milestones Resources Tasks

3. Problem Manage, execute, and report on Dynamics AX test cases in Visual Studio 2010

4. Users & Use Cases Primary User – VS Tester Works entirely in VS2010 & MTLM Develops requirements & test cases Executes test cases Secondary User – AX Developer Works entirely in Dynamics AX Develops code Writes test cases

5. Assumptions Tests formatted properly & fully functional in default environment VS2010 Ultimate & Dynamics AX being used Using TFS as repository Limitations Restricted to use of VS2010, Dynamics AX & TFS Must have functioning network access to TFS & Dynamics AX VS2010 unreleased – Little Documentation

6. Deliverables A process to: Import Dynamics AX test case information into TFS Retrieve test case information from TFS Execute Dynamics AX Tests through VS2010 Report on Dynamics AX Tests run through VS2010 A detailed tutorial illustrating how to perform the above process

7. System Description

8. Functional Requirements 1. Imported Test Case Information Provide details about which class/module AX test case belongs to Provide metadata for each AX test case about method/function being tested 2. Management View wrapped AX test case names within MTLM Choose AX test cases to run within MTLM 3. Execution Takes no more than 10% longer than when run in Dynamics AX AX test case results displayed in MTLM 4. Reporting Display Error/Fail messages normally associated with test cases Report Pass/Fails Report number of test cases run

9. Non-Functional Requirements Written in.NET managed code Tutorials & documentation designed for ease of use Applicable to any valid Dynamics AX Test cases Varying levels of granularity – Project, Class, Method

10. Constraints Deliverables small enough to be transferred through Codeplex Function on VS2010 compatible machine without additional software Cannot modify VS2010 or Dynamics AX

11. Risks RiskLikelinessDescriptionMitigation Feature CreepSomewhat likely A significant level of ambiguity is built into the project that can lead to more features being requested as we progress. To avoid this, we need to define the scope in writing and only add to it if all tasks have been completed. Insufficient knowledge of relevant technologies Somewhat likely Because we are using technology that is both new to us and has versions that were just newly released, relevant information is tough to locate. Use clients' knowledge and contacts to locate necessary information. Hardware failureUnlikely The software will be developed on personal machines while TFS is located on a campus server. Contact service center for immediate diagnosis and maintenance. Access to required software unavailable Somewhat unlikely The speed with which we can acquire the necessary licenses is a concern due to the various software packages we require to complete the project. Remain in contact with MSDNAA and Microsoft to inform them what we need and when we need it. Trying to accomplish too much at once Somewhat likely Due to the ambiguity of the project there is a potential to spread ourselves too thin. Approach each task separately

12. Resources & Cost Estimate General Resource Requirements Server that supports Windows 2008 Visual Studio 2010 Ultimate w/ Team Foundation Server Windows Server 2008 R2 Standard w/ 10 CALs Dynamics AX 2009 TypeItemCost Hardware Computer able to support Windows Server 2008 $500 SoftwareVisual Studio w/ TFS$5469 Software Windows Server 2008 R2 Standard w/ 10 CALs $1209 Labor 8hrs/week * 80 weeks* $20/hr $12800 Total $19978

13. Schedules

14. DESIGN Functional Decomposition User Interface Specification Test Plan

15. Functional Decomposition – Import

16. Functional Decomposition – Retrieval

17. Functional Decomposition

18. User Interface Specification

19. User Interface Specification Cont

20. Test Plan - Import Test FunctionTest NameTest DescriptionExpected Outcome XPO to Excel ConverterValid XPO A valid XPO file is passed to the converter A properly formatted Excel file containing the test cases is returned Invalid XPO An improperly formatted XPO file is passed to the converter The converter detects an invalid XPO file and returns an error message to the user (100) NonExistent XPO A nonexistent XPO file is passed to the converter The converter detects a non existent file and returns an error message to the user (101) Test Case MigratorValid Excel File A valid Excel file is passed to the migrator Test cases are added to TFS that correspond with the test cases in the Excel file Invalid Excel File An improperly formatted Excel file is passed to the migrator No test cases are added to TFS and an error message is returned to the user (200) Nonexistent Excel File A nonexistent Excel file is passed to the migrator The migrator prompts the user for an existent Excel file Invalid TFS Server A nonexistent TFS server is passed to the migrator The migrator prompts the user for a valid TFS server Invalid credentials for TFS The credentials for connecting to TFS are incorrect or lack permissions An error message is returned to the user (201)

21. Test Plan - Export Test FunctionTest NameTest DescriptionExpected Outcome TFS Test Case RetrivalValid Test Case A valid test case is retrieved from TFS The test case is shown in a list that the user can select from No Test Cases to Retrieve The TFS repository contains no test cases There are no test cases for the user to select, however, they can reenter another TFS repository Invalid TFS Server An invalid TFS repository is given by the user An error message is returned to the user (300) Invalid credentials for TFS The credentials for connecting to TFS are incorrect or lack permissions An error message is returned to the user (301)

22. Test Plan – Execute & Report Test FunctionTest NameTest DescriptionExpected Outcome Generic AX Test Case RunnerValid Generic Test Case RunA valid generic test case is run The results for the test case run in AX are shown in MTLM AX32.exe Not Available The path for AX32.exe does not contain AX32.exe An error message is returned to the user (400) Network Error The path for AX32.exe is across a network which the client cannot connect to An error message is returned to the user (401) Invalid XPO Parameter An invalid XPO file is passed to the runner An error message is returned to the user (402) Nonexistent XPO Parameter A nonexistent XPO file is passed to the runner An error message is returned to the user (403) Empty Test Case File An empty test case file is passed to the runner No wrapped test cases are run Invalid Test Case File An invalid test case file is passed to the runner An error message is returned to the user (404) Improperly Formatted Summary Result XML File An improperly formatted summary result XML file is passed to the runner An error message is returned to the user (405)

23. CONCLUSION Current Status Team Contributions Individual Contributions Future Plan

24. Acquired Server Setup & Configured TFS Acquired & Installed Dynamics AX 2009 Researched Generic Test Case Wrapping Executed & Obtained Results of Generic Non-AX Test Cases Current Status – On Schedule

25. Team Contributions Research on: Visual Studio 2010 Generic Test Wrapping Generic Test Experimentation Deliverables Project Plan Design Document Weekly Meetings Team With Microsoft

26. Individual Breakdown Ian Dallas Communications Liaison Jacob Grimm System Administrator Yuriy Gritsenko Team Lead Compiled Documents Matt Smith Webmaster

27. To Do – Fall 2010

28. Questions?