article https://www.browserstack.com/guide/static-software-testing-tools
This blog will focus on static testing. Static testing is the inspection of a code program without execution. Static testing is an early stage of creating a program, where a program is being developed, and code can be adjusted before the final product. A program’s files being reviewed before its release saves a company money, without the program being reworked. Review analysis and static analysis are two different methods for static testing. Informal review is a type of review analysis where team members provide code feedback, while static code analysis for static analysis uses software tools to detect coding errors. Static testing is used multiple times in coding a program. When a project is first assigned whether in a professional or academic setting, programmers need to understand the requirements of their projects. Usually after instructions have been reviewed, coding would be the next step, but static testing adds an extra step of checking if a program has the documents used for coding. Throughout the development of a program, a common practice is running the program, whether with unit testing or running a whole program, for a programmer to know if the program is error free. Static testing at the coding stage can either be feedback from team members, or different software tools such as Soot and checkstyle. BrowserStack Code Quality tool is one software tool for static testing. In my programming experience, I am used to having to manually fix my errors. This past week, I was introduced to new visual studio code software tools for coding errors. BrowserStack Code Quality tool is one tool of automated stack testing, where static testing is done through software tools.
BrowserStack Code Quality has an assistant that recommends how large classes in a program can be split into smaller classes. BrowserStack Code Quality can be downloaded in either Android studio, Vscode, or Intellij, with a quick program scan with feedback. Another software tool is Checkstyle which only works with Java. Developers using Checkstyle learn about errors when writing code, compared to after a program has executed. Developers who are using Checkstyle can create coding conditions, and a program is checked for following defined coding conditions. Recently, I learned how to use PMD in Visual Studio Code. PMD detects logical errors in code such as uninitialized variables, unused code. PMD has a copy paste detector that identifies duplicated code. PMD supports more than 10 different programming languages.
From the blog jonathan's computer journey by Jonathan Mujjumbi and used with permission of the author. All other rights reserved by the author.