11
11
# -----------------
12
12
#
13
13
# 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
15
19
#
16
20
# To cleanup after a run, see "cleanup.sh".
17
21
#
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:
19
23
#
20
24
# "##TEST_INFO" is very concise (one line per test (either PASS or FAIL).
21
25
# "[timestamp]" is concise.
22
26
# "+" is verbose.
23
27
# Anything else is semi-verbose.
24
28
#
29
+ #
25
30
# This script accepts optional env var overrides:
26
31
#
27
32
# RESULT_ROOT The root directory of the test temporary files.
33
38
# See "Directory Configuration and Structure" below for
34
39
# defaults and a detailed description of test directies.
35
40
#
41
+ # QUICKTEST When set to "true", limits testing to a subset of
42
+ # of the tests.
43
+ #
36
44
# WERCKER Set to true if invoking from Wercker, set
37
45
# to false or "" if running stand-alone or from Jenkins.
38
46
# Default is "".
@@ -371,6 +379,8 @@ trap ctrl_c INT
371
379
372
380
function ctrl_c() {
373
381
declare_new_test_from_trap 1 run_aborted_with_ctrl_c
382
+ # disable the trap:
383
+ trap - INT
374
384
fail " Trapped CTRL-C"
375
385
}
376
386
@@ -1449,6 +1459,8 @@ EOF
1449
1459
# like local, it uses the t3 channel...
1450
1460
run_wlst_script $1 hybrid ${pyfile_con}
1451
1461
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.
1452
1464
run_wlst_script $1 local ${pyfile_con}
1453
1465
fi
1454
1466
@@ -1470,6 +1482,11 @@ function run_wlst_script {
1470
1482
fail " requires at least 3 parameters: domainKey local|remote|hybrid local_pyfile optionalarg1 optionalarg2 ..."
1471
1483
fi
1472
1484
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
+
1473
1490
local DOM_KEY=" $1 "
1474
1491
local NAMESPACE=" ` dom_get $1 NAMESPACE` "
1475
1492
local DOMAIN_UID=" ` dom_get $1 DOMAIN_UID` "
@@ -2352,8 +2369,9 @@ function test_suite_init {
2352
2369
}
2353
2370
2354
2371
#
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.
2357
2375
#
2358
2376
2359
2377
function test_suite {
0 commit comments