getBrowserConsoleMessages returns undefined in 1.8.0

[sorin-davidoi]

What is your Test Scenario?

Load a simple page and fetch the console messages.

What is the Current behavior?

test.getBrowserConsoleMessages() returns undefined or null.

What is the Expected behavior?

It should return the console messages.

What is your web application and your TestCafe test code?

Your complete test code (or attach your test files):

fixture`Test`;

test
    .page('https://duckduckgo.com')
    ('test', async test => {
        const { error, warn, log, info } = await test.getBrowserConsoleMessages();
    });

Your complete configuration file (if any):

Your complete test report:

Test
 ✖ test

   1) TypeError: Cannot destructure property `error` of 'undefined' or 'null'.

      Browser: Firefox 72.0 / macOS 10.15

         1 |fixture`Test`;
         2 |
         3 |test
         4 |    .page('https://duckduckgo.com')
         5 |    ('test', async test => {
       > 6 |        const { error, warn, log, info } = await test.getBrowserConsoleMessages();
         7 |    });
         8 |

         at Object.<anonymous> (/Users/sorindavidoi/Repositories/HTML-Client/test.ts:6:15)
         at fulfilled (<redacted>test.ts:3:58)
         at $$testcafe_test_run$$flJkbqpN0$$
      (<redacted>/node_modules/testcafe/src/api/test-run-tracker.js:76:16)
         at $$testcafe_test_run$$flJkbqpN0$$
      (<redacted>/node_modules/testcafe/src/api/test-run-tracker.js:76:16)

Steps to Reproduce:

See test file.

Your Environment details:

• testcafe version: 1.8.0
• node.js version: v12.14.1
• command-line arguments: firefox test.ts
• browser name and version: Firefox 72
• platform and version: macOS 10.15
• other:

This is a regression in 1.8.0 - it does not happen in 1.7.1.

[miherlosev]

Hi @sorin-davidoi

I've reproduced the problem. Thank you for the provided information.

[miherlosev]

Fixed in #4664

[lock]

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.