Problem: missing basic integration tests in CI

Open
#201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
ci-cd, testing

Research direction

Start with scripts/develop_experiments/develop_scripts.md to understand the referenced testing approach and identify the relevant integration-test and CI entry points. Add a simple end-to-end test composing stream A and stream B into stream C, then ensure that test runs successfully in CI.

Written by the indexing model from the issue text.

Description

Problem: missing basic integration tests in CI

Pre-seed data was also helpful in ensuring that our streams worked e2e. However, we don't > need that complexity: simple stream A + B -> composed C tests would ensure it works.

Originally posted by @outerlook in https://github.com/truflation/tsn/issues/200#issuecomment-2098498548

See https://github.com/truflation/tsn/blob/main/scripts/develop_experiments/develop_scripts.md for a reference of how we could test.

Dominant language
Go
Stars
7
Forks
3
Avg merge
3h 2m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

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.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.