Skip to content

Stop building a separate end_of_support integration test binary for zebrad #6714

Open

Description

Motivation

We currently have a separate test file for end of support tests, which makes cargo link zebrad into two different test binaries. This increases build time and test size on disk.

Specifications

Each file in the tests directory is a separate crate, so we need to bring our library into each test crate’s scope. For that reason we add use adder at the top of the code, which we didn’t need in the unit tests.

https://doc.rust-lang.org/book/ch11-03-test-organization.html#integration-tests

Suggested Solution

Testing

The updated tests should pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    C-cleanupCategory: This is a cleanupC-testingCategory: These are testsE-help-wantedCall for participation: Help is requested to fix this issue.I-slowProblems with performance or responsivenessS-needs-triageStatus: A bug report needs triage

    Type

    Projects

    • Status

      New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions