bitcoindevkit/bdk-dart

test: add Wallet.keychains() Dart binding smoke coverage

Open

#104 opened on Jul 2, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Dart (17 forks)auto 404
good first issuetesting

Repository metrics

Stars
 (11 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Add a small Dart-side smoke test for the generated Wallet.keychains() binding.

This is not intended to retest wallet keychain behavior owned by bdk-ffi. The goal is only to prove the regenerated Dart binding path is callable and that List<WalletKeychain> lifts into usable Dart objects. Wallet.keychains() came in through #101, and the current Dart test suite does not call this generated path today.

Scope

  • Call wallet.keychains() from Dart on a standard wallet.
  • Assert the returned list is non-empty.
  • Assert each returned WalletKeychain exposes a usable keychain.
  • Assert each returned WalletKeychain.publicDescriptor can be converted to a descriptor string.
  • Keep assertions thin and focused on Dart binding usability.

Contributor guide

Research direction
Create a Dart test that calls wallet.keychains(), asserts the returned list is non empty, and checks that each WalletKeychain has a usable keychain and publicDescriptor property.
Tech stack
dart
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DartGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90