Polyspace as You CodePolyspace as You Code detects critical defects and security vulnerabilities and checks for code compliance with coding rule standards such as MISRA C®, MISRA C++, AUTOSAR C++14, CERT® C, CERT C++, as well as custom naming conventions, and reports the findings within the source code view. When connected to the Polyspace Access central repository, it can highlight only new issues added by the developer compared to the development baseline. InstallationPolyspace as You Code requires a Polyspace Access license. if you do not have a license, you can request a free trial. To run the extension, download and run the Polyspace as You Code installer for your platform: The extension is also available on the Visual Studio Code Marketplace. If you download the extension from the Marketplace, you still need to run the Polyspace as You Code installer to install the Polyspace analysis engine before you can start using the extension. After the installation, you might need to configure some extension settings to make full use of all the Polyspace as You Code features. For more information, see the Get Started section. Get StartedTo start using Polyspace as You Code with the default configuration:
Depending on your build system, you might need to modify the More information to get startedTo see a more detailed description of how to get started with Polyspace as You Code, open the Polyspace as You Code walkthroughs. To open the walkthroughs, go to Help > Welcome > Walkthroughs. ConfigurationConfigure the Analysis
Review Results
Baseline
TroubleshootingIf an analysis fails, you see a popup with a short description of the issue. To investigate the issue further, open the Output panel by selecting the file where the analysis failed from the Quality Monitoring view, or by clicking in the Configuration or Baseline views. Scroll through the Output panel to try to determine the cause of the analysis failure. Contact UsWe encourage all feedback. If you encounter a technical issue or have an enhancement request, create an issue here or contact MathWorks at support@mathworks.com. |