haskell-distributed / haskell-distributed/distributed-process
Should we have integration tests that use separate executables?
Open
Nobody has claimed this yet.
Question
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
This is quite awkward to set up in travis, though on my local machine using a docker image it seems to work fine. Might be an additional use case for the next major version.
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 existing tests. Start by reviewing the Travis setup and the local Docker-based reproduction, then determine the scope for integration tests using separate executables and what support for the next major version would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, haskell
- Domain
- ci-cd, distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100