search

jimmymcp / al-test-runner

VS Code Extension to help run AL tests against Business Central container
https://jpearson.blog/al-test-runner-for-visual-studio-code/
MIT License
12 stars 16 forks source link

Run All Tests in a Workspace with more than one Test App #150

Open jamesmayr opened 2 months ago

jamesmayr commented 2 months ago

I set up a simple multi root workspace with 1 app and 2 test apps (All our Al workspaces contains several apps with several test apps) image

I've Published all apps to the Docker Instance.

but when i run all tests only the tests from one test app are successfully run: image

(when I uncomment the //"al-test-runner.testFolderName": "test" line in the usersettings - the tests from the other projects are run)

The error in the codeunit looks like this: image

If you need further Information, let me know.

jimmymcp commented 3 weeks ago

sorry, somehow I completely missed this issue.

Interesting scenario. To be honest I've never considered the need to support more than one test app. Everything in the extension works on the assumption that you have a single test app (it finds the workspace folder called test|tests and creates an .altestrunner folder in there, it calls PowerShell to run the tests for the app id of that test app etc.)

What is your use case here?

I can imagine that you want to combine several apps into one container and run all of their tests together - but I'd imagine that being something you'd do in a pipeline rather than in VS Code. Or maybe you have a different scenario?

jamesmayr commented 3 weeks ago

@jimmymcp Thank you for your response.

We are developing Apps for the Market Place and for the custom business central solution Nevaris (it a vertical solution for the construction domain in europe.) That means all our workspaces consists at least 4 Apps (2 Normal Apps and 2 Test Apps)

Eg: Base Application Nevaris Applicaton (depends on Base Application & on Custom Vertical Nevaris) Base Application Test (depends on Base Application, Test against Current/NextMajor/NextMinor) Nevaris Application Test (depends on Nevaris Application & on Custom Vertical Nevaris, Test against a specific release (23.05 at the moment))

the problem is that the custom vertical is always some versions behind the current release. (23.05 at the moment). That means we run the custom vertical tests on a separate test app against 23.05 and the base application tests against the current release. Thats why weed need two test projects for a workspace.

Hope this make sense for you.