Repository navigation
Shared test vectors in bindings tests #1199
Description
I suppose these test vectors really need to come from a common utils library or common fixtures (and perhaps they do in following commits?) because otherwise they all need to be crosschecked in each language.
Originally posted by @DanGould in #1190 (comment)
Reacted by Ben Allen
Activity
spacebear21 commentedon Jan 23, 2026
I tried to do this naively but it highlighted a deeper issue: currently the test utils are re-exported in the top-level namespace in our language bindings. This means that exposing test constants in the FFI test utils would significantly pollute the top-level namespace, e.g.
payjoin.exampleUrl()would live right alongsidepayjoin.ReceiverBuilder().FWIW this is currently already the case with
payjoin.TestServicesbut that struct is at least clearly an isolated test service based on its name.I didn't find a straightforward way to namespace the test utils re-export like
payjoin.testUtils.exampleUrl()but this is something we should probably figure out before 1.0 language bindings releases.