Testing Scenarios

You have different test scenarios based on the type of Service in a Sandbox and where the Endpoint URL points to.

Test Type	Service in Sandbox	Endpoint URL Points To	Test Client	Pre-Requisites
Service API	Backend Service exposing http or gRPC API	A backend service	API testing libraries or tools like curl, postman or BloomRPC	None
End-to-End	Frontend Service like a Web UI	A frontend service	A Web Browser	None
End-to-End	Backend Service	A frontend service	A Web Browser	Header Propagation

All generated Endpoint URLs are authenticated. You will need to pass in an API Key as explained below.

Using Endpoint URLs pointing to frontend Services

If the endpoint URL is pointing to a frontend Web Application, you can load it up in your web browser and authenticate to it just as you log into the Signadot Dashboard and gain access to your service in the sandbox.

Using Endpoint URLs pointing to backend Services using http

You can also access backend URLs over http(s) using cURL or Postman for manual testing. This requires that you provision an API key from the Signadot Dashboard, and then issue a request with the signadot-api-key header as shown below.

curl -H "signadot-api-key: <api-key-here>" https://<endpoint>--<sandbox-name>.preview.signadot.com

Using Endpoint URLs pointing to backend Services using gRPC

For gRPC requests, the service running within the cluster must be accessible without encryption or authentication. The gRPC endpoint itself is secured using TLS and can be connected to at <full-endpoint-url>:443 with the server authentication using SSL/TLS. The certificate issued to the endpoint URL is authenticated by a public CA, so, it can be validated using default CA certificates included in your system. gRPC requests also require a Signadot API key to invoke. An example request using grpcurl is shown below.

grpcurl -vv \
    -H 'signadot-api-key: ...' \
    -d '{"context_words": ["cookware"]}' \
    <endpoint>--<sandbox-name>.preview.signadot.com:443 service.someService/Method