1111# -----------------
1212#
1313# This script runs a series of acceptance tests and archives the results
14- # into tar.gz files upon completion.
14+ # into tar.gz files upon completion. It currently runs in three modes,
15+ # "Wercker", "Jenkins", and "standalone" Oracle Linux, where the mode
16+ # is controlled by the WERCKER and JENKINS environment variables described
17+ # below. A standalone run filters out verbose lines from the console output
18+ # while redirecting full output to the file /tmp/test_suite.out
1519#
1620# To cleanup after a run, see "cleanup.sh".
1721#
18- # The test has three levels of logging output, output that begins with:
22+ # The test has three levels of logging output. Output that begins with:
1923#
2024# "##TEST_INFO" is very concise (one line per test (either PASS or FAIL).
2125# "[timestamp]" is concise.
2226# "+" is verbose.
2327# Anything else is semi-verbose.
2428#
29+ #
2530# This script accepts optional env var overrides:
2631#
2732# RESULT_ROOT The root directory of the test temporary files.
3338# See "Directory Configuration and Structure" below for
3439# defaults and a detailed description of test directies.
3540#
41+ # QUICKTEST When set to "true", limits testing to a subset of
42+ # of the tests.
43+ #
3644# WERCKER Set to true if invoking from Wercker, set
3745# to false or "" if running stand-alone or from Jenkins.
3846# Default is "".
@@ -371,6 +379,8 @@ trap ctrl_c INT
371379
372380function ctrl_c() {
373381 declare_new_test_from_trap 1 run_aborted_with_ctrl_c
382+ # disable the trap:
383+ trap - INT
374384 fail " Trapped CTRL-C"
375385}
376386
@@ -1449,6 +1459,8 @@ EOF
14491459 # like local, it uses the t3 channel...
14501460 run_wlst_script $1 hybrid ${pyfile_con}
14511461 else
1462+ # TODO The following has a dependency on java and WebLogic being in the path/classpath.
1463+ # We should run on 'hybrid' mode instead if java and WebLogic aren't already setup.
14521464 run_wlst_script $1 local ${pyfile_con}
14531465 fi
14541466
@@ -1470,6 +1482,11 @@ function run_wlst_script {
14701482 fail " requires at least 3 parameters: domainKey local|remote|hybrid local_pyfile optionalarg1 optionalarg2 ..."
14711483 fi
14721484
1485+ # TODO It seems possible to obtain user/pass from the secret via WLST verbs. This
1486+ # would be better than passing it to the WLST command-line in plain-text. See
1487+ # read-domain-secret.py in domain-job-template for an example of how this is done
1488+ # for WLST that runs from within a pod...
1489+
14731490 local DOM_KEY=" $1 "
14741491 local NAMESPACE=" ` dom_get $1 NAMESPACE` "
14751492 local DOMAIN_UID=" ` dom_get $1 DOMAIN_UID` "
@@ -2352,8 +2369,9 @@ function test_suite_init {
23522369}
23532370
23542371#
2355- # TODO: Make output less verbose -- suppress REST output, etc. Move output to file and/or
2356- # only report output on a failure and/or prefix output with a "+".
2372+ # TODO: Make output less verbose -- suppress REST, archive, and job output, etc. In general, move
2373+ # move verbose output to file and/or only report output on a failure and/or prefix output
2374+ # with a "+". Also, suppress output in the pod readiness loops to only once every 30 seconds.
23572375#
23582376
23592377function test_suite {
0 commit comments