smartcontractkit / smartcontractkit/chainlink-starknet
Yarn (all) tests should start/tear-down their own env and be idempotent
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 60
- Forks
- 31
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 2
Description
Currently, some project tests expect the network to be running externally before they are started, others don't have that requirement and start their own network programatically on beforeAll.
These two workflows conflict if they are ran together - no network cleanup, port conflict.
Ideally, we provide env access programmatically, so each test suite can manage their own.
Originally posted by @krebernisak in https://github.com/smartcontractkit/chainlink-starknet/pull/93#discussion_r962618953
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Yarn test suites, especially suites that start the network in beforeAll, with those that require an externally running network. Make each suite manage its own environment and verify that all Yarn tests can run together repeatedly without missing cleanup or port conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100