The first thing I see highlighted is the variable my_FIRST_var. Now if I look at this method in my IDE, I see some things highlighted: For my environment I am using IntelliJ IDEA, and I have the SonarLint plugin installed.Įnter fullscreen mode Exit fullscreen mode In addition to static code analysis that may be baked into your IDE, there are 3rd partying linting plugins such as SonarLint that allow you to analyze your code right in the IDE. If you haven't run it in the past, you are very likely to find some interesting results. If you don't use it now, take some time to find out how your IDE supports static analysis. Most modern IDEs have a mechanism to allow for static code analysis. Static code analysis, courtesy of your IDE enforcing common team-based language ruleset.Static code analysis evaluates your source code statically, without running it. It's different from dynamic testing, in that in that the analysis is done against your source code, without the application executing. Static code analysis is another tool you can use to ensure the quality of your code. These tests are all considered "dynamic tests", as they are executed against the running application. All of these tests are run after code has been written and will execute the code to verify it conforms to the functional requirements being validated.
These tests are used to ensure that future code changes don't break existing functionality, and can include integration, API, and end-to-end testing. As a Quality Engineer, I am typically involved in building automated tests.
0 kommentar(er)
