Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat(forge(bin)): Move coverage setup from bin #9039

Open
Tracked by #9012
nhtyy opened this issue Oct 5, 2024 · 0 comments
Open
Tracked by #9012

feat(forge(bin)): Move coverage setup from bin #9039

nhtyy opened this issue Oct 5, 2024 · 0 comments
Labels
A-internals Area: internals A-library Area: library T-feature Type: feature

Comments

@nhtyy
Copy link
Contributor

nhtyy commented Oct 5, 2024

Component

Forge

Describe the feature you would like

Tracked by #9012

Currently, the easiest way to get LCOV data from forge tests in the server is to the run the bin (and sanitize the foundry toml), because alot happens in the bin file

I propose moving it to the lib so its more accessible to users, probably extending the runner

Additional context

No response
@nhtyy nhtyy added T-feature Type: feature T-needs-triage Type: this issue needs to be labelled labels Oct 5, 2024
@nhtyy nhtyy mentioned this issue Oct 5, 2024
Open
4 tasks
@nhtyy nhtyy changed the title feat(forge(bin)): Move LCOV generation from the bin feat(forge(bin)): Move coverage setup from bin Oct 5, 2024
@zerosnacks zerosnacks added A-library Area: library A-internals Area: internals and removed T-needs-triage Type: this issue needs to be labelled labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-internals Area: internals A-library Area: library T-feature Type: feature
Projects
Foundry
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nhtyy @zerosnacks