Running Canopy in Azure Devops












1















I have a couple of automated tests written in Canopy. I run them locally by running the following command:



dotnet run Project.AutomatedTests.fsproj


on Azure DevOps I tried to configure them the same way, so I have the following steps:



1.



dotnet restore Project.sln


2.



dotnet build Project.sln


3.



dotnet run Project.AutomatedTests.dll


But Azure DevOps fails with following error:



2019-01-19T11:11:42.5195371Z ##[error]Error: /usr/bin/dotnet failed with return code: 1
2019-01-19T11:11:42.5219579Z ##[error]Dotnet command failed with non-zero exit code on the following projects : /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/publish/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/obj/Release/netcoreapp2.1/Project.AutomatedTests.dll


I also tried running:



dotnet run Project.AutomatedTests.fsproj


But it fails with the same error.



I tried to run it with --project argument like that:



-v d --project /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Project.AutomatedTests.fsproj


but tests hangs up with the following exception:



 at Start.main(String _arg1) in /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Program.fs:line 17
at canopy.classic.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.fs:line 250
at canopy.parallell.functions.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.parallell.functions.fs:line 835
at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)


Maybe someone has an idea what I did wrong?










share|improve this question

























  • Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

    – nilekirk
    Jan 19 at 13:45











  • Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

    – MNie
    Jan 19 at 14:32











  • Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

    – nilekirk
    Jan 19 at 14:41











  • Nope with release.

    – MNie
    Jan 19 at 14:43











  • Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

    – Devon Burriss
    Jan 23 at 20:06
















1















I have a couple of automated tests written in Canopy. I run them locally by running the following command:



dotnet run Project.AutomatedTests.fsproj


on Azure DevOps I tried to configure them the same way, so I have the following steps:



1.



dotnet restore Project.sln


2.



dotnet build Project.sln


3.



dotnet run Project.AutomatedTests.dll


But Azure DevOps fails with following error:



2019-01-19T11:11:42.5195371Z ##[error]Error: /usr/bin/dotnet failed with return code: 1
2019-01-19T11:11:42.5219579Z ##[error]Dotnet command failed with non-zero exit code on the following projects : /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/publish/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/obj/Release/netcoreapp2.1/Project.AutomatedTests.dll


I also tried running:



dotnet run Project.AutomatedTests.fsproj


But it fails with the same error.



I tried to run it with --project argument like that:



-v d --project /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Project.AutomatedTests.fsproj


but tests hangs up with the following exception:



 at Start.main(String _arg1) in /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Program.fs:line 17
at canopy.classic.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.fs:line 250
at canopy.parallell.functions.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.parallell.functions.fs:line 835
at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)


Maybe someone has an idea what I did wrong?










share|improve this question

























  • Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

    – nilekirk
    Jan 19 at 13:45











  • Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

    – MNie
    Jan 19 at 14:32











  • Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

    – nilekirk
    Jan 19 at 14:41











  • Nope with release.

    – MNie
    Jan 19 at 14:43











  • Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

    – Devon Burriss
    Jan 23 at 20:06














1












1








1








I have a couple of automated tests written in Canopy. I run them locally by running the following command:



dotnet run Project.AutomatedTests.fsproj


on Azure DevOps I tried to configure them the same way, so I have the following steps:



1.



dotnet restore Project.sln


2.



dotnet build Project.sln


3.



dotnet run Project.AutomatedTests.dll


But Azure DevOps fails with following error:



2019-01-19T11:11:42.5195371Z ##[error]Error: /usr/bin/dotnet failed with return code: 1
2019-01-19T11:11:42.5219579Z ##[error]Dotnet command failed with non-zero exit code on the following projects : /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/publish/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/obj/Release/netcoreapp2.1/Project.AutomatedTests.dll


I also tried running:



dotnet run Project.AutomatedTests.fsproj


But it fails with the same error.



I tried to run it with --project argument like that:



-v d --project /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Project.AutomatedTests.fsproj


but tests hangs up with the following exception:



 at Start.main(String _arg1) in /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Program.fs:line 17
at canopy.classic.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.fs:line 250
at canopy.parallell.functions.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.parallell.functions.fs:line 835
at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)


Maybe someone has an idea what I did wrong?










share|improve this question
















I have a couple of automated tests written in Canopy. I run them locally by running the following command:



dotnet run Project.AutomatedTests.fsproj


on Azure DevOps I tried to configure them the same way, so I have the following steps:



1.



dotnet restore Project.sln


2.



dotnet build Project.sln


3.



dotnet run Project.AutomatedTests.dll


But Azure DevOps fails with following error:



2019-01-19T11:11:42.5195371Z ##[error]Error: /usr/bin/dotnet failed with return code: 1
2019-01-19T11:11:42.5219579Z ##[error]Dotnet command failed with non-zero exit code on the following projects : /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/bin/Release/netcoreapp2.1/publish/Project.AutomatedTests.dll,/home/vsts/work/1/s/backend/tests/Project.AutomatedTests/obj/Release/netcoreapp2.1/Project.AutomatedTests.dll


I also tried running:



dotnet run Project.AutomatedTests.fsproj


But it fails with the same error.



I tried to run it with --project argument like that:



-v d --project /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Project.AutomatedTests.fsproj


but tests hangs up with the following exception:



 at Start.main(String _arg1) in /home/vsts/work/1/s/backend/tests/Project.AutomatedTests/Program.fs:line 17
at canopy.classic.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.fs:line 250
at canopy.parallell.functions.start(BrowserStartMode b) in C:projectscanopysrccanopycanopy.parallell.functions.fs:line 835
at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)


Maybe someone has an idea what I did wrong?







azure f# azure-devops canopy-web-testing






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 19 at 19:03







MNie

















asked Jan 19 at 11:40









MNieMNie

7751929




7751929













  • Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

    – nilekirk
    Jan 19 at 13:45











  • Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

    – MNie
    Jan 19 at 14:32











  • Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

    – nilekirk
    Jan 19 at 14:41











  • Nope with release.

    – MNie
    Jan 19 at 14:43











  • Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

    – Devon Burriss
    Jan 23 at 20:06



















  • Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

    – nilekirk
    Jan 19 at 13:45











  • Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

    – MNie
    Jan 19 at 14:32











  • Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

    – nilekirk
    Jan 19 at 14:41











  • Nope with release.

    – MNie
    Jan 19 at 14:43











  • Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

    – Devon Burriss
    Jan 23 at 20:06

















Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

– nilekirk
Jan 19 at 13:45





Try set the verbosity flag to d or diag to get more info (dotnet run -v d ...)

– nilekirk
Jan 19 at 13:45













Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

– MNie
Jan 19 at 14:32





Nothing change. There is also a communicate that the file was not found. But when I run dotnet build instead of run everything was ok.

– MNie
Jan 19 at 14:32













Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

– nilekirk
Jan 19 at 14:41





Seems that maybe dotnet run looks for dlls in ../Release/... Maybe you are building with Debug configuration. Try pass -c Release to dotnet build.

– nilekirk
Jan 19 at 14:41













Nope with release.

– MNie
Jan 19 at 14:43





Nope with release.

– MNie
Jan 19 at 14:43













Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

– Devon Burriss
Jan 23 at 20:06





Maybe you could setup a minimal repo example repository on git? Here is a repo of some canopy test I wrote for a blog post github.com/dburriss/PageModuleModelExample . It uses dotnet core so maybe it will help? Note that you run (Powershell) dotnet .CoolblueUiTests.dll. Note the run part is gone when executing a dll.

– Devon Burriss
Jan 23 at 20:06












1 Answer
1






active

oldest

votes


















0














The solution to my problem was:



start ChromeHeadless


instead of:



start chrome


and after that everything works just fine.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54266689%2frunning-canopy-in-azure-devops%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The solution to my problem was:



    start ChromeHeadless


    instead of:



    start chrome


    and after that everything works just fine.






    share|improve this answer




























      0














      The solution to my problem was:



      start ChromeHeadless


      instead of:



      start chrome


      and after that everything works just fine.






      share|improve this answer


























        0












        0








        0







        The solution to my problem was:



        start ChromeHeadless


        instead of:



        start chrome


        and after that everything works just fine.






        share|improve this answer













        The solution to my problem was:



        start ChromeHeadless


        instead of:



        start chrome


        and after that everything works just fine.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 24 at 19:26









        MNieMNie

        7751929




        7751929






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54266689%2frunning-canopy-in-azure-devops%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Homophylophilia

            Updating UILabel text programmatically using a function

            Cloud Functions - OpenCV Videocapture Read method fails for larger files from cloud storage