inso cli in docker not running test that works in inso cli
- Dominant language
- TypeScript
- Stars
- 40k
- Forks
- 2.4k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
### Expected Behavior
`docker run -it --rm -v $(pwd):/var/temp kong/inso:latest run test -w /var/temp/ --src /var/temp/`
should have the same behaviour than
`inso run test` and run the test
### Actual Behavior
inso run test actually run test:
`inso run test --disableCertValidation
✔ Select a document or unit test suite · demoTestSuite - uts_f32a40
✔ Select an environment · demoEnv- env_7dc2bca518
[db] No workspace parentId found for wrk_234e9e1dab4f4cac87077dd6e9bb8507 setting default proj_default-project
demoTestSuite
✔ FindTestShouldRetrieve200 (893ms)
1) GetAddressShouldRetrieve404
✔ GetTestShouldRetrieve200 (127ms)
2 passing (1s)
1 failing
1) demoTestSuite
GetShouldRetrieve404:
AssertionError: expected 500 to equal 404
+ expected - actual
-500
+404
at Context. (/tmp/insomnia-testing/0.4643974702769973-test.ts:20:33)`
but docker image stop after selecting environement and does not return test result
`
docker run -v /mnt/c/Users/xxxxx/AppData/Roaming/Insomnia/:/var/temp -it --rm kong/inso:latest run test --src /var/temp
✔ Select a document or unit test suite · demoTestSuite - uts_f32a40
✔ Select an environment · demoEnv- env_7dc2bca518
demoTestSuite
`
### Reproduction Steps
have a insomnia document with a gitsync and some test running (or failling ) on insomnia
run it with inso cli and get a test report
run it with docker inso image and test look not running
### Is there an existing issue for this?
- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Additional Information
in CI working with a docker image allow to use inso in gitlab runner easily
### Insomnia Version
2023.5.6
### What operating system are you using?
Windows
### Operating System Version
microsoft-standard-WSL2 x86_64 GNU/Linux
### Installation method
apt-get install insomnia
### Last Known Working Insomnia version
not applicable
Contributor guide
Research direction
Start by comparing the `inso run test` entry point with the `kong/inso:latest` Docker command using the reproduction steps and mounted workspace. Done means the Docker invocation runs the selected test suite and returns its test results, including failures, rather than stopping after environment selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- cli, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100