OriginProtocol / OriginProtocol/origin-dollar
Smoke test CI integration
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 152
- Forks
- 115
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 17
Description
We are already able to run smoke tests manually using the script.
We would like to add smoke tests as a step in the Continuous Integration. What we probably want to do is:
- check migration.json to determine what deploy scripts have already been ran on the mainnet
- see if the current branch contains a deploy file that is not in
migrations.jsonfile - if there are such files run smoke test agains it
Helper note: there are already helper functions for fetching deployment scripts.
Contributor guide
No contributing guide indexed for this repository
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 with the smoke-test instructions in README.md, the mainnet contracts/deployments/mainnet/.migrations.json file, and the helper functions in contracts/utils/fileSystem.js. Trace how deployment files are identified, then make CI detect branch deploy files absent from migrations.json and run smoke tests for them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, solidity
- Domain
- ci-cd, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100