|
|
|
|
|
|
|
|
|
|
- Overview
- The static audit of the project
- Start static audit
- List of errors detected by the static audit
- The audit of the content of the application library
- Overview
- Interpreting the results of the audit regarding the library content
- The audit of the setup content
- Overview
- Interpreting the results of the audit regarding the setup content
Static auditing is a feature of the environment that allows you to examine the elements of a project to detect various problems and suggest improvements. The static audit includes: The static audit of the project Start static audit To start the static audit of the project: - In the Project dashboard click the gray arrow of the "Static audit" widget. The static audit of the project starts.
or - On the "Project" tab, in the "Audit and performance" group, expand "Static audit" and select "Start static audit". The audit wizard opens. Select the type of audit to perform:
- Audit of the entire project. The current project will be reviewed.
- Audit of some project elements. In the next step, select the elements to be audited. At the end of the wizard, the audit will be started on the selected elements.
The audit window opens:
1: In the main area, the audit shows the various problems detected. 2: For each problem, the editor proposes an automation solution by clicking on the "..." button. Depending on the type of problem, you might be prompted to change a value in a configuration window, or the problem may be fixed automatically. 3: Each item of information identified by the static project audit can be ignored. To do so, select "Ignore this information" in the context menu of information table. This button allows you to see the information that was disabled and to re-enable it. 4: The "Refresh" button restarts the project audit and updates the table display. 5: The "Print" button is used to print out a detailed report of detected problems. Remarks: - The window for static audit is a non-modal window and it can remain opened while correcting the errors. It does not interfere with the use of development environment.
- The static audit also lists the problems detected by the UI audit. These problems concern the use of obsolete technologies that can slow down your project, the generation of your application, your application, etc. For more details, see UI audit.
List of errors detected by the static audit The static audit of project can detect the following errors:
Compilation problems detected by the static audit | | A native access is used by the project but it is not installed on the computer. | | Unused code was detected. | | Unused variables have been detected. | | Project elements are orphan elements (they are never used in the project code). | | Compilation errors (UI or code) have been detected. | | The project uses more than 1000 elements. We recommend that you use the 64-bit version of WINDEV, WEBDEV and WINDEV Mobile. | | The compilation directory (<ProjectName>.CPL directory) is found on a network disk. The editor performance may be slowed down. We recommend that you use a local directory. This directory can be configured in the project options. | Problems in project analysis detected by the static audit | | A native connector is used by the project but is not installed on the workstation. | Tip: Project analysis has no links.
We advise you to create links in order to ensure data consistency.The lack of link definition does not allow for automatic management of referential integrity, which is a risk to the application quality. | Problems of SCM (Source Code Manager) detected by the static audit | | Project elements have been checked out from the SCM since a long time without being checked back in. | | Elements are currently checked out in test mode. | | Tip: it is advisable to deactivate archiving of the analysis in SCM. | | Tip: it is advisable to convert the project analysis to the new format. For more details, see New project analysis format. | | Problems common to the window editor, page editor and report editor detected by the static audit | | Spelling mistakes have been detected. | | Unused groups of controls have been detected. | | Some elements do not contain all project languages. | | Some elements are not updated from their templates. | | Dissociated styles have been detected. | Problems of window editor detected by the static audit | | Unused styles have been detected. | | An internal window is not updated from its template. | | A "File path" type input mask is selected, but path entry assistance is not offered. | Identifying the windows managing (or not) the large fonts
One or more windows include a display mode in large font that differs from the mode used by most application windows.
The management mode of large fonts must be identical for all application windows.
The "..." button allows you to get the list of project windows with their management mode of large fonts. All you have to do is choose the requested option and apply the modifications. | | Charts may show jagged graphics if the anti-aliasing option is not enabled. | Problems of page editor detected by the static audit | | The referencing optimizations have not been applied. | Problems of report editor detected by the static audit | | A report is based on a Table control that does not exist. | | An internal report uses a non-existent report. | | A report uses the "Integrated code" option while this is not required. | Problems of the query editor detected by the static audit | | One or more optimizations on the project queries have been detected. | | One or more queries concern data files that no longer exist in the project analysis. | Problems of the automated test detected by the static audit | | One or more automated tests have encountered errors. | Problems of code editor detected by the static audit | | Unused multilingual messages have been detected. | | Too many errors have been disabled. | | The percentage of comments in the project is too low. | | The average number of lines per process is too high. |  New in SaaSMultilingual channels in old format detected. Multilingual strings in the old format don't get the latest updates, are a source of errors and can unnecessarily increase the size of project elements. Attention This feature is only available in WINDEV Suite SaaS 2025 Update 1. For more details, see Using new features exclusive to WINDEV Suite SaaS 2025. | Problems of project editor detected by the static audit | | One or more configurations generate several targets. | | The automatic check-out from SCM is not enabled. | | The skin template of the project is not installed on the computer. | | The former mechanism of developer groupware is used. | | The performance profiler has not been used since a long time. In this case, the static audit proposes to start the performance profiler. | | The description file of the code style was not found. | | The project has not been cleaned since a long time. In this case, the static audit proposes to start the project cleaner. | | The UI errors are disabled. | | The spelling checker of OpenOffice is not installed on the computer. | | The project is large and it does not use the SCM. | | Elements are found in different versions. For more details, see Managing the element versions. | | Unused elements are found in the project directory. In this case, the static audit is used to start the search for orphan elements. | | The project uses the developer groupware and not the Source Code Manager. | Note The above list is not exhaustive, as new errors may be added as updates are made. The audit of the content of the application library Overview The audit of the application library content shows the size of the different project elements included in the library. This information is displayed in a table and in a TreeMap: this enables you to view the importance of the size of the elements in relation to the other ones. To start the audit regarding the content of application library: - In the Project dashboard click the gray arrow of the "Static audit" widget. The static audit starts. Select the " Analysis of the library" tab.
or - On the "Project" tab, in the "Audit and performance" group, expand "Static audit" and select "Analysis of the library (EXE, WDK, WDL)".
Note The application library (WDL, WDK, EXE, etc.) must have been generated at least once to use this audit. Interpreting the results of the audit regarding the library content The audit of the library content is used to detect the following problems: - Presence of an unwanted file in the application library.
- Graphic visualization of size occupied by each file.
From the audit window, ability to directly display an element selected in its editor. To do so, select the element and click the "View" button. The audit of the setup content
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|