Mocking HTTP requests without in-process feature
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 966
- Forks
- 162
- Avg merge
- 18h 51m
- Merged PRs (30d)
- 8
Description
Summary
I have read that using in-process feature is one solution to be able to mock HTTP requests.
https://github.com/erikhuda/thor/wiki/Integrating-with-Aruba-In-Process-Runs
But as described in:
- https://github.com/cucumber/aruba/issues/199
- https://github.com/cucumber/aruba/pull/159
It is not possible to have both interactive CLI and use in-process feature.
Context & Motivation
I am using Thor on a gem that provides some commands to request information from a server. For example, when running a command I ask the user to choose between a set of servers available (thus interaction) and returns the requested information.
Current Behavior
To test my commands I tried using the in-process feature as described here https://github.com/erikhuda/thor/wiki/Integrating-with-Aruba-In-Process-Runs
which works fine to mock HTTP requests but fails as soon as there's interaction with CLI.
Expected Behavior
I would like to find a solution to have both mocking HTTP requests and using interactive CLI Aruba features like type('something')
Your Environment
rspec 3.6.0
aruba 0.14.2
webmock 3.0.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Aruba in-process integration wiki page, issue 199, and pull request 159, then inspect how interactive CLI input such as type('something') is handled alongside HTTP mocking. Done means documenting or implementing a supported way to combine interactive Aruba features with mocked requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100