![]() The OUTPUT panel will start showing the information about subsequent steps of the static analysis. For now with these settings made, select the Timer folder in Explorer.įrom the context menu, select “C/C++test: Analyze Selected File(s) …”. Let’s stay with the default.įor your real projects, there’s one more setting you may need to configure to start using static analysis. Select test configuration: Defines which static analysis checkers will be used to scan your project.Select compiler configuration: Select the compiler that is closest to what you are using for your project, for example “GNU GCC 9.x (x86_64)” if you use GCC 9.2.Select C/C++test installation: Point to the place where you unpacked C/C++test Standard.To perform the simple configuration of the extension, click the C/C++test quick start in status bar: In the VS Code, switch to Explorer and use “Add folder to workspace …” to add the /examples/Timer folder to your workspace. You can install the license by editing the cpptestcli.properties file located in the main directory of the distribution or place the cpptestcli.properties file in your home directory and put the licensing information there.įor our experiment here, let’s use the Timer example project that is shipped with C/C++test. Your license needs to contain the command line feature. The message informs that in order to run the static analysis with the VS Code extension you need to download the C/C++test Standard, which is the command line static analysis engine that is used by the C/C++test Visual Studio Code extension.Īfter downloading the C/C++test Standard distribution simply unpack it to any directory you like and install the trial (or full) license. In the search field, type “C++test” and install the extension.Īfter the installation, the extension will welcome you with the following message: Start VS Code and go to Extensions (Ctrl + Shift + X). The easiest way to get up and running with Parasoft static analysis extension for the Visual Studio Code editor is via the Microsoft Marketplace. Watch On-Demand Webinar How to Get Started With C/C++test for VS Code ![]() In this post, I’m focusing on the static analysis for C/C++ but we also support C# with static analysis extension for Parasoft dotTEST. We decided to fill this gap and provide an extension for this great editor to help check the code you just wrote against your preferred coding standard, review the results, and fix or suppress them - all inside the VS Code. I mean the full standards support, Clang-Tidy, is cool but it covers only a fraction of these standards. Until the 2020.1 release of the Parasoft C/C++test in April, there was nothing that could help you to comply with MISRA, CERT, and AUTOSAR C++ coding standards without a need to leave the editor to check the results. However, there is a limited number of extensions for C/C++ static analysis. ![]() VS Code is supported by a vast ecosystem of extensions available through the marketplace. ![]() We often see it in use for developing safety-critical C/C++ software. Its popularity is not limited to the teams developing with JavaScript or TypeScript. It’s fast, simple, customizable, extensible, and runs on the three leading development platforms: Windows, Linux, and Mac. In the latest Stack Overflow Annual Developer Survey, VS Code dominated the Development Environments and Tools category. The popularity of the Visual Studio Code (VS Code) editor is growing at a rapid pace. In this blog post, I’ll share a couple of hints with you about configuring and using our brand new C/C++test static analysis extension for the Visual Studio Code editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |