Robolectric 4.9.1+: izilungiselelo ze-proxy zokulandwa kwe-Android runtime

I-Robolectric ingalanda ama-artifact e-Android runtime ngesikhathi izivivinyo ziqhutshwa. Ukuthi ithuluzi lokwakha lixazulula ngempumelelo izincikamizwa ezivamile zephrojekthi akufakazeli ukuthi lokhu kulanda ngesikhathi sokuhlola kusebenzisa i-proxy efanayo.

I-Robolectric 4.9.1 nezinguqulo ezilandelayo zibhala lezi zakhiwo zesistimu zalowo olandayo:

robolectric.dependency.proxy.host=proxy.example
robolectric.dependency.proxy.port=8080

Zidlulisele ku-JVM eqhuba izivivinyo. Okokulanda ama-artifact omphakathi okuvunyelwe ngesixhumanisi se-HTTP esingaqinisekisiwe, sebenzisa ikheli elivela kuhlu lwe-proxy ye-HTTP kulezi zakhiwo ze-host ne-port. Ephrojekthini ye-Android esebenzisa i-Groovy DSL ye-Gradle, ukulungiselelwa okuhambisanayo kungaba:

android {
    testOptions {
        unitTests.all {
            systemProperty 'robolectric.dependency.proxy.host', 'proxy.example'
            systemProperty 'robolectric.dependency.proxy.port', '8080'
        }
    }
}

Gcina lokhu kanye nokulungiselelwa kwezivivinyo okukhona kwephrojekthi. Isakhiwo esinikezwa kuphela isiqalisi se-Gradle akusona ubufakazi bokuthi i-JVM yokuhlola ehlukanisiwe isitholile.

Ngokwemvelo yokuhlola enqanyuliwe ngamabomu, i-Robolectric ibhala futhi robolectric.offline ne robolectric.dependency.dir. Lokho kulungiselelwa kudinga ukuthi ama-artifact e-runtime afanele abekwe kudayirekithari ebekiwe. Ingqoloyi ye-offline ye-Gradle ngokwayo ayithathi indawo yedayirekithari elindelwe isixazululi se-offline se-Robolectric.