Skip to content

chore: Committer package should be unit tested #3426

@SimonTheLeg

Description

@SimonTheLeg

The commiter package is untested via unit tests. While some of the code is reached using E2E tests, I strongly believe funcs like generatePatchAndSubResources and withPatchAndSubResources can be tested pretty staight forward with a dedicated unit test and should definitely be tested. Additionally the code can panic in a pretty inconvenient spot, which I think is not ideal either.

I think this is especially important since, we use committers quite regulary in our code:

Image

This task is mainly a placeholder so I don't forget to work on it, while working on another task :)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions