#kni — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kni, aggregated by home.social.
-
#Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?
Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?
All solutions we’ve tried/considered so far kinda feel bad.
(I'm mostly dealing with C/C++ and Kotlin)
-
#Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?
Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?
All solutions we’ve tried/considered so far kinda feel bad.
(I'm mostly dealing with C/C++ and Kotlin)
-
#Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?
Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?
All solutions we’ve tried/considered so far kinda feel bad.
(I'm mostly dealing with C/C++ and Kotlin)
-
#Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?
Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?
All solutions we’ve tried/considered so far kinda feel bad.
(I'm mostly dealing with C/C++ and Kotlin)
-
#Android friends, how do you unit test your #JNI / #KNI code? Do you write extra KNI glue just so you can trigger internal native methods that call back out into #Kotlin?
Do you restrict yourself to only integration tests and black-box tests and just *not* unit-test this stuff?
All solutions we’ve tried/considered so far kinda feel bad.
(I'm mostly dealing with C/C++ and Kotlin)