Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit tests execution in Windows reports error #590

Open
pboychev-bcom opened this issue Jan 9, 2025 · 0 comments
Open

Unit tests execution in Windows reports error #590

pboychev-bcom opened this issue Jan 9, 2025 · 0 comments
Labels
area/tests Relates to tests and code coverage kind/bug Something isn't working priority/high triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change

Comments

@pboychev-bcom
Copy link
Contributor

Description

Running the unit tests for a project reports an error in Windows even if there is no such thrown.
The error indicates the process triggered for running the unit tests has exited with an error exit code.

Steps to Reproduce

  1. Create a TypeScript module / project.
  2. Write unit tests for the project.
  3. Run the unit tests / build the project.

Preconditions:
The build / unit tests execution should be triggered under Windows.

Expected behavior:
The tests are passing successfully.

Actual behavior:
The tools are reporting an error like the following:

Error occurred in unit tests execution: null

Reproduces how often:
Every time.

Component/s:
vrotest

Affects Build/s:
3.0.0, 3.1.0, 3.1.1

Client

Rabobank

Proposed changes

We should check if the spawned process exists with exit code 0 (number) or "True" (string) to support both Unix and Windows based workstations.

@VenelinBakalov VenelinBakalov added kind/bug Something isn't working version/minor Introduces a non-breaking feature or change area/tests Relates to tests and code coverage triage/accepted The issue was accepted and will be done priority/high labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tests Relates to tests and code coverage kind/bug Something isn't working priority/high triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change
Projects
None yet
Development

No branches or pull requests

2 participants