5.8.2.1.12.5. TestMeta run

As soon as you click OK in the QA Check Settings dialog, the selected test criteria are applied and the test run is started.

	Note
The test run of extensive directories may take several hours. It is recommended to test either overnight or on a separate computer. The Abbreviate function allows you to cancel, but unlike the Cancel function, you do not lose any results determined up to that point. See below for details.

Note

The test run of extensive directories may take several hours. It is recommended to test either overnight or on a separate computer.

The Abbreviate function allows you to cancel, but unlike the Cancel function, you do not lose any results determined up to that point. See below for details.

When the TestMeta run begins, a) the selected directory/project is blocked and appears grayed out. However, you can continue working on other projects.

Docking window "Project selection [Project selection] ": Directory "bosses" blocked

And b) the QA check docking window is opened.

Docking window "QA check [QA-Check] "

You can use the options in the "Mode [Mode] " list field to filter results during the run, but also after the run has been completed.

The following options are available:

All: All messages are displayed.

Error -> Make the necessary corrections.

Note

To reach QA level 5 Errors must be corrected.

Publishing is only possible as of QA level 5.

With V12.8 there is a new category for test meta warnings, which identifies a warning that will turn into an error in future versions. This makes it easier to react to newly announced problems without blocking projects that had previously gone through the test meta process.

Critical and normal warnings are identified by different icons:

Critical warning
Is displayed, for example, if hidden variables have been used in a dimensioning (warning 4149).
Normal warning

The illustration shows an example of critical and normal warnings side by side.

Warning -> Make the necessary corrections if necessary.
Running: Shows which projects are currently being processed.
Idle: When testing the entire catalog or directories, some projects are in the queue. This setting allows you to see what still needs to be tested.
Ok: Labeling of projects without warnings and errors
Canceled: The filter allows you to quickly see whether a project has been canceled or not. You can also see in which test segment (e.g. Project Tests [Project tests] | Catalog Tests [Catalog tests] | Value Range Tests [Value range tests] | Table Tests [Tables tests] ) a project was canceled.
There may be undiscovered bugs and the project in question is not being considered for a QA status change.

Cancel Test

Cancellation of test meta regardless of the current status. No results are transmitted to PARTproject. The old status remains unchanged.

Abbreviate test

The following message appears when you click on the Shortcut [Abbreviate] button:

The current step is canceled and then already completed segments are continued!

Projects are tested in the segments Project tests (e.g. "Check file names", "Check images"), Table tests [Tables tests], Value range tests (e.g. "Check short description", "Check volume body") and Catalog tests: (e.g. check standard description for duplicates, file names, license keys).

Test segments

Projects that have been started but not completed in any segment are canceled, i.e. they remain in their original state as they were when they were canceled [Cancel].
Finished projects from the previous section will be continued in the next section and run through all sections (assemblies only continue, if all single parts continue).
The results of all projects (finished and canceled) are transferred to PARTproject.
All completed projects will have their QA state adapted.

Abbreviations [Abbreviate] can also be used several times.

Close dialog

To start another TestMeta run, the QA-Check docking window must be closed. Click on Close.

Prev	Up	Next
5.8.2.1.12.4. Plugins " tab page	Home	5.8.2.1.13. Catalog filter