NativeScript / NativeScript/nativescript-cli

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

Offen
#4,515 20 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@Fatme arbeitet bereits daran.

Seit 22.4.2019.

unit testing
Vorherrschende Sprache
JavaScript
Sterne
1.1k
Forks
204
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
8

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.