NativeScript / NativeScript/nativescript-cli

Unable to run unit tests in CI on an Android emulator running on Genymotion SaaS

Aberta
#4,515 20 comentários 0 reações 1 responsável Ver no GitHub

@Fatme já está trabalhando nisso.

Desde 22/4/2019.

unit testing
Linguagem predominante
JavaScript
Estrelas
1.1k
Forks
204
Merge médio
1d 9h
PRs com merge (30d)
8

Descrição

Environment

  • CLI: 5.4.0-2019-03-21-13075
  • Cross-platform modules: 5.3.0
  • Android Runtime: 5.2.1
  • iOS Runtime: 5.2.0
  • Plugin(s):

Describe the bug

We're using Genymotion SaaS to spin up emulators to run tests on CI. I got it wired up to start the emulators and tns test android is able to install the app on the emulator but tests don't actually run. I get the following output.

Screen Shot 2019-04-08 at 6 07 56 PM

You should be able to see the entire log by going to https://circleci.com/gh/resideo-platform/exemplar/3033?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link

Note: the emulators runs on a remote server. I have to forward any port from remote emulator to the local host. There is an error about not being able to connect to a port: Error is: connect ECONNREFUSED 127.0.0.1:43108.. I tried to open a port but it changes every time that the test run. I haven't been able to track down what this port is used for.

To Reproduce

I believe you should be able to reproduce this issue by starting a remote emulator where the testing port needs to be explicitly opened.

Expected behavior

I'm not sure if the tests are failing to run because the port is not open, but if it is then I'd expect the port to be stable. At least, it should be possible to specify the port that's used so I can open that port.

Sample project

The entire project is available in the repo https://github.com/resideo-platform/exemplar/pull/61

Additional context

Thank you :)

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.