Issue
With BC21 the AL Test Runner has now included testing with permissions. The test codeunit property TestPermissions is now fully operational.
Current behavior
The consequence is that any test codeunit by default (using MS Test Runner app) will be run with permissionset 'D365 Full Access' (which is being set in codeunit 132218 "Permission Test Catalog" in Tests-TestLibraries) as the default value of TestPermissions is Restrictive.
When genearting a new feature ATDD.TestScriptor does not set the TestPermission property explicitly, so, it defaults to Restrictive, which is maybe not what the user wants.
Wanted behavior
Always add the TestPermission property to a newly created test codeunit. The value of it is determined by a new setting atddTestScriptor.testPermissions allowing the user to set an intial value.
Issue
With BC21 the AL Test Runner has now included testing with permissions. The test codeunit property TestPermissions is now fully operational.
Current behavior
The consequence is that any test codeunit by default (using MS Test Runner app) will be run with permissionset 'D365 Full Access' (which is being set in codeunit 132218 "Permission Test Catalog" in Tests-TestLibraries) as the default value of TestPermissions is Restrictive.
When genearting a new feature ATDD.TestScriptor does not set the TestPermission property explicitly, so, it defaults to Restrictive, which is maybe not what the user wants.
Wanted behavior
Always add the TestPermission property to a newly created test codeunit. The value of it is determined by a new setting
atddTestScriptor.testPermissionsallowing the user to set an intial value.