Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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
.Automated Testing in Microsoft Dynamics 365 Business Central

You're reading from   .Automated Testing in Microsoft Dynamics 365 Business Central Efficiently automate test cases in Dynamics NAV and Business Central

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789804935
Length 222 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Luc van Vugt Luc van Vugt
Author Profile Icon Luc van Vugt
Luc van Vugt
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: Automated Testing - A General Overview
2. Introduction to Automated Testing FREE CHAPTER 3. Section 2: Automated Testing in Microsoft Dynamics 365 Business Central
4. The Testability Framework 5. The Test Tool and Standard Tests 6. Section 3: Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
7. Test Design 8. From Customer Wish to Test Automation - The Basics 9. From Customer Wish to Test Automation - Next Level 10. From Customer Wish to Test Automation - And Some More 11. Section 4: Integrating Automated Tests in Your Daily Development Practice
12. How to Integrate Test Automation in Daily Development Practice 13. Getting Business Central Standard Tests Working on Your Code 14. Test-Driven Development 15. Setting Up VS Code and Using the GitHub Project 16. Other Books You May Enjoy

Test example 3 – a first UI test

The field Lookup Value Code had been implemented on the Customer table and tested. But, of course, to allow users to manage it, it needs to be made accessible in the UI. Consequently, it needs to be placed on the Customer Card.

Customer wish

The next stage of the customer wish is very close to the previous part defined by [SCENARIO #0001]. The main difference is that we now want to access a customer by means of the UI element Customer Card. By mimicking end users, our scenario describes creating a new Customer Card (see second [GIVEN]). Have a look:

[FEATURE] LookupValue UT Customer
[SCENARIO #0003] Assign lookup value on customer card
[GIVEN] A lookup value
[GIVEN] A customer card
[WHEN...
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