karma-runner / karma-runner/karma
Can karma be started in an independent server?
- Dominant language
- JavaScript
- Stars
- 12k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm with some projects in hands and one of them (called _Neck_) is a transporter of tests and their resources for browser or other kind of heads/workers.
_Neck_ is currently in a _WIP_ state but its paused until we have a _requirehit_ production-ready version (could say its some sort of _webpack_ but in fact it is quite different).
On _Neck_ we call our _workers_ as **Heads** and they aren't attached to a specific project at all, when a test job is launched, it transports resources to them and gathers responses.
I was happy to hear about _karma_, it seems a lot interesting and we could not only start using but also contribute to it and discard Neck from our milestones in case it matches our needs.
My question is: is there any chance to have browsers connected to a **karma http server** without having to run them from project's folder?
The reason why I am questioning this is that I would like to create a **karma server** from a docker container (within our CI Server) and trigger **karma run**s on each test job on different projects, which are runt from another server inside another docker container.
Contributor guide
Research direction
No files or tests are named. Start by tracing the karma http server and karma run entry points, then determine whether a server in one Docker container can accept browser and test jobs launched from another project container. Done should define the supported independent-server workflow and its cross-container behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100