tag Command

Owned by Michael Bruton (Deactivated)
Jun 16, 2015
4 min read

ETLUnit 3.9.6

 

Draft in Progress

This document is a draft and is under development.

 

Description

SEE ETLUnit author's Tags page.

A tag is a group of named execution sets created by ETLUnit after a test run.  The execution sets may be run again later, by using the tag name. Even if other tests are run after the tag is created, the tagged set may be run again.  The exception to this rule is the 'last' tag, which always reruns the last test command.

So there are two types of tags:

  1. Explicitly named tag.  The user provides a name for the tag using the tag command.
  2. Software-supplied tag.  Every test run creates a tag named "last."

Each tag has five sets.

Set NameContains
allEvery test method or operation identified by the tag.
successEvery test method or operation that succeeded.
failEvery test method or operation that resulted in failure.
errorEvery test method or operation that caused an error.
failError(Case sensitive) Union of fail and error sets.

Example

Following is a command line example that uses tags.  Notice how named tags may be recalled and used after running other tests.  The last test below runs all the tests represented by two different tags.

 

userme> tag t1
userme> te @assert_with_sql_dft_pkg
Processing [1] tests
class [default].assert_with_sql_dft_pkg   ----------------------------------------
1/1        .inlineSqlDftPkg
  Passed                                                                      P[1]
Tests run: 1, Successes: 1, Time elapsed: 00.486 sec
userme> tag t2
userme> te %assert_samples@|assert_with_sql|
Processing [2] tests
class assert_samples.assert_with_sql   -------------------------------------------
1/2        .inlineSql
  Passed                                                                      P[1]
2/2        .sqlScript
  Passed                                                                      P[2]
Tests run: 2, Successes: 2, Time elapsed: 00.716 sec
userme> te @|execute_sql_demo|
Processing [3] tests
class execute_samples.execute_sql_demo   -----------------------------------------
1/3        .sql_demo_1
  Passed                                                                      P[1]
2/3        .sql_demo_2
  Passed                                                                      P[2]
3/3        .sql_demo_3
      ERR_SQL_SP_FAILURE
  Caused an error                                                        P[2] E[1]
Tests run: 3, Successes: 2, Errors: 1, Time elapsed: 00.670 sec
userme> te <last,error>
Processing [1] tests
class execute_samples.execute_sql_demo   -----------------------------------------
1/1        .sql_demo_3
      ERR_SQL_SP_FAILURE
  Caused an error                                                             E[1]
Tests run: 1, Errors: 1, Time elapsed: 00.300 sec
userme> te <t1> or <t2>
Processing [3] tests
class [default].assert_with_sql_dft_pkg   ----------------------------------------
1/3        .inlineSqlDftPkg
  Passed                                                                      P[1]
class assert_samples.assert_with_sql   -------------------------------------------
2/3        .inlineSql
  Passed                                                                      P[2]
3/3        .sqlScript
  Passed                                                                      P[3]
Tests run: 3, Successes: 3, Time elapsed: 00.833 sec

Â