serverless/

README

Function Controller Integration Tests

Overview

The project is a test scenario for the Function Controller. It creates a sample Function, exposes it using an APIRule, and sends GET requests to the Function to check if it is accessible from the cluster and outside of the cluster.

Prerequisites

Use the following tools to set up the project:

• Go v1.19
• Kyma CLI

Usage

Run a Local Version

To run integration tests, follow these instructions:

1. Install Serverless.

2. Enable kubectl proxy:

   kubectl proxy
   

3. Run test with given scenario. You can also specify test suite to run. If not specified, all test suites are run within scenario.

   go run cmd/main.go {scenario} --test-suite {test-suite}
   

Environment Variables

Use the following environment variables to configure the application:

Name	Required	Default	Description
APP_TEST_WAIT_TIMEOUT	No	5m	The period of time for which the application waits for the resources to meet defined conditions
APP_TEST_NAMESPACE_BASE_NAME	No	serverless	The name of the namespace used during integration tests
APP_TEST_FUNCTION_NAME	No	test-function	The name of the Function created and deleted during integration tests
APP_TEST_APIRULE_NAME	No	test-apirule	The name of the APIRule created and deleted during integration tests
APP_TEST_TRIGGER_NAME	No	test-trigger	The name of the Trigger created and deleted during integration tests
APP_TEST_SERVICE_INSTANCE_NAME	No	test-service-instance	The name of the ServiceInstance created and deleted during integration tests
APP_TEST_SERVICE_BINDING_NAME	No	test-service-binding	The name of the ServiceBinding created and deleted during integration tests
APP_TEST_SERVICE_BINDING_USAGE_NAME	No	test-service-binding-usage	The name of the ServiceBindingUsage created and deleted during integration tests
APP_TEST_DOMAIN_NAME	No	test-function	The domain name used in the APIRule CR
APP_TEST_INGRESS_HOST	No	kyma.local	The Ingress host address
APP_TEST_DOMAIN_PORT	No	80	The port of the Service exposed by the APIRule in a given domain
APP_TEST_INSECURE_SKIP_VERIFY	No	true	The flag that controls whether tests use verification of the server's certificate and the host name to reach the Function
APP_TEST_VERBOSE	No	true	The value that controls whether tests log resources that are subject to change
APP_TEST_MAX_POLLING_TIME	No	5m	The maximum period of time in which the Function must reconfigure after an update
APP_TEST_KUBECTL_PROXY_ENABLED	No	false	It enables running test locally with kubectl proxy. Run kubectl proxy --proxy 8001 in the background and set the env to true

Development

Install Dependencies

This project uses go modules as a dependency manager. To install all required dependencies, use the following command:

go mod download

Test Flow

Cloud Event Contract Tests

To save a cloud event to memory, Function uses two keys:

• ce-source, identifies what kind of the event was sent: contract-test or runtime name.
• ce-type - type of event: test-binary, test-structured, send-check

The same keys are used to fetch saved cloud events by sending a GET request.

Function emits cloud event when a POST request is sent without cloud event headers.