OpenFn / OpenFn/kit-lightning-integration

Add Provisioner / Sync Tests

Open
#19 0 comments 0 reactions 1 assignee View on GitHub

@doc-han is already working on this.

Since Sep 16, 2026.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
1d 10h
Merged PRs (30d)
10

Description

The most important thing to test in the integration suite, the least well tested part of the platform, is sync through the provisioner API.

Areas to test:

  • create new project
  • update project
  • remove stuff (workflow, steps, channels, credentials)

We probably need a "canonical" project file which has every key in it.

Considerations:

  • Do we need tests with v1 and v2? They both use the provisioner API the same way... but we do need to ensure that both versions build the state object correctly (and this is a big area of problems). So ideally the test would be like "create a new project" and it would run for v1 and v2. Let's start by duplicating tests manually, then maybe think about some automation later (it would be ideal to set up tests with a v2 project spec file, then use automation to run commands through v1 and v2)
  • what are we asserting against? Do we check the lightning database? Do we post and then fetch? Do we post and assert on the returned project state? Maybe that last one?

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.