Reviewing the results of the unit test
by Mat Fergusson, Simon Buxton
Mastering Microsoft Dynamics AX 2012 R3 Programming
- Mastering Microsoft Dynamics AX 2012 R3 Programming
- Table of Contents
- Mastering Microsoft Dynamics AX 2012 R3 Programming
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Preparing Our Solution
- The technical architecture of a solution
- Minimizing the footprint of changes
- Selecting the appropriate layer for our solution
- Configuring source control
- Creating the models
- Creating a label file
- Creating a project
- Setting up the default project and model
- Designing the technical solution
- Designing test plans
- Summary
- 2. Creating Data Structures
- 3. Creating the User Interface
- 4. Creating Business Logic and Hooking into Core AX
- Moving table validation and logic into a class
- Adding navigation
- Number sequences
- Hooking into standard AX logic using event handling
- Summary
- 5. Adding Business Intelligence
- 6. Extending the Solution
- Adding secondary list pages
- Using menu items to change the vehicle status
- Adding a drop dialog to change vehicle group
- Exposing the vehicle group logic as a custom web service
- Summary
- 7. Designing Your Security Model
- 8. Customizing Standard AX
- Key goals when customizing standard or third-party code
- How to determine where to make the change
- Adding fields to tables
- Integrating a custom module with standard AX
- Using an extension table for additional fields
- Changing the behavior of a class
- Extending a framework – vendor electronic payments
- Summary
- 9. Advanced Features and Frameworks
- Adding custom filters to list pages
- Advanced methods of adding ranges to list pages
- Using the SysOperation framework
- Using the SysOperation framework execution modes
- Customizing the user interface displayed by the SysOperation framework
- Tracking progress of scheduled tasks
- Understanding the global address book
- Accessing the financial dimension framework
- Summary
- 10. Advanced Development Techniques
- 11. Unit and Performance Testing
- A. Efficient Design and Development with Microsoft Dynamics AX
- B. Using Version Control
- C. Code Editor Scripts
- Index
Even the simplest code has some part that executes conditionally, and we need to be sure we have tested all of the code. The test framework allows us to assess how much of the code was actually tested. This is called code coverage.
This time, we will turn on code coverage, which is done by the following steps:
- In the unit test toolbar, click on Parameters.
- In the form, check both Record code coverage and Record number of records.
- Run the test again, and click on Details once the test completes. This form shows a record for each test run and some statistics and details about the test.
- Select the last test run and click on Tests.
- Since the last test was just for one class, we will see one record in the list of test cases, and a record for each test method, as shown here:
- To check the code that was covered for the test case, click on Coverage in the top-right corner and press Compare on the Code coverage form.
- Expand the Methods node, select
initFromConFMSVehicleTable, and review the results, as shown in the following screenshot:
Here, we can see that line 9 was not executed or covered by our test, hence the tick symbol that is not in a green circle. We can also see that the update method was not covered at all.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.