Test Codeunit: PTE0007: Assertion function 'AssertError' must not be invoked.

[richardrobberse]

Using the AssertError function in an AL test codeunit results in the following error:
PTE0007: Assertion function 'AssertError' must not be invoked.

PTE0007 says: Test assertion functions are not allowed in a non-test context.
So it looks like codeunits with SubType = Test are not recognized as a test context.

DockerImage: bcinsider.azurecr.io/bcsandbox-master:13.0.22070.0-nl
AL Lanuage: 0.15.14407

[atoader]

Hi, @richardrobberse! You are right, this looks like a bug, but I need to investigate. Are you building a Per Tenant Extension? From what I know, these extensions should not contain tests.

[richardrobberse]

Hey @atoader I have separated my automated tests from my actual app by creating a separate extension that contains my automated tests.
The test extension has a dependency on my actual extension so that I can code against it.

[atoader]

I think the fastest way around this is to disable the "${PerTenantExtensionCop}" for your test extension. That doesn't need to respect the rules of the analyzer.

[atoader]

As far as I can see, this issue has been fixed in the latest version of the AL extension. You can disable errors locally by using rulesets https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-rule-set-syntax-for-code-analysis-tools

[richardrobberse]

That's great news 👍
I'll try the suggested workaround.

Thanks

[atoader]

You're welcome :) ! Please close the issue if it works or let me know if it doesn't.

[richardrobberse]

It worked :)
Can you add the tags so that it's clear it will be fixed in a future release, this will help other people facing the same thing.

[atoader]

Note for future readers: This issue has been fixed in the latest version of the AL Language extension. This version of the extension will ship in the next major release of the product.