Finance | Project Operations, Human Resources, ...

Unit tests execution from build pipeline problem

(1) Share

Report

Posted on by Jay Dev

Hi guys,

I have a build pipeline in our Azure DevOps, where Unit tests execution is included as a final step.

- task: VSTest@2
  displayName: 'Execute Tests'
  inputs:
    testAssemblyVer2: '$(TestAssembly)'
    # searchFolder: '$(Agent.BuildDirectory)\Bin\'
    searchFolder: '$(Build.BinariesDirectory)\CSIEAutomatedTestsSuite\Bin\'
    testFiltercriteria: '$(TestFilter)'
    vsTestVersion: 17.0
    runInParallel: false
    codeCoverageEnabled: true
    #otherConsoleOptions: '/Platform:X64 /InIsolation /TestAdapterPath:"$(VsixExtensionFolder)"'
    otherConsoleOptions: '/Platform:X64 /InIsolation'
    testRunTitle: 'Unit Test - $(Build.DefinitionName)'
    platform: '$(BuildPlatform)'
    configuration: '$(BuildConfiguration)'
    continueOnError: true
 
This task resulted in a following error:
 

An exception occurred while invoking executor 'executor://systestexecutor/v1':
Could not load file or assembly 'Microsoft.Dynamics.AX.Framework.SysTest, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

It is self-hosted agent on a VM where 'Microsoft.Dynamics.AX.Framework.SysTest' obviously installed in a C:\AOSService\PackagesLocalDirectory\bin

Could somebody point me what might be wrong?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Assisted by AI

ANInnoSolutions 446 on at

Like (0)

Report
Copy link

Link copied!
Hi Jay Dev,

1) Issue
- Unit test execution in Azure DevOps pipeline fails during VSTest step
- Error message states that assembly 'Microsoft.Dynamics.AX.Framework.SysTest' cannot be loaded
- The assembly exists on the self hosted agent under C:\AOSService\PackagesLocalDirectory\bin
- Tests are not executed because the SysTestExecutor cannot resolve required dependencies
- The issue blocks automated test execution in CI pipeline

2) Reason
- The error is caused by the test execution environment not resolving Dynamics 365 Finance assemblies at runtime
- VSTest does not automatically include AOSService binary paths in the probing path for test execution
- A required dependency (Microsoft.Dynamics.AX.Framework.SysTest) is not found in the test working directory or search path
- This leads to a failure when the SysTestExecutor tries to initialize and load AX test framework assemblies
- This can happen because the build agent environment is not configured like a full D365 runtime environment (missing PATH / binding context / probing paths)

3) Resolution
- Copy required AX assemblies (including Microsoft.Dynamics.AX.Framework.SysTest and dependencies) into the test binaries folder before running VSTest
- Alternatively extend the PATH or use a runsettings file to include probing paths pointing to C:\AOSService\PackagesLocalDirectory\bin
- Ensure that the test adapter and SysTest framework DLLs are available in the same directory as the test assemblies
- Use TestAdapterPath parameter to explicitly point to the AX SysTest adapter if required
- Validate that the correct platform (x64) and isolation settings are used as already configured
- Run tests locally on the agent VM using vstest.console to confirm environment setup outside pipeline
- Ensure that the service account running the agent has access to the AOSService folder
- Consider packaging test execution within a deployable package or use a build VM image that includes the full D365 runtime
- If needed create a pre step in the pipeline to prepare the AX runtime context before test execution
*When modifying specific path objects, please note that missing or a higher amount of objects can cause inconsistencies during execution times

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References:

Microsoft Licensing Guide

Microsoft Doc`s/Learn

Was this reply helpful? Yes No
Subra 456 on at

Like (0)

Report
Copy link

Link copied!

Hi Jay,

Could you please let me know which version you are using in D365 and please make sure you have checked-in all the required files.

Thanks,
Subra

Was this reply helpful? Yes No
Deepak Agarwal 8,791 on at

Like (0)

Report
Copy link

Link copied!

Hey Jay,

This type of error generally come when in your development you miss a model dependency. I am not entirely sure on your case though. Is there any development done as part of testing? Also are you getting same error on all environment or specific environment.

Was this reply helpful? Yes No