Skip to main content

MSDYN365BC - Futuristic CAL Development - Testing Customization.

Hi Readers,


As discussed in the Last article, in this post we will Test for all development done in this series.


If you are new to this series then Please Refer Table of Index.


We will break our Test in multiple Test Cases to test all subscribers that we have developed in our Functionality.

Let's Test our solution.
Test Case  1 - If we Create a Purchase order with a G/L Account line & a Line with Item. Does Line with G/L Account bring the Expense Code automatically or not?


Test Results - PASS.

Test Case  2 - If user Change Quantity Expense Code becomes Blank or Not?


Test Results - FAIL.

A wrong Event subscribed. Actually, we subscribed to Location Code instead of Quantity field in Purchase Line as shown below. (Refer Here for Mistake)

Wrong (Current) Subscriber - Subscribed in Location Code Field.


Right Subscriber - Subscribing the Quantity Field.


Testing again with update Subscriber.


Test Results - PASS.

Test Case  3 - If a user tries Posting purchase order with Line with G/L Account Does not have Expense Code. Will it error out and for the right line?

Test Results - FAIL.

A code is checking Expense Code in all lines which it should, as our expense code functionality is only for Lines with G/L Account. That means we have wrong code in Subscriber as shown below.


Let Update Code and filter TESTFIELD for Line with Type G/L Account in Subscriber to check only lines with G/L Account as shown below.


Testing again with updated Subscriber Code.


Test Results - PASS.

Test Case  4 -  As per customer requirements, System should check Expense Code in the Purchase Line is Disabled or not. If Disabled then system should generate an error message.

Set Disable EXP1 from the Expense Page as shown below.


As we have seen in the last test case, there was no code for the same requirement (as shown below).


so Test Results - FAIL.

Let's add the code in the subscriber to check expense status as shown below.


Now let's test the solution with updated code in subscriber codeunit.


Test Results - PASS.

Test Case  5 - Now let's assign "Expense Code" in Purchase Line and then post Purchase Order and see in G/L Entries.


Test Results - PASS.

In Next Article, we will develop the Report which is the last part of Customer Requirements.

Let us know your thoughts as a comment on the article. Hope it makes sense!

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

NAV 2013 Credential Type - How to Use?

Hi all, Please do these activities when you have time, its a long activity and i would suggest do all activities in one go. So be clam and lets start. For NAV 2013 R2 Refer Here. For NAV 2016 Steps have been Reduced Please Refer Here. I have installed NAV 2013 and its work great with my windows credentials. I was checking the service console (Microsoft Dynamics NAV Administration) in NAV 2013 and found out that Credentials Type have multiple Options.