Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test run doesnt start from workspace (overrrides config.json) #102

Closed
VadymPatuk opened this issue Aug 16, 2023 · 3 comments · Fixed by #104
Closed

Test run doesnt start from workspace (overrrides config.json) #102

VadymPatuk opened this issue Aug 16, 2023 · 3 comments · Fixed by #104
Assignees

Comments

@VadymPatuk
Copy link

Hi James,

Has same issue #98

Figured out that using workspaces with this definition your extensión works well (same if only app.Test openned in VS)

{
  "folders": [
    {
      "path": "app"
    },
    {
      "path": "app.Test"
    },
    {
      "path": ".AL-Go"
    }
  ],
  "settings": {}
}

But if you change with this one extension stop working. After run test its loading indefinitely and never ends.

{
    "folders":  [
                    {
                        "path":  ".AL-Go"
                    },
                    {
                        "path":  "app"
                    },
                    {
                        "path":  "app.Test"
                    }
                ],
    "settings":  {
                    
                 }
}

Did you try format workspace file @alexandr-gladkiy @vengo2021 ?

@vengo2021
Copy link

vengo2021 commented Aug 17, 2023

Hi, managed to make it working by removing .Al-Go from workspace.

{
    "folders":  [
                    {
                        "path":  "app"
                    },
                    {
                        "path":  "app.test"
                    }
                ],
    "settings": {

                }
}

My config looks like:


{
    "containerResultPath":  "C:\\ProgramData\\BcContainerHelper",
    "securePassword":  "01000000d08c9ddf0115d1118c7a00c04fc297eb01000000bef05587031dd94482a03ddfa577a3b50000000002000000000010660000000100002000000063a660bb6b5cbf02b7eddbf26dbf15c3cd28acbf69933656a687362db004af85000000000e8000000002000020000000f22315d5748faedc6987152a43516ab746a7e3c8477a45e5c0e84942e842a071100000002986afc98aced0a05402ba677e7b53ae40000000b344400fe40bdd64211162e89a7b572cb7bca907a297fe32437b147ea2288b8410a6129434a4e3018b75af5edcc75d4595369fc886d2bc5eb9b6a25b90ee982e",
    "userName":  "Admin",
    "userPassword":  "admin",
    "companyName":  "CRONUS UK Ltd.",
    "testSuiteName":  "",
    "vmUserName":  "",
    "vmSecurePassword":  "",
    "remoteContainerName":  "",
    "dockerHost":  "",
    "newPSSessionOptions":  "",
    "testRunnerServiceUrl":  "https://xxx:7048/BC/ODataV4/TestRunner?company=CRONUS UK Ltd.\u0026tenant=default",
    "codeCoveragePath":  ".altestrunner//codecoverage.json",
    "culture":  "en-US",
    "launchConfigName":  "V22R3SSL"
}

@VadymPatuk
Copy link
Author

@vengo2021 ok same here, excluding .AL-Go folder from workspace fixes issue.

Worth mention that both app was added with Actions from AL-GO Pte template https://github.com/microsoft/AL-Go-PTE (example https://github.com/VadymPatuk/example-al-test-runner/actions)

Maybe workflow action somehow rearrange data in workspace file and make it incompatible with AL-Test-Runner 😕

image

@jimmymcp jimmymcp self-assigned this Aug 23, 2023
jimmymcp added a commit that referenced this issue Aug 23, 2023
Fixes #102

Take debug configuration from test folder, not first folder in the workspace
@jimmymcp
Copy link
Owner

Thanks for the repo to reproduce the problem, very helpful. It's a combination of

  • the launch configuration for each app is in the .vscode folder per app (as opposed to in the workspace or user settings - which I always use now so couldn't see the problem at first)
  • the first folder in the workspace does not contain the launch settings (because the first folder was the .AL-GO folder)

Fix coming, I'll push into the pre-release first and then into the release later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants