square/workflow-kotlin

Support explicit expectation of no worker running

Open

#653 opened on Jan 31, 2022

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Kotlin (114 forks)github user discovery
enhancementgood first issuetesting

Repository metrics

Stars
 (1,120 stars)
PR merge metrics
 (Avg merge 55d 8h) (9 merged PRs in 30d)

Description

Right now there is no easy way to expect that some particular worker is not running during the given render step. There is a workaround to use requireExplicitWorkerExpectations, but it requires to specify the footprint for the rest of the workers.

Proposal: add methods like expectNoWorker/expectNoWorkerOutputting that will do the work complementary to expectWorker/expectWorkerOutputting by checking non-existence of a single worker with specific footprint.

Contributor guide

Research direction
Examine the existing 'expectWorker' and 'expectWorkerOutputting' methods in the test utilities, understand their implementation, and create complementary methods 'expectNoWorker' and 'expectNoWorkerOutputting' that verify the absence of a specific worker footprint.
Tech stack
kotlin
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Kotlin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70