Tushen tabbatar da wakili don buƙatar REST Assured

REST Assured yana da ƙayyadaddun wakili wanda ke ɗaukar adireshin mai shiga tsakani da bayanan shigarsa tare:

import static io.restassured.RestAssured.given;
import io.restassured.specification.ProxySpecification;

var proxy = ProxySpecification.host("proxy.example")
    .withPort(8080)
    .withScheme("http")
    .withAuth(proxyUser, proxyPassword);

var request = given().proxy(proxy);

Aikace-aikacen yana bayar da proxyUser da proxyPassword daga tushen bayanan shigarsa na yau da kullum. Wannan ɓangaren yana gina ƙayyadaddun buƙata; ka kira URL ɗin API da ake nufi ta request da kodin buƙata da tabbatarwa na yau da kullum na gwajin.

Tsarin http yana bayyana ƙarshen wurin wakilin. URL ɗin API na iya kasancewa HTTPS. Tsarin withAuth na REST Assured yana bayar da tabbatar da wakili na asali; ba ya yin shawarwari da kowace tsarin tabbatarwa na kamfani kawai saboda an bayar da igiyoyi biyu.

Ka sanya bayanan shigar API a cikin saitin tabbatar da API ɗin kansa. Ka guji maye gurbin asusun wakili da kanun Authorization na gama-gari ko da kalmar sirrin sabis. A HTTPS, ana iya buƙatar tabbatarwa ga mai shiga tsakani yayin kafa CONNECT, kafin musayar HTTP da makoma ta kasance.

Lokacin da sauran gazawar ita ce amincewa da takarda

Ƙalubalen CONNECT da aka ƙi da kuskuren tabbatar da takardar TLS sakamako ne daban-daban. Idan CA da ƙungiyar ke sarrafawa da ake buƙata ba ya cikin tsarin amincewar abokin ciniki, sami wannan CA ta hanyar gudanarwa da aka amince da ita sannan ka saita truststore na abokin cinikin gwajin.

REST Assured yana bayyana trustStore don wannan manufa. Truststore yana canza waɗanne masu bayarwa ne abokin ciniki na HTTPS ya amince da su; ba ya zaɓar wakilin kuma ba ya bayar da shigarsa. Ka ci gaba da kunna tabbatar da sunan mai masauki da takarda maimakon yin amfani da musafaha na accept-all don karɓar duk wata takadda da aka gabatar.