powered by CADENAS

Manual

Manual

3.2.17.6.  TestMeta: ReverseConfigs / Reverse Search (automatic)

TestMeta also tests the functionality of ReverseConfig and Reverse Search (automatic) [internal name "GraphSearch"]

For this, activate the options Test value ranges and Test order number for uniqueness.

The test can also be performed for single projects.

The value given under maximum test time in minutes applies for ReverseConfigs / Reverse Search and all other tested processes altogether.

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[7]) 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, during the test Order number or Typecode is searched for all table rows (value range variants included).

A check will be performed if the flag VARSEARCHRESOLVEORDERNO[8] is accordingly set. (Possibly perform the Resolve check. See Section 5.8.2.1.15.15, “ Resolve check ”.)

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.

  • "Found wrong variable set", if the ReverseConfig returns variable values, which do not match the order number / type code.

For Reverse Search (automatic) [GraphSearch] following messages are displayed:

  • GraphSearch for Type code %1 failed

    or

  • GraphSearch for Order number %1 failed

For ReverseConfigs and Reverse Search (automatic) only warnings are shown, so that the test won't fail at it.



[7] On project level it is in the project file, on catalog level in $CADENAS_DATA/23d-libs/<catalog name>/dir.prj. No GUI equivalent. Manual intervention not needed. Will be automatically set during Resolve check.

[8] On project level it is in the project file, on catalog level in $CADENAS_DATA/23d-libs/<catalog name>/dir.prj. No GUI equivalent. Manual intervention not needed.