Book Image

Learning Dynamics NAV Patterns

By : Marije Brummel
Book Image

Learning Dynamics NAV Patterns

By: Marije Brummel

Overview of this book

Microsoft Dynamics NAV is a complete ERP system, which also contains a robust set of development tools to support customization and enhancement. These include an object designer for each of the seven application object types, a business application-oriented programming language with .NET interface capability, a compiler, a debugger, and programming testing language support. Learning Dynamics NAV Patterns will guide you through the NAV way of solving problems. This book will first introduce you to patterns and the software architecture of the NAV and then help you to build an example application. Then, it walks you through the details of architectural patterns, design patterns, and implementation patterns. This book will also talk about anti-patterns and handling legacy code. Finally, it teaches you to build solutions using patterns. Proven patterns and best practices will help you create better solutions that are easy to maintain in larger teams across several locations. It will guide you through combining abstract patterns using easy-to-understand examples and will help you decide which patterns to use in which scenarios.
Table of Contents (9 chapters)
8
Thank you for buying Learning Dynamics NAV Patterns

Testing the application

After we have built all the functions, we can start testing the application. Please note that we have not built any user interface. The basic methods of our application can all be tested without the UI. We will only need to test the UI code if the code was intended to influence the UI.

We need to build a test Codeunit, containing the elements that we would like to test. It should also create the Setup and Master Data that we need.

This can be split into two test code units, but for the sake of simplicity, we have combined them into one.

The first set of test functions implements the data, whereas the second set tests the result. We have a set of helper functions to avoid duplicate code.

One of the tests is the price calculation. We can create a specific record in the price table, and then test whether the price is applied:

[Test] TestPrice()
Stay.GET('STAY0001');
Stay.TESTFIELD(Price, 10);

Test isolation...