Robolectric na iya sauke kayan aikin Android runtime yayin da gwaje-gwaje ke gudana. Samun kayan aikin gini ya warware dogaron yau da kullum na aikin cikin nasara ba ya tabbatar da cewa wannan saukewar a lokacin gwajin tana amfani da wakili ɗaya.

Robolectric 4.9.1 da na baya sun rubuta waɗannan kaddarorin tsarin ga mai saukar da ke:

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

Miƙa su ga JVM ɗin da ke gudanar da gwaje-gwajen. Don sauke kayan aiki na jama'a da aka yarda ta hanyar mai shiga tsakani na HTTP mara tabbaci, yi amfani da adireshi daga jerin wakilan HTTP a cikin waɗannan kaddarorin mai masauki da tashar. Don aikin Android da ke amfani da Groovy DSL na Gradle, saitin da ya dace zai iya zama:

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

Riƙe wannan tare da saitin gwajin aikin da ake da shi. Kaddarar da aka ba mai ƙaddamar da Gradle kawai ba hujja ba ce cewa JVM ɗin gwajin da aka raba ya karɓa.

Don yanayin gwajin da aka cire haɗi da gangan, Robolectric kuma ya rubuta robolectric.offline da robolectric.dependency.dir. Wannan tsarin yana buƙatar a ajiye ingantattun kayan runtime a cikin jagorar da aka ƙayyade. Taskar offline ta Gradle kanta ba ta maye gurbin jagorar da mai warwarewar offline na Robolectric ke tsammani.

Labarai masu alaƙa