Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Dynamics NAV Patterns

You're reading from   Learning Dynamics NAV Patterns Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and design

Arrow left icon
Product type Paperback
Published in Sep 2015
Publisher Packt
ISBN-13 9781785284199
Length 214 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Marije Brummel Marije Brummel
Author Profile Icon Marije Brummel
Marije Brummel
Mark Brummel Mark Brummel
Author Profile Icon Mark Brummel
Mark Brummel
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

Preface 1. Chapter 1: Introducing Dynamics NAV Patterns and Software Architecture 2. Chapter 2: Architectural Patterns FREE CHAPTER 3. Chapter 3: Design Patterns 4. Chapter 4: Building an Example Application Using Patterns 5. Chapter 5: Coding Best Practices 6. Chapter 6: Anti-patterns and Handling Legacy Code 7. Chapter 7: Building Solutions Using Patterns 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image