How to run functional tests in build script?

[janhesters]

** Please describe which feature you have a question about? **
I'm trying to run functional tests with TestCafe when building. Here are my build settings:

version: 0.1
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
        - yarn validate
    build:
      commands:
        - yarn run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

And here is how the "validate" script looks like:

"validate": "yarn -s unit-tests && yarn -s lint && yarn -s functional-tests",
"functional-tests": "testcafe 'chrome:headless' src/functional-tests/",

But this throws the error:

2019-08-08T15:36:17.385Z [WARNING]: ERROR Unable to find the browser. "chrome:headless" is not a browser alias or path to an executable file.

How can I add Chrome to the Amplify console, or run functional tests with it?

** Provide additional details**

[garyleefight]

@janhesters You have to install the missing dependency yourself. You can add commands to install chrome dependencies in prebuild.

[janhesters]

@garyleefight Do you know which dependencies and how to install them exactly?

I can't find how to install chrome for the Amplify console. I only found this, which tackles docker. And these Google docs are for Travis CI. As far as I can tell, there is no addons key for the Amplify build settings.

[garyleefight]

@janhesters https://stackoverflow.com/questions/44516816/install-chrome-headless-using-npm
Hope it helps.

[janhesters]

@garyleefight Thank you for your help. Managed to solve the install problem by adding

- wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
- yum install -y ./google-chrome-stable_current_*.rpm

to my build settings.

My question is now: How can I run yarn start so that the tests can pass? Currently the functional tests run, but fail, because no server is running.

[garyleefight]

@janhesters You can use https://stackoverflow.com/questions/30950032/how-can-i-run-multiple-npm-scripts-in-parallel concurrently package to run yarn start and your test command in parallel.
It will kill yarn start when your test commands finished. But the exit code is 1, which is considered build failure in our console.
You can read this post to get rid of exit code 1.
https://github.com/kimmobrunfeldt/concurrently/issues/127

Hope it works for you.

Besides, AWS Amplify Console baked Cypress test in the default image. You can choose it as an alternative selection.

Thanks,
Gary

[janhesters]

@garyleefight

You can use https://stackoverflow.com/questions/30950032/how-can-i-run-multiple-npm-scripts-in-parallel concurrently package to run yarn start and your test command in parallel.
It will kill yarn start when your test commands finished. But the exit code is 1, which is considered build failure in our console.
You can read this post to get rid of exit code 1.
kimmobrunfeldt/concurrently#127

Thank you I will try concurrently.

I also found the --app flag for TestCafe which does exactly what I want (= run yarn start when the test starts, and terminate the app afterwards). But, for some reason if I test in headless mode in the console or locally, the tests fail. I created a SO question here.

Besides, AWS Amplify Console baked Cypress test in the default image. You can choose it as an alternative selection.

Really? I didn't know that and could'n find anything in the docs about this. Do Cypress tests "just work"? Or is there extra configuration needed.

[janhesters]

I got it working by adding a delay to launch the app.

"functional-tests": "testcafe 'chrome:headless' src/functional-tests/ --app 'yarn start' --app-init-delay 4000",

[rudyhadoux]

@janhesters Do you know the npm lib start-server-and-test (no need to add delay) ?
I achieve same tests with
start-server-and-test angular-http-server --path ./dist/site -p 4200 http://localhost:4200 testcafe chrome:headless ./testcafe/test.js

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.