mfp's two cents

...on Dynamics AX Development!

April, 2009

  • mfp's two cents

    Thank you - Arijit Basu!


    I've just handed over my final edits to my chapters of the upcoming "Inside Dynamics AX 2009" book to MS-Press. A big THANK-YOU is due to the book's technical reviewer Arijit Basu. He has diligently reviewed every single paragraph and added suggestions for improvements, corrected inaccuracies, highlighted ambiguities, pointed out missing information and spotted occasional blunders. He has also ensured that all the examples in the book are working as expected, and the figures are illustrative. I've not counted how many hundreds of comments Arijit has added to my chapters, but I'm very pleased with the thorough review. (I can now rest assure that the content is not too far from the mark.)   Arijit; this book would not have had the high quality - if it were not for your massive review effort.

    Please visit Arijit's blog at:

  • mfp's two cents

    AX6 sneak preview - X++ Unit test improvements


    These days the first milestone of AX6 is being completed. It means the first wave of new functionality has been implemented, tested and documented. As always; it is an exciting time to be working on AX...

    One of the features coming in MorphX in AX6 is set of improvements in the X++ Unit Test framework.

    First of all the unit test framework in AX6 is leveraging the new attribute feature in the X++ langauge. For example; you can use an attribute to declaratively specify the target class for your test (i.e. the class that is being tested by this unit test). Here is how:

    class MyTestCase extends SysTestCase

    Starting in AX6; you can also use attributes to mark which methods on the unit test class are test methods:

    public void myTest()

    If you are using both unit testing and a version control system, you can benefit from marking your most critical test methods as check-in-tests. When setting up the version control system, you can specify which test project to run during check-in, and whether to run all unit test methods, or only the unit test methods that are marked as check-in-tests. During a check-in process the specified unit tests will be executed, and only if they all succeed the check-in will be submitted. This gives you the flexibility to run the most critical unit tests during the check-in process, while still having a full suite of unit tests that can be run on-demand. Here is how to mark a method as a check-in-test:

    public void myCheckInTest()
    Using test projects in AX6 to group your unit tests brings even more benefits. When running the test project, you now get the results visible directly in the project as small icons - and when hovering over a failed unit test, you get the failure message. 

    This posting is provided "AS IS" with no warranties, and confers no rights.

Page 1 of 1 (2 items)