Files

T

8a17d391c5 Envtest based integration tests for Fission (#2858 )

* skeleton for envtest fission
* Refactor code and add CLI test
* hack
* Update server test
* remove skip-ci for lint tests
* Pass client go storagesvc
* Add clientGen interface across code
* Fix storagesvc test
* Fix cmd client
* add retry in server test
* Fix concurrenct access to pool deployment
* Remove old executor test
* get rid of ginkgo/gomega
* disable flaky test
* flaky test
* revert ci change
* handle err from ParseBool

---------

Signed-off-by: Sanket Sudake <sanketsudake@gmail.com>
Co-authored-by: Pranoy Kundu <pranoy1998k@gmail.com>

2023-10-26 12:09:11 +05:30

benchmark

refactor: move from io/ioutil to io and os package (#2236 )

2021-10-23 17:14:12 +05:30

cluster

Move to new CI cluster (#1500 )

2020-01-23 13:35:26 +08:00

e2e

Envtest based integration tests for Fission (#2858 )

2023-10-26 12:09:11 +05:30

tests

Update go deps across project (#2837 )

2023-09-24 11:14:43 +05:30

upgrade

Bumping up release of Helm for release script (#1715 )

2020-09-16 16:07:48 +05:30

upgrade_test

fix: Environment typo (#2829 )

2023-08-30 07:50:09 +05:30

build.sh

jvm-jersey-env (#1677 )

2020-09-08 21:24:25 +05:30

init_tools.sh

Allow using URL as archive source when creating functions (#1360 )

2019-10-28 22:37:13 +08:00

kind_CI.sh

test job with old namespace support to ensure backward compatibility of fission (#2654 )

2022-12-08 12:15:23 +05:30

README.md

Update go dependencies (#1240 )

2019-08-23 16:17:12 +08:00

run_test.sh

Reduce logs in image pull and system prune for tests (#2163 )

2021-08-16 12:17:20 +05:30

test_utils.sh

remove .* suffix after Dockerfile (#2685 )

2023-01-11 14:04:56 +05:30

test.sh

Fix CI unable to start test due to the same travis build ID (#1246 )

2019-07-25 15:54:12 +08:00

utils.sh

Allow different namespaces in CI for fission-function and fission-builder (#2609 )

2022-11-11 18:56:20 +05:30

README.md

Test Framework

Prerequisite tools

GNU parallel >= 20161222

If you want to run test on Mac, you also need to install GNU tools for command compatibility. With Homebrew, you can get them by:

   brew install coreutils findutils gnu-sed

Run a single test

cd $REPO/test

# run 'tests/test_node_hello_http.sh'
./tests/test_node_hello_http.sh

# if you want to preserve the resources that created by test for debug
export TEST_NOCLEANUP=yes
./tests/test_node_hello_http.sh

# run 'tests/test_environments/test_go_env.sh' with custom images
export GO_RUNTIME_IMAGE=my.docker.repo/go-env:test
./tests/test_environments/test_go_env.sh

Run tests in parallel

NOTE: Some tests will consume lots of resources and cause the test fail.

Example: Run tests with 4 concurrent jobs.

cd $REPO/test

export JOBS=4
./run_test.sh \
    tests/test_backend_poolmgr.sh \
    tests/test_node_hello_http.sh \
    tests/test_pass.sh \
    tests/test_specs/test_spec.sh

# The test output will be available in logs/
cat logs/test_backend_poolmgr.sh.log

# The summary report will be saved to logs/_recap
cat logs/_recap