Unit tests for scripts/*.py

Open
  • Is something wrong?
#8,086 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start with scripts/test_scripts.py and inspect the top-level Python scripts it is meant to cover. Replace the trivial smoke test with unit tests for their behavior, then remove the TODO comment. Run scripts/run-python-tests.sh <path> against the relevant scripts and confirm the new tests pass.

Written by the indexing model from the issue text.

Description

Part of #7987. The top-level scripts/*.py (test file: scripts/test_scripts.py) has only a trivial smoke unit test (added so that scripts/run-python-tests.sh covers it).

Add real unit tests, then replace the TODO comment in the test file.

Run with: scripts/run-python-tests.sh <path>

Dominant language
Scala
Stars
118
Forks
125
Avg merge
22h 35m
Merged PRs (30d)
340

Getting set up

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 canton-network/splice

All issues in canton-network/splice

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.