D365 Finance and Operation Performance Testing

Learn how to create a script for performance testing Microsoft D365 Finance & Operations with StresStimulus.

Microsoft D365 F&O, automatic script creation

Transcript

Welcome to StresStimulus video training. In this video, I will show you how to record and configure a script for performance testing Microsoft D365 for finance and operation. Its performance testing is necessary to ensure adequate user experience under various load conditions. The challenge of load-testing D365 F&O is that in this application, a large number of page objects have dynamic IDs that must be correlated. StresStimulus handles all script correlations automatically, regardless of the complexity of the test scenario and the amount of customization in your instance. I will record a scenario that creates a purchase order with one line item here. For more realistic testing, I will then parameterize it to include test data in the load-testing process. Finally, I will add a loop to create POs with a variable number of items. In StresStimulus I click on the recorder to start the recording wizard. Enter a test case name: "Create purchase order". Select a web browser, Microsoft Edge, and click Next. Entered the URL. . . . and the name of the first transaction, "Landing page". Click here to open the browser and start recording. In the StresStimulus recorder, add transaction "Login" and enter the credentials. Once the application loads, add transaction All POs and navigate to the purchase order grid. Add transaction New PO and click New. Paste the customer number and click OK. To add a line, create a new transaction, add line Item, click add line and paste the item number D0001. Add transaction Save. and click the Save button. "Log out" and sign out. Click the stop button to end the recording. The StresStimulus proprietary autocorrelation engine is scanning the script and creating correlation rules automatically. As you can see in the progress bar, StresStimulus creates a large number of autocorrelation parameters. Some of these parameters are immediately necessary for the script to work correctly, and others are essential to support the expiration of some tokens. If you don't have them, the script will initially work, but it will fail after the tokens expire, which may be in 24 or 48 hours. Now let's verify the script by playing it back to ensure it is properly correlated. The verification shows no errors. Now let's check if the script created a new purchase order. I go back to the purchase order page and refresh it. And there are two identical POs were created, one during recording and another one during script playback. Now let's customize the script to create POs with a random number of different items. I will parameterize the item with a dataset containing item information and create a loop for adding items with a repeat count from a data generator. I navigate to the dataset section. Click the import button. I will use a CSV file. Enter the path of the Item file. Click next with all defaults until the last step to create the dataset, Items. Change its default binding mode to VU-iteration-bound to use a different Item on every loop iteration. Then click the Finish button. Next, let's search the requests for the recorded item number, D0001. StresStimulus highlights the requests with this Item. Right-click the first highlighted request and select Create a Parameter. In the parameter dialog, right-click on the highlighted value and replace it with the dataset column, Item Number. In the appeared MessageBox select OK to create more parameters like this one in other requests. Now, let's create a random number of line repeats. Navigate to the data generator section and create a new one. Select integer and set the min and max to 2 and 4. Name it, ItemCount. Now let's create a loop. In the text case tree, right-click on the Add line item transaction. Select Create Container and click Loop. Set the number of Repeats property to the new data generator, ItemCount. Verify again to ensure that the parameters are created correctly. The verification reported no errors. Let's also check in the browser that one more PO was created. Refreshing? A new PO was created. Click to confirm it has a random number of lines exceeding one. It does. And the Item numbers are from the dataset. Now this script is ready to be used in a Load Test. For help with test configuration, users can schedule scripting sessions from the StresStimulus Help menu, Support Options. Let's review the main takeaways: We went over the following StresStimulus elements: Correlation required for D365 F O scripts to work, is automatic. Parameterization allows using test data. Loops are used to customize user flow. Scripting sessions provided as a part of support are scheduled from the StresStimulus application. Thank you for watching