OpenFn/kit

Add more lazy state tests

Open

#840 opened on Dec 9, 2024

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (19 forks)auto 404
DevXgood first issue

Repository metrics

Stars
 (20 stars)
PR merge metrics
 (PR metrics pending)

Description

We have a set of integration tests under execute, which compile and run code without the overhead of the CLI and Worker. It's a really nice way to focus tests on code without worrying about infrastructure.

We don't have many tests at the moment and I'm keen to add more

I'd be really keen to add a while of lazy state tests to the lazy-state file. Simple stuff, advanced stuff, even illegal stuff. I'd like this to be a really comprehensive and definitive listing of lazy state usage.

We should start with very basic tests, which could even be copied from the examples on the docsite. Tests should build up methodically and go onto more complicated stuff.

The examples used here could go on to be used to train AI.

Resources:

Contributor guide

Research direction
Study the existing lazy state test file and the linked documentation to understand the operator's behavior, then write a series of tests from basic to advanced, covering valid and invalid usage.
Tech stack
typescript
Domain
testing
Issue type
Test
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
JavaScript/TypeScriptLazy state operator concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75