NativeScript / NativeScript/nativescript-cli

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

Open
#4,515 20 comments 0 reactions 1 assignee View on GitHub

@Fatme is already working on this.

Since Apr 22, 2019.

unit testing
Dominant language
JavaScript
Stars
1.1k
Forks
204
Avg merge
1d 9h
Merged PRs (30d)
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 :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.