Van Vugt's dynamiXs

When working on getting the standard tests running on our solution the standard Test Tool was not making our live as easy as it could. Wanting to rerun only successful or failing tests, this was near to impossible. Manually deselecting individual tests turning of the Run field, was, euphemistically said, not the most meaningful thing to do. So, already a couple of years ago we decided to add some actions to the test tool allowing us to (1) select the Run field for (a) all tests (b) only failing…

Overtime I have been advocating the use of the standard Business Central tests in various posts, webinars, conference presentations, and my book . IMHO this has been, and still, is an undervalued collection of over 22,000 automated tests that cover all functional areas. It's a no brainer to let them run on your solution as we did on ours . In case your solution intertwines with standard code chances are big that these tests will also hit your code resulting in a number of failing tests. As discussed…

Those of us that have been around long enough will remember that Microsoft Business Solutions-Navision 4.0 came out with the new XMLport and MenuSuite object types. I can clearly remember a sort of astonishment about this UI-less XMLport. To allow you to feed this "pipeline" with data you had to wrap it in another object. Where Dataports had Request Forms like reports the XMLport totally failed this. And if you wanted the user to provide input, you would typically wrap the call to the XMLport…

Together with Global Mediator we start a series of blogposts about QA for Dynamics channel. The idea was born when both I and my Global Mediator friends came to the same conclusion: test automation is still not really taking off in the Dynamics NAV/BC world, let alone quality assurance. So we sat down and started a joined project which we baptised: QA, the ugly duckling . Through this we want to sharpen our minds and at the same make you, our readers, part of it. Let's see how this first stone…

While developing your own extension on NAV 2018 or "BC under version 15" you have the availability over 2 debuggers: the VSCode debugger and the C/SIDE (or should we call it Windows) debugger. Both serve a somewhat different scenario: VSCode debugger You want to run step-by-step through the code of your extension - being AL code - and from there might step into the code that resides in the NAV/BC installation you are programming against. Most probably the C/AL code of the standard application…