WRITING YOUR OWN AUTOMATED TESTS FOR DYNAMICS 365 BUSINESS CENTRAL

In this one day workshop Luc van Vugt, the godfather of BC test automation, will learn you how to efficiently automate test cases.

You will also learn how and where to start and get a broader view on what test automation can and should entail.

Writing your own automated tests for Dynamics 365 Business Central

In this one day workshop Luc van Vugt, the godfather of BC test automation, will learn you how to efficiently automate test cases.
You will also learn how and where to start and get a broader view on what test automation can and should entail.

Writing your own automated tests for Business Central

Writing your own automated tests

In this one day workshop what the essences are of automated testing and how to apply them to your own NAV code

Tips & Tricks for efficient and effective test automation data setup

In this session we will show you different ways of how to get your test data setup efficiently and effectively. We will identify what to test, and how to isolate it, thus making it less database dependent or maybe no dependency at all.

An often heard complaint from teams starting with test automation, is the vast extend of data setup. Seemingly a whole database needs to get setup before any action under test can be executed. This often holds back whole development teams to start their test automation effort. Or, once started, makes some wonder whether they should continue this effort as it appears to be too costly, both in maintenance and repeated execution.

Moreover, you will see how these choices highly correlate to the structure of your production code and we will unveil choices you can make in the future regarding your code structure.

Test automation is a team effort

My experience is that test automation is often seen as a technical exercise: it is the developers who should be involved in this. A big misconception in my opinion. After all, just like the implementation of requirements, it is a team effort, with both a functional and a technical component, which are inextricably linked. In my session I want to highlight this and exchange ideas with the participants about the consequences.

Advanced topics in test automation

In this session Luc van Vugt (and co-speakers - see notes section) will discuss a number of advanced topic to leverage your test automation practice. Think of testing permissions, writing testable code and testing in and out going calls.

Get better code by combining Test Plan & SOLID principles making your test automation lightning fast

Most of todays automated tests are deeply database dependent. You probably know them. Those tests where a lot of data creation is done before you get to execute the action under test. The thing with them is that they both take a lot of time to build and a lot of time to run.

With the principles of SOLID, inspired by Vjeko, we have restructured the logic of the code in a way that isolates and abstracts it. This makes the tests run lightning fast because it’s no longer dependent on any data from Business Central. And next this: by applying this approach we attain less dependency on breaking changes.

This coupled with a revised test plan ensures a more stable and better testable code yielding a better result in the end.

10 Tips for successful requirement specifications

Having been around in this world of software development Henrik and Luc "have been there" and would like to share their 10 tips for successful requirement specifications. 10 tips that will help you prevent overdue deadlines, deliveries, and above all frustrations of stakeholders and contributors.

Join Henrik and Luc in a engaging session that will be worthwhile in various ways.

With Henrik, user advocate, and Luc, BC test automation guru, as a speakers we will certainly touch on the user perspective and test.

How to set up test automation fixture efficiently when your code is not SOLID

Historically BC code was never written with testability in mind. When coding tests against this code, it leaves us with ample option than setting up a lot of data before the action under test can be exercised.
Ideally you probably would like to refactor your code to comply with SOLID principles and make your automated test effort overall much simpler. But often our vast code heritage and new projects ahead do not allow us to get that prioritized and leaves us with non-SOLID code to write test automation against.
In this workshop you will learn about, and apply, various ways to efficiently set up data when creating automated tests for code that does not comply with SOLID principles.

Why bother about test automation on customer projects? You can't sell that.

Test automation (TA) tends to divide the world into two in various ways. One of them is on the edge of product vs. project where people say TA only pays of on product development and in no way on projects. "You just can't sell that."
In this session Luc van Vugt is going to shed light on this discussion and will show you how you could turn this into another direction.

Test automation starts in the requirements

My experience is that test automation is often seen as an exercise only developers are working on. A big misconception in my opinion and a potential threat to not getting test automation (TA) to become a success. TA starts in the requirements!. With TA – read: testing in general - we verify the behavior of what we have implemented, and this behavior is what our requirements (should) define. Thus TA is a team effort, with functional and technical parts inextricably linked. In my session I want to highlight this and exchange ideas with the participants about the consequences.

Real life experience with test automation

For more than 5 years already both James and Luc have gone their way in NAV/BC development that was always focused on having test automation included. Their roads crossed at different points, but mostly ran independently of each other. In this, differently flavored approaches in incorporating test automation in their daily work happened.

With this session James and Luc are going to update each other on their findings and to share with you their practical tips on what makes test automation work for them. They’re hoping to meet you then.

10 Myths about test automation on customer projects

As customers adopt the Cloud-first approach and implement Business Central SaaS, the subject of Test Automation (TA) is often left behind when PTE development is needed. TA tends to be surrounded with a lot of myths and hear-say. The biggest of them: "You just can't sell that."

Seemingly valid arguments, will have you believe that the workload and technical know-how required in order to provide your customers with TA is just "too much" and "not worth it for the customer" prevents you from even bringing it up. Henrik Helgesen and Luc van Vugt would never drive their cars without having a proper insurance, and neither should your customers.

In this session Henrik Helgesen and Luc van Vugt will unravel 10 myths about Test Automation on customer projects and provide you with suggestion on how to turn this into a business opportunity.