https://github.com/0xjepsen/testdrive
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.6%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: 0xJepsen
- Language: Rust
- Default Branch: master
- Size: 188 KB
Statistics
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 3
- Releases: 0
Metadata Files
README.md
Foundry Rust Monorepo Template
Template for quickly getting started with developing Rust applications that leverage Foundry for EVM smart contract development.
Continuous Integration is already set up to test both your Rust and Solidity code, as well as ensure formatting and that your Rust bindings match the Solidity build artifacts.
Directory Structure
The project is structured as a mixed Rust workspace with a Foundry project under
contracts/ and typesafe auto-generated bindings to the contracts under
bindings/.
├── Cargo.toml
├── app // <-- Your Rust application logic
├── contracts // <- The smart contracts + tests using Foundry
├── bindings // <-- Generated bindings to the smart contracts' abis (like Typechain)
Testing
Given the repository contains both Solidity and Rust code, there's 2 different workflows.
Solidity
Forge is using submodules to manage dependencies. Initialize the dependencies:
bash
forge install
If you are in the root directory of the project, run:
bash
forge test --root ./contracts
If you are in in contracts/:
bash
forge test
Rust
cargo test
Generating Rust bindings to the contracts
Rust bindings to the contracts can be generated via forge bind, which requires
first building your contracts:
forge build --root ./contracts
forge bind --bindings-path ./bindings --root ./contracts --crate-name bindings
Any follow-on calls to forge bind will check that the generated bindings match
the ones under the build files. If you want to re-generate your bindings, pass
the --overwrite flag to your forge bind command.
Installing Foundry
First run the command below to get foundryup, the Foundry toolchain installer:
sh
curl -L https://foundry.paradigm.xyz | bash
Then, in a new terminal session or after reloading your PATH, run it to get
the latest forge and cast binaries:
sh
foundryup
For more, see the official docs.
Owner
- Name: Jepsen ✨
- Login: 0xJepsen
- Kind: user
- Location: Somewhere in meatspace
- Website: https://www.networkspirits.com/
- Twitter: 0xjepsen
- Repositories: 12
- Profile: https://github.com/0xJepsen
Creating Biodigital Jazz
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: about 1 year ago
All Time
- Total issues: 0
- Total pull requests: 7
- Average time to close issues: N/A
- Average time to close pull requests: 3 months
- Total issue authors: 0
- Total pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 4
- Bot issues: 0
- Bot pull requests: 7
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
- dependabot[bot] (6)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- 278 dependencies
- actions/checkout v2 composite
- onbjerg/foundry-toolchain v1 composite
- Swatinem/rust-cache v1 composite
- actions-rs/toolchain v1 composite
- actions/checkout v2 composite