Skip to content
This repository has been archived by the owner on May 5, 2023. It is now read-only.

Commit

Permalink
Version 2.7.2
Browse files Browse the repository at this point in the history
  • Loading branch information
joergboe committed Jun 11, 2018
1 parent 1acbbd9 commit 88e04a7
Show file tree
Hide file tree
Showing 7 changed files with 11 additions and 9 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,6 @@ Version 2.7.0:
- New utils function: trim, getSystemLoad, getSystemLoad100
- Print the elapsed time

Version 2.7.1:
Version 2.7.2:
- Some fixes in category handling

2 changes: 1 addition & 1 deletion bin/case.sh
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ declare -i executedTestFinSteps=0
declare TTTT_failureOccurred=''
declare TTTT_skipthis=""
eval "$TTXX_runCategoryPatternArray"
declare -a TTTT_categoryArray=()
declare -a TTTT_categoryArray=( 'default' )

#test finalization function
function caseFinalization {
Expand Down
9 changes: 5 additions & 4 deletions bin/man.sh
Original file line number Diff line number Diff line change
Expand Up @@ -369,14 +369,15 @@ function manpage () {
Alternatively the existence of an file SKIP in the Test Case/Suite directory inhibits the execution of all variants of the Case/Suite.
The function 'setCategory' defines the categories of a Test Case or Test Suite. The categories are checked before the Case- or Suite- preparation
is executed.
The function 'setCategory' defines the categories of a Test Case or Test Suite. If the function 'setCategory' is not called during
Case or Suite initialization, the artifact has the default category 'default'. If the function 'setCategory' is called with an empty
parameter list, all catagories are cleaned. The categories are checked before the Case- or Suite- preparation is executed.
The run-categories of the a test run can be defined with command line parameter -c|--category VALUE. The run-categories
are considered to be patterns.
If one of the run-category pattern matches any of the categories of the artifact, the Case/Suite is executed. Otherwise it is skipped.
A test Cases or Suites without a defined categorie are always executed independently from the run-categories.
A test Case or Suite without a defined categorie is always executed independently from the run-categories.
If no run-category pattern is entered, all Cases and Suite are executed, regardless of the defined categories.
If the run-caegory 'default' is specified, all Cases and Suites are executed that have no explicit category set.
## Sequence Control
Expand Down
2 changes: 1 addition & 1 deletion bin/suite.sh
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ eval "$TTXX_runCategoryPatternArray"
declare -rx TTRO_suite="${suitesName[$TTRO_suiteIndex]}"
declare -rx TTRO_inputDirSuite="${suitesPath[$TTRO_suiteIndex]}"
declare TTTT_skipthis=''
declare -a TTTT_categoryArray=()
declare -a TTTT_categoryArray=( 'default' )

declare -a cases=() # case pathes
declare -a casesNames=() # the short path
Expand Down
2 changes: 1 addition & 1 deletion bin/version.sh
Original file line number Diff line number Diff line change
@@ -1 +1 @@
declare -xr TTRO_version="2.7.2__dev__"
declare -xr TTRO_version="2.7.2"
2 changes: 1 addition & 1 deletion samples/Categories/Suite1/CaseWithCat/TestCase.sh
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
#--variantCount=5
#--variantCount=6

#prepare the case categories
case "$TTRO_variantCase" in
Expand Down
1 change: 1 addition & 0 deletions samples/Categories/Suite1/TestSuite.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
setCategory

0 comments on commit 88e04a7

Please sign in to comment.