Testcafe “chapters” in Text Log on Browserstack









up vote
1
down vote

favorite












I have a test suite that takes ~ 10 minutes to run in BrowserStack (Automate). If a test case fails, it is challenging to find where in the recorded video the failure occurs. Having the fixture name and test name visible in the bottom of the browser helps with scrubbing through the video, but having some kind of chapter marker would be really helpful. I noticed that something in my tests is spitting out links with start buttons into the Text Log but I'm not sure what is actually causing it. Is there a way to do this on purpose?



Update with picture of what I'm talking about:
logs










share|improve this question



















  • 1




    Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
    – Mukesh Tiwari
    Nov 9 at 18:04










  • Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
    – Samantha Blasbalg
    Nov 9 at 20:02














up vote
1
down vote

favorite












I have a test suite that takes ~ 10 minutes to run in BrowserStack (Automate). If a test case fails, it is challenging to find where in the recorded video the failure occurs. Having the fixture name and test name visible in the bottom of the browser helps with scrubbing through the video, but having some kind of chapter marker would be really helpful. I noticed that something in my tests is spitting out links with start buttons into the Text Log but I'm not sure what is actually causing it. Is there a way to do this on purpose?



Update with picture of what I'm talking about:
logs










share|improve this question



















  • 1




    Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
    – Mukesh Tiwari
    Nov 9 at 18:04










  • Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
    – Samantha Blasbalg
    Nov 9 at 20:02












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have a test suite that takes ~ 10 minutes to run in BrowserStack (Automate). If a test case fails, it is challenging to find where in the recorded video the failure occurs. Having the fixture name and test name visible in the bottom of the browser helps with scrubbing through the video, but having some kind of chapter marker would be really helpful. I noticed that something in my tests is spitting out links with start buttons into the Text Log but I'm not sure what is actually causing it. Is there a way to do this on purpose?



Update with picture of what I'm talking about:
logs










share|improve this question















I have a test suite that takes ~ 10 minutes to run in BrowserStack (Automate). If a test case fails, it is challenging to find where in the recorded video the failure occurs. Having the fixture name and test name visible in the bottom of the browser helps with scrubbing through the video, but having some kind of chapter marker would be really helpful. I noticed that something in my tests is spitting out links with start buttons into the Text Log but I'm not sure what is actually causing it. Is there a way to do this on purpose?



Update with picture of what I'm talking about:
logs







e2e-testing browserstack testcafe






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 9 at 20:02

























asked Nov 9 at 14:49









Samantha Blasbalg

1877




1877







  • 1




    Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
    – Mukesh Tiwari
    Nov 9 at 18:04










  • Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
    – Samantha Blasbalg
    Nov 9 at 20:02












  • 1




    Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
    – Mukesh Tiwari
    Nov 9 at 18:04










  • Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
    – Samantha Blasbalg
    Nov 9 at 20:02







1




1




Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
– Mukesh Tiwari
Nov 9 at 18:04




Testcafe uses JS API (github.com/browserstack/api) which does not provides Selenium like functionality
– Mukesh Tiwari
Nov 9 at 18:04












Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
– Samantha Blasbalg
Nov 9 at 20:02




Yes I know that, I found that in other SO answers vaguely about this. What I'm saying is, my test runs do put things in the Text Log without me doing anything (see the picture I meant to attach originally). What is causing this to happen, and how can I do it on purpose?
– Samantha Blasbalg
Nov 9 at 20:02












1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










The Text Log on BrowserStack shows Selenium commands executed by the browser during a test session. Since TestCafe doesn't use Selenium to perform test actions it must be clear in ideal conditions, but BrowserStack will terminate the session that doesn't send any command within 90 seconds (IDLE TIMEOUT). So TestCafe retrieves the current URL every 80 seconds to work around this timeout.



To help you identify problematic tests in a recorded video, you can modify TestCafe reporters (e.g., the default spec reporter) to print a precise timestamp when a test starts. You can also modify the BrowserStack browser provider to execute custom Selenium commands that will be added to the Text Log on BrowserStack.



Also, you can create a proposal in the TestCafe repository about improving test logs on BrowserStack. If it receives enough votes, the TestCafe team will consider its implementation.






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',
    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%2f53228025%2ftestcafe-chapters-in-text-log-on-browserstack%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








    up vote
    1
    down vote



    accepted










    The Text Log on BrowserStack shows Selenium commands executed by the browser during a test session. Since TestCafe doesn't use Selenium to perform test actions it must be clear in ideal conditions, but BrowserStack will terminate the session that doesn't send any command within 90 seconds (IDLE TIMEOUT). So TestCafe retrieves the current URL every 80 seconds to work around this timeout.



    To help you identify problematic tests in a recorded video, you can modify TestCafe reporters (e.g., the default spec reporter) to print a precise timestamp when a test starts. You can also modify the BrowserStack browser provider to execute custom Selenium commands that will be added to the Text Log on BrowserStack.



    Also, you can create a proposal in the TestCafe repository about improving test logs on BrowserStack. If it receives enough votes, the TestCafe team will consider its implementation.






    share|improve this answer
























      up vote
      1
      down vote



      accepted










      The Text Log on BrowserStack shows Selenium commands executed by the browser during a test session. Since TestCafe doesn't use Selenium to perform test actions it must be clear in ideal conditions, but BrowserStack will terminate the session that doesn't send any command within 90 seconds (IDLE TIMEOUT). So TestCafe retrieves the current URL every 80 seconds to work around this timeout.



      To help you identify problematic tests in a recorded video, you can modify TestCafe reporters (e.g., the default spec reporter) to print a precise timestamp when a test starts. You can also modify the BrowserStack browser provider to execute custom Selenium commands that will be added to the Text Log on BrowserStack.



      Also, you can create a proposal in the TestCafe repository about improving test logs on BrowserStack. If it receives enough votes, the TestCafe team will consider its implementation.






      share|improve this answer






















        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        The Text Log on BrowserStack shows Selenium commands executed by the browser during a test session. Since TestCafe doesn't use Selenium to perform test actions it must be clear in ideal conditions, but BrowserStack will terminate the session that doesn't send any command within 90 seconds (IDLE TIMEOUT). So TestCafe retrieves the current URL every 80 seconds to work around this timeout.



        To help you identify problematic tests in a recorded video, you can modify TestCafe reporters (e.g., the default spec reporter) to print a precise timestamp when a test starts. You can also modify the BrowserStack browser provider to execute custom Selenium commands that will be added to the Text Log on BrowserStack.



        Also, you can create a proposal in the TestCafe repository about improving test logs on BrowserStack. If it receives enough votes, the TestCafe team will consider its implementation.






        share|improve this answer












        The Text Log on BrowserStack shows Selenium commands executed by the browser during a test session. Since TestCafe doesn't use Selenium to perform test actions it must be clear in ideal conditions, but BrowserStack will terminate the session that doesn't send any command within 90 seconds (IDLE TIMEOUT). So TestCafe retrieves the current URL every 80 seconds to work around this timeout.



        To help you identify problematic tests in a recorded video, you can modify TestCafe reporters (e.g., the default spec reporter) to print a precise timestamp when a test starts. You can also modify the BrowserStack browser provider to execute custom Selenium commands that will be added to the Text Log on BrowserStack.



        Also, you can create a proposal in the TestCafe repository about improving test logs on BrowserStack. If it receives enough votes, the TestCafe team will consider its implementation.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 12 at 15:51









        Andrey Belym

        60637




        60637



























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53228025%2ftestcafe-chapters-in-text-log-on-browserstack%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

            𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

            Edmonton

            Crossroads (UK TV series)