Optum / Optum/runiac

Getting error "exec: 'gotestsum': executable file not found in $PATH"

Open
#52 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
24
Forks
19
Avg merge
11m
Merged PRs (30d)
2

Description

I'm experimenting with unit tests in my terraform step, but when I execute Runiac it reports that a test has been found but after the step runs and it tries to execute the test I'm getting the error "exec: 'gotestsum': executable file not found in $PATH".

Here's the log before the error:

Running command: gotestsum --format standard-verbose --junitfile /output/junit/azure-hello-world-default-namespace-primary-centralus.xml --raw-command -- test2json -p azure-hello-world-default-namespace-primary-centralus ./tests.test -test.v.
EnvVars: [TF_VAR_runiac_step, TF_VAR_runiac_region_group, TF_VAR_runiac_target_account_id, TF_VAR_runiac_project, TF_VAR_runiac_region_deploy_type, TF_VAR_runiac_account_id, TF_VAR_runiac_region, TF_VAR_runiac_track, TF_VAR_runiac_primary_region, TF_VAR_runiac_namespace, TF_VAR_runiac_deployment_ring, TF_VAR_runiac_app_version, TF_VAR_runiac_environment]

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.

Research direction

Start by locating the Runiac code that assembles the logged gotestsum command and configures the test step environment. Reproduce the Terraform-step invocation, then trace how the executable is resolved from PATH; done means the reported test command runs successfully or produces a clear configuration error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, terraform
Domain
devops, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.