square/workflow-kotlin

testRender should be lenient about side effects like it is about workers.

Open

#624 opened on Jan 11, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Kotlin (114 forks)github user discovery
good first issue

Repository metrics

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

Description

Need to be thoughtful about rolling it out, though, since we'd change semantics on existing tests pretty drastically. Maybe that's fine?

Contributor guide

Research direction
Review the implementation of testRender to understand current handling of workers and determine how to extend leniency to side effects.
Tech stack
kotlin
Domain
mobile dev
Issue type
Test
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Kotlin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55