5.8.2.1.12.1. Tabbed page "General"

Tabbed page "General"

Tabbed page "General"

  • Test selection -> list field:

    • User: Free input

    • QA-State-5: Settings prepared that QA state is achieved after a successful run.

    • QA-Checker-Plugin:

  • Calculate geometry: This function builds up the attributes (table rows) of all geometries (*.3db drawing files) on a trial basis. Attributes which lead to an “impossible” structure, such as a negative value for width across flats, are logged as an error. The calculation process may take a very long time (depending on catalog size).

  • Test already tested projects:

  • Test value ranges:

    • As many value range combinations as possible are gone over and it is checked whether the 3D geometry can be build correctly.

    • If Test order number for uniqueness is activated in addition, it is also checked whether there are double order number among the tested variants.

    • If there is a ReverseConfig for a project, then it is checked whether the order number can be found via the ReverseConfig.

    • If there is no ReverseConfig, as of SP5 it is checked, whether the option Index order numbers dependent on value ranges is activated.

    Also see Section 5.12.7, “Classification according to CNSORDERNO / CNSTYPECODE ”.

  • Maximum test time (minutes)

  • Job Server:

  • Line filter:

  • Maximum number of parallel tests:

    The initial display value (default value) corresponds to the available CPU cores (*2 for hyperthreading if available).

    Leave this setting if there are no problems like a jerking mouse cursor, for example.

    The reduction of parallel tests (CPU cores) by one or two (depending on the used machine), should leave enough performance for a trouble-free working.

    However, be aware that a test itself can use multi-threading, so that using the half of cores does not automatically mean the use of half of the CPU. If also other CPU-intensive processes shall be started, then you have to consider theses, too.