ruby / ruby/mspec

Improve communication of parallel mspec

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
66
Forks
66
PR merge metrics
No merged PRs in 30d

Description

This would allow to report errors as they are observed and be more flexible.
Currently, errors are delayed until the end as they are dumped into a YAML file.
This will need an improved protocol between the master mspec and the sub-processes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the master mspec and subprocesses currently communicate and where errors are dumped into the YAML file. Define the improved protocol around reporting errors as they are observed, then verify that parallel runs communicate failures before completion without relying only on the final dump.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.