e2e test: create a new container to hold all testing utilities like ffmpeg/MistLoadTest/MistAnalyser*
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
It was evident from https://github.com/livepeer/catalyst/pull/54 that we need a third container that launches all tester binaries instead of relying on the CI host to have certain dependencies fulfilled. A workaround was used for the linked PR to copy over the relevant binaries required for load-testing into the CI host. These binaries should instead live in their own containers.
Contributor guide
No contributing guide indexed for this repository
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
Review the e2e setup and the workaround described in PR #54, then identify where the CI host currently receives ffmpeg, MistLoadTest, and MistAnalyser binaries. Done means a separate container launches the tester binaries and the end-to-end load tests no longer depend on those dependencies being installed on the CI host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100