Robolectric 4.9.1+: dejinta proxy ee soo dejinta Android runtime

Robolectric wuxuu soo dejisan karaa artefact-yada Android runtime inta tijaabooyinku socdaan. In qalabka dhisidda uu si guul leh u xalliyo ku-tiirsanaanta caadiga ah ee mashruuca ma caddeyso in soo dejintan waqtiga tijaabada ay isticmaalayso isla proxy-gaas.

Robolectric 4.9.1 iyo kuwa ka dambeeya waxay u diiwaangeliyaan soo-dejiyahan sifooyinkan nidaamka:

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

U gudbi JVM-ga socodsiiya tijaabooyinka. Soo dejinta artefact-ka dadweynaha ee lagu oggolaaday iyada oo loo marayo dhexdhexaadiye HTTP aan la xaqiijin, isticmaal cinwaan ka mid ah liiska proxy-yada HTTP sifooyinkan host-ka iyo port-ka. Mashruuc Android oo isticmaala Groovy DSL-ka Gradle, qaabeynta la xiriirta waxay noqon kartaa:

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

Kani la hay qaabeynta tijaabada ee mashruuca ee jirta. Sifo loo gudbiyay kaliya bilowga Gradle maaha caddayn in JVM tijaabo la farcamay uu helay.

Deegaan tijaabo oo si ula kac ah loo gooyay, Robolectric waxay kaloo diiwaangelisaa robolectric.offline iyo robolectric.dependency.dir. Habayntaas waxay u baahan tahay in artefact-yada runtime ee saxda ah la dhigay galka la cayimay. Kaydka offline-ka ee Gradle laftiisu ma beddelo galka ay filayso xallinta offline-ka ee Robolectric.