carols10cents/cargo-open

Add a test for getting the directory of a crate that is a dependency of a dependency

Open

#6 opened on Oct 4, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (21 stars) (5 forks)user submission
E-easyhelp wanted

Description

In main.rs, add a unit test for the cargo_dir function that checks that it returns the correct source code directory for a crate that is a dependency of a crate that is a top-level dependency.

For example, clap is one of this project's top-level dependencies, and ansi_term is one of clap's dependencies. So if we run cargo_dir("ansi_term") in the context of this project, we should get the correct source code directory for ansi_term even though it's not in the Cargo.toml file directly.

Contributor guide

Tech stack
rust
Domain
testingtooling
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust basicsUnit testing with #[test]Cargo dependency graph
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the existing test setup in `src/main.rs` (if any) and the implementation of `cargo dir`. Understand how `cargo metadata` can be used to resolve transitive dependencies. Write a test that calls `cargo dir` with a crate like `ansi term` and asserts the returned path is correct. Refer to the `Cargo.lock` file to find the exact version and location.