Prepare mock server to test out client side implementation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 399
- Forks
- 185
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
This aims to test out client logic - e.g. if a new selenium version causes this client's implementation issue.
Each Appium driver has its own integration tests with emulators/simulators to test driver-side behavior, so this issue doesn't aim to test driver-side behavior - except for appium server/driver process handling code. Instead, we may need to have a way to test incoming/outgoing http requests, and internal implementation logic to run them faster
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
The issue names no files or tests. Start by scoping a mock-server approach for client-side HTTP requests, internal request logic, and Appium server/driver process handling while excluding driver-side behavior; done requires a defined way to run these tests faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100