techgaun/mock

create a lock so tests don't have to worry about being async: false

Open

#6 opened on Oct 8, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (1 fork)github user discovery
enhancementhelp wantedquestion

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

We need to have a process that controls mocking via lock. On every mock, the process will request for lock from this lock handling process. Once the test execution completes, it will release the lock & the next test can do the mocking. Would have to see how feasible it would be and if anything would actually block certain tests to the point it times out?

I am not sure if this will always work for consumers though. For example, anything not mocking will try to access the original module?

Contributor guide

Research direction
Investigate implementing a lock process using GenServer in Elixir. Study how to acquire and release locks for mocking in tests, and evaluate potential blocking issues.
Tech stack
elixir
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ElixirOTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65