NativeScript / NativeScript/nativescript-cli

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

Ouverte
#4,515 20 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@Fatme y travaille déjà.

Depuis le 22/4/2019.

unit testing
Langage dominant
JavaScript
Étoiles
1.1k
Forks
204
Merge moyen
1 j 9 h
PR mergées (30 j)
8

Description

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 :)

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.