Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add `cargoTest` task

Open
  • Is something wrong?
#67 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kotlin, rust
Domain
build-system, testing

Research direction

Start by locating the existing Gradle tasks and the rust-android-gradle exec option, then trace how task dependencies and environment variables are passed to Rust builds. Done means the repository's Gradle test runner can invoke cargo test after the required static libraries are built and with the needed environment variables available.

Written by the indexing model from the issue text.

Description

It might make sense to allow running cargo test via a Gradle task. My particular use case requires this because

  • My Rust code depends on static libraries built in another gradle task
  • My build.rs relies on extra environment variables provided injected via rust-android-gradle's exec option to compile properly
  • The repo's test runner is configured to interface with gradle already, so it makes sense to add the Rust tests there too
Dominant language
Kotlin
Stars
1.3k
Forks
95
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/rust-android-gradle

All issues in mozilla/rust-android-gradle

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.