.travis.yml 파일 작성하기 과정 중에 아무리해도 테스트가 성공이 안됩니다.

.travis.yml 파일 작성 후에 깃 커밋하고

sudo: required

language: generic

services:
  - docker

before-install:
  - echo "start creating an image with dockerfile"
  - docker build -t gonieyoo720/docker-react-app -f Dockerfile.dev .

script:
  - docker run -e CI=true gonieyoo720/docker-react-app npm run test -- --coverage

after_success:
  - echo "Test Success"

트래비스에까지 테스트를 돌렸는데, 몇번을 수정하고 해봐도

트래비스에서 테스트를 통과하지 못하네요.

오타 확인도 많이 해봤는데, 해결을 못하고있습니다.

테스트에 중지되지않은 비동기작업이 있다고 오류를 해결하려면 devDependency를 추가하라는데, 어떻게 해야할까요

--------------------|---------|----------|---------|---------|-------------------
File                | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
--------------------|---------|----------|---------|---------|-------------------
All files           |    8.33 |        0 |   33.33 |    8.33 |                   
 App.js             |     100 |      100 |     100 |     100 |                   
 index.js           |       0 |      100 |     100 |       0 | 7-17              
 reportWebVitals.js |       0 |        0 |       0 |       0 | 1-8               
--------------------|---------|----------|---------|---------|-------------------
Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        2.06 s
Ran all test suites.
Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.
babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.
  
The command "docker run -e CI=true gonieyoo720/docker-react-app npm run test -- --coverage" exited with 1.
Done. Your build exited with 1.

docker-react-app-tests-1  | One of your dependencies, babel-preset-react-app, is importing the
docker-react-app-tests-1  | "@babel/plugin-proposal-private-property-in-object" package without
docker-react-app-tests-1  | declaring it in its dependencies. This is currently working because
docker-react-app-tests-1  | "@babel/plugin-proposal-private-property-in-object" is already in your
docker-react-app-tests-1  | node_modules folder for unrelated reasons, but it may break at any time.
docker-react-app-tests-1  | 
docker-react-app-tests-1  | babel-preset-react-app is part of the create-react-app project, which
docker-react-app-tests-1  | is not maintianed anymore. It is thus unlikely that this bug will
docker-react-app-tests-1  | ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
docker-react-app-tests-1  | your devDependencies to work around this error. This will make this message
docker-react-app-tests-1  | go away.

One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.

babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.