Skip to content

Files

Latest commit

author
Zhimin Xiang
Check DNS record status less frequently (knative#10312)
Dec 9, 2020
5374c76 · Dec 9, 2020

History

History
This branch is 3347 commits behind knative/serving:main.

e2e

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
autotls
autotls
Dec 9, 2020
gc
gc
Oct 29, 2020
initscale
initscale
Sep 17, 2020
multicontainer
multicontainer
Nov 25, 2020
tagheader
tagheader
Nov 25, 2020
README.md
README.md
Dec 4, 2018
activator_test.go
activator_test.go
Nov 25, 2020
autoscale.go
autoscale.go
Nov 30, 2020
autoscale_test.go
autoscale_test.go
Nov 30, 2020
destroypod_test.go
destroypod_test.go
Nov 25, 2020
e2e.go
e2e.go
Nov 11, 2020
egress_traffic_test.go
egress_traffic_test.go
Nov 25, 2020
grpc_test.go
grpc_test.go
Nov 25, 2020
helloworld_test.go
helloworld_test.go
Nov 25, 2020
http2_test.go
http2_test.go
Nov 25, 2020
image_pull_error_test.go
image_pull_error_test.go
Sep 19, 2020
initial_scale_test.go
initial_scale_test.go
Oct 14, 2020
logging_test.go
logging_test.go
Nov 25, 2020
minscale_readiness_test.go
minscale_readiness_test.go
Nov 24, 2020
namespace_test.go
namespace_test.go
Nov 25, 2020
pod_schedule_error_test.go
pod_schedule_error_test.go
Sep 29, 2020
rollback_byo_test.go
rollback_byo_test.go
Aug 5, 2020
route_service_test.go
route_service_test.go
Oct 29, 2020
scale.go
scale.go
Nov 25, 2020
service_to_service_test.go
service_to_service_test.go
Nov 25, 2020
service_validation_test.go
service_validation_test.go
Sep 29, 2020
subroutes_test.go
subroutes_test.go
Oct 29, 2020
websocket.go
websocket.go
Oct 14, 2020
websocket_test.go
websocket_test.go
Oct 6, 2020

README.md

End to end tests

Adding end to end tests

Knative Serving e2e tests test the end to end functionality of the Knative Serving API to verify the behavior of this specific implementation.

These tests use the test library.

Requirements

The e2e tests are used to test whether the flow of Knative Serving is performing as designed from start to finish.

The e2e tests MUST:

  1. Provide frequent output describing what actions they are undertaking, especially before performing long running operations. Please see the Log section for detailed instructions.
  2. Follow Golang best practices.