OpenZeppelin / OpenZeppelin/compact-contracts
Enhance the simulator testing artifacts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
We need eventually to not have hardcoded artifacts.
Is it possible to not push the test-artifacts, and instead compile the sample-contracts before testing and get the output on /test-artifacts directory?
Originally posted by @0xisk in https://github.com/OpenZeppelin/compact-contracts/pull/247#discussion_r2465081541
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
Review the simulator test setup and current checked-in artifacts, then trace how the sample-contracts are built before tests run. Done means the sample-contracts compile during testing, their output is placed in /test-artifacts, and hardcoded test artifacts are no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100