Keep browser open while developing a test in Testcafe

Question

How to keep the browser window open after a test executes in Testcafe?

There was a question on the forum here that brought me to a live Testcafe version, but it seems to be deprecated.

I wish to keep the browser window open to see the elements while I'm developing the test.

Update:

This is my config file:

{
  "name": "testcafe-demo",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "testcafe": "^1.8.2"
  },
  "devDependencies": {},
  "scripts": {
    "test": "testcafe chrome tests/",
    "testcafe": "testcafe"
  },
  "author": "mmrse",
  "license": "ISC"
}

I tried starting the tests from the command line with

E:\testcafe-demo> npm run testcafe chrome demo.testcafe.ts --live

and with

E:\testcafe-demo> npm test chrome demo.testcafe.ts --live

but the result is always the same - after the test is finished, the browser is closed and there is no indication "live" mode was being activated.

Related: https://stackoverflow.com/questions/55105328/testcafe-live-not-running. — Mate Mrše, Mar 02 '20 at 14:23

score 7 · Accepted Answer · edited May 26 '20 at 10:30

7

Features from TestCafe Live were integrated into the main TestCafe product.

See Live Mode for more information.

Make sure to add the --live argument into your script:

  "scripts": {
    "test": "testcafe chrome tests/ --live",
    "testcafe": "testcafe"
  },

And run your tests using npm run test.

Here's another example:

screeshot.js

import { Selector } from 'testcafe';

fixture `My fixture`
    .page `http://devexpress.github.io/testcafe/example/`;

test('Take a screenshot of a fieldset', async t => {
    await t
        .typeText('#developer-name', 'Peter Parker')
        .click('#submit-button')
        .takeScreenshot({
            path:     'my-fixture/thank-you-page1.png',
            fullPage: true
        });
});

Command-line arguments:

testcafe chrome screenshot.js --live

Output:

Using locally installed version of TestCafe.

Live mode is enabled.
TestCafe now watches source files and reruns
the tests once the changes are saved.

You can use the following keys in the terminal:
'Ctrl+S' - stops the test run;
'Ctrl+R' - restarts the test run;
'Ctrl+W' - enables/disables watching files;
'Ctrl+C' - quits live mode and closes the browsers.


Watching the following files:
  c:\Temp\screenshot.js
 Running tests in:
 - Chrome 79.0.3945.130 / Windows 10

 My fixture
 √ Take a screenshot of a fieldset (screenshots: c:\Temp\screenshots\my-fixture\thank-you-page1.png)


 1 passed (5s)

Make changes to the source files or press Ctrl+R to restart the test run.

edited May 26 '20 at 10:30

Mate Mrše

7,997
10
40
77

answered Feb 20 '20 at 08:30

Alex Skorkin

4,264
3
25
47

Hmmm, I added `--live` flag at the end of my command line, but the browser still closes at the end of the test. – Mate Mrše Feb 20 '20 at 08:40
Make sure that you use the latest version (1.8.1+) with the Live mode integrated. – Alex Skorkin Feb 20 '20 at 09:00
I have the 1.8.2. version but still. – Mate Mrše Feb 20 '20 at 09:19
What OS and browser version are you running your tests on? Do you have a testcafe config file? If so, what's inside? – Alex Skorkin Feb 20 '20 at 10:13
Chrome 80.0.3987.116 / Windows 10. I have a basic (default) config file, the only change is the author name. – Mate Mrše Feb 20 '20 at 10:18
I have the same environment. Try to move your config file so that it is not used, and run the example I've added to the answer. What output do you get in the command prompt? – Alex Skorkin Feb 20 '20 at 12:43
Please see my updated question. I never get `Live mode is enabled.` in cmd output. – Mate Mrše Feb 20 '20 at 15:21
What about my example? Did you run it? – Alex Skorkin Feb 21 '20 at 07:38
I did. It runs fine, but not in live mode. – Mate Mrše Feb 21 '20 at 07:44
Please run these commands in your command-prompt using my sample and make a screenshot of the results in the command-prompt: `testcafe -v` `testcafe chrome screenshot.js --live` – Alex Skorkin Feb 21 '20 at 09:13
Also, as a second test, add the '--live' argument into your config directly: "scripts": { "test": "testcafe chrome tests/ --live", "testcafe": "testcafe" }, and run "npm run test" – Alex Skorkin Feb 21 '20 at 09:13
Adding '--live' argument to config script worked! Please add that to your answer and I will accept it. Thanks. – Mate Mrše Feb 21 '20 at 09:24

Keep browser open while developing a test in Testcafe

1 Answers1

Linked