If you are writing Business Central automated tests then you are probably creating some data as part of those tests. Sometimes it can be useful to see the records that have been created, especially if you are trying to create the correct scenario for the GIVEN part of your test and are experimenting with the library codeunits in that part of the system.
For quite some time, it has been possible to run automated tests in Docker using the Run-TestsInBcContainer function and it is my strong belief that this is used by a lot of partners today. Since 17.2, the Test Runner is available in Online Business Central Sandbox environments for installation from AppSource. From Extension Marketplace, you can install the Test Runner, open page 130451 and run your test manually. With BcContainerHelper 2.0.4 or later, you can also run tests in online sandbox environments, this blog post explains how.
I don’t think webhooks need an introduction. But for those who are new to the topic, here you can find the official documentation. In short, a webhook is a push notification. The “don’t call us, we’ll call you” scenario of web services. You tell Business Central in what resource you are interested (e.g. Item, Customer, etc.), and they’ll call you in case there is any change. With resource I mean any of the existing APIs, including custom APIs.
Let’s talk about the performance of the test code that we write for Business Central. What do I mean by “performance” and how can we improve it?
Obviously, before we set out to improve something we need to have an idea of what it is we’re trying to optimise for. I’m coming to think of the performance of test code in a couple of key ways:
Over almost a decade I have been evangelizing test automation by blogging, presenting at various conferences and webinars, workshops, and, eventually last year, writing a book. People are picking up, but it’s clear there is still “a war to be won”. Testing, more specifically test automation, is too often considered a cost center instead of an essential part of our daily development practice.
On April 1st, we shipped Microsoft Dynamics 365 Business Central 2020 Wave 1. It is a great release with a lot of exciting new features, which I will leave to others to write about and describe.
I will instead write about a small issue on the 19 local 16.0 DVDs you can download. They all contain test framework apps and our Microsoft test apps which ships for W1.
When working on getting the standard tests running on our solution the standard Test Tool was not making our live as easy as it could. Wanting to rerun only successful or failing tests, this was near to impossible. Manually deselecting individual tests turning of the Run field, was, euphemistically said, not the most meaningful thing to do.