c14f768971
* Change event type in Sequence with Broker example (#2897) (#2916) If the type of the event isn't changed by the last step in the sequence the event will be resent to the Trigger that targets the sequence creating an unwanted loop. Fixes #2851 Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com> * Reworked shell hello world example * Reworked example to be a "true" shell example that is considerable different than the helloworld-go example * Added examples for kn usage (Fixed according to review comments) Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com> |
||
|---|---|---|
| .. | ||
| e2e | ||
| sampleapp | ||
| sampleconsistency | ||
| site | ||
| OWNERS | ||
| README.md | ||
| e2e-tests.sh | ||
| flag.go | ||
| presubmit-link-check.sh | ||
| presubmit-tests.sh | ||
README.md
Test
This directory contains tests and testing docs.
- Unit tests currently reside in the codebase alongside the code they test
- End-to-end tests
Running unit tests
TODO(#66): Write real unit tests.
Running end-to-end tests
Dependencies
You might need to install kubetest in order to run the end-to-end tests
locally:
go get -u k8s.io/test-infra/kubetest
Simply run the e2e-tests.sh script, setting $PROJECT_ID first to your GCP
project. The script will create a GKE cluster, install Knative, run the
end-to-end tests and delete the cluster.
If you already have a cluster set, ensure that $PROJECT_ID is empty and call
the script with the --run-tests argument. Note that this requires you to have
Knative Build installed and configured to your particular configuration setup.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.