5.12.3.1.9.6. TestMeta: ReverseConfigs / Reverse Search (automatic)

TestMeta also tests the functionality of ReverseConfig and Reverse Search (automatic) [the term "GraphSearch" may also be used in TestMeta messages]

To do this, set the options Test value ranges and Test order number for uniqueness.

The test can also be performed for single projects.

The value specified under Maximum test time in minutes [maximum test time in minutes] applies to ReverseConfigs / Reverse Search and all other tested processes together.

Projects, where the order number can be found via full-text search index (Lucene) are excluded from the test. This concerns following:

Projects, which do not have value ranges, because they are always found via Lucene.
Projects marked as to be resolved (key VARSEARCHRESOLVEORDERNO^[47]) and whose value ranges are resolvable (meaning do not have continuous value ranges without step width like 1-100, for example).

If a ReverseConfig is found, the system searches for the order number [Order number] or type key [Type code] for all project lines (including value range variants) during the test.

The system checks whether the flag VARSEARCHRESOLVEORDERNO^[48] is set accordingly. (If necessary, run the resolution check [Resolve check], see Section 5.8.2.1.16.26, “ Reverse Search - Resolve check (automatic) ”)

If a search fails, the following warnings are displayed:

Type code search for type code "xy" failed
Order number search for order number "xy" failed

In addition the following warning is displayed:

"Found wrong project", if a project was found, which does not contain the number.
"Found wrong row", if a row was found, which does not contain the searched number.
"Incorrect variable set found" if the ReverseConfig returns variable values that do not match the order number/type code.

The following messages are displayed for Reverse Search (automatic):

GraphSearch for Type code %1 failed
or
GraphSearch for Order number %1 failed

Only warnings are issued for ReverseConfigs and Reverse Search (automatic) so that the test does not fail.

^[47]At project level this is in the project file, at catalog level in the catalog file $CADENAS_DATA/23d-libs/<katalogname>/dir.prjno GUI equivalent. Manual intervention is not necessary. Is set automatically during the resolution check [Resolve check].

^[48]At project level this is in the project file, at catalog level in the catalog file $CADENAS_DATA/23d-libs/<katalogname>/dir.prjno GUI equivalent. Manual intervention is not necessary.

Prev	Up	Next
5.12.3.1.9.5. TestMeta: General for order number or type code	Home	5.12.3.1.9.7. Index order numbers dependent on value ranges