bitcoindevkit / bitcoindevkit/bdk-dart

test: smoke test Dart full-scan binding call path

Open
#106 2 comments 0 reactions 0 assignees View on GitHub
testing
Dominant language
Dart
Stars
13
Forks
20
Avg merge
24m
Merged PRs (30d)
3

Description

### Description
Add a narrow Dart-side smoke test for the generated full-scan binding path.

This is not intended to test Electrum/Esplora scan semantics or wallet discovery behavior. Those belong in `bdk-ffi`. The goal here is only to prove that the Dart-generated full-scan request/update path is callable and that the returned FFI objects lift into usable Dart objects.

Current Dart integration tests exercise `startSyncWithRevealedSpks()` and backend `sync_()`, but they do not call the generated full-scan path from Dart.

### Scope
- Build a wallet in Dart.
- Call `wallet.startFullScan().build()`.
- Pass the resulting `FullScanRequest` through one env-gated backend full-scan call.
- Assert the returned `Update` object lifts successfully and can be passed to `wallet.applyUpdate(...)`.
- Keep assertions limited to Dart binding callability and object usability.

Contributor guide

Open the contributing guide

Research direction

Start with the existing Dart integration tests covering startSyncWithRevealedSpks() and backend sync_(), then trace the generated wallet.startFullScan().build() path. Add an environment-gated backend full-scan call, verify the returned Update lifts into a usable Dart object, and pass it to wallet.applyUpdate(...).

Written by the indexing model from the issue text.

Assessment

Tech stack
dart
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.