Some of the work I recently did on Java static scanning was done on Jenkins using The FindBugs plugin, but due to the removal of Jenkins permissions and the release of Java code permissions (I’m not sure how the two are related), I’m going to do the static code scanning locally.

There is a plugin for FindBug-idea in Intellij, which I found on the Internet. However, I found a plugin for QaPlug-Findbugs in Intellij. Looks like it’s doing the same thing.

But both plug-ins face the same problem: I didn’t follow up the update of Intellij, and the supported version upper limit is old. Here I found the official information of FindBug-idea which was last updated on October 17, 2016. Obviously, this is no longer working. That’s why Intellij’s plugin library doesn’t show the changed plugins when I search for findBugs and bugs.

Qaplug-findbugs was last maintained on April 23, 2018, so it supports version-upper limit compatibility changes to support IntelliJ IDEA 2018.1.1. Later versions are not supported. Those of you using the new Version of Intellij are going to have to give it up.

  • According to the above two plug-ins’ official information, there is no recent upgrade and maintenance plan.

This led me to SpotBugs, and here’s an official transcript:

The IntelliJ SpotBugs plug-in provides static byte code analysis to find errors in Java code from IntelliJ IDEA. SpotBugs is Java’s bug detection tool that uses static analysis to find more than 400 error patterns, such as null pointer dereference, infinite recursive loops, incorrect use of Java libraries, and deadlocks. SpotBugs can identify hundreds of serious defects in large applications (typically about 1 defect for every 1000-2000 lines of uncommented source statements).

The use method will not be repeated, and other plug-ins download and install the same method, here is a simple intercept of a BUG screenshots, we feel.

It’s so important to learn English well

In the left column of the source code will show different colors of bugs, distinguish different levels of bugs, according to my current self-test situation, most of them are standard, the actual operation needs to solve the error information first, and then to solve the suspicious problem, because the suspicious is too much.

The scan detected 155 classes files and found 143 bugs.

  • Of the three plug-ins mentioned in this articleIntellijAddress:

Plugins.jetbrains.com/plugin/1401…

Plugins.jetbrains.com/plugin/4597…

Plugins.jetbrains.com/plugin/3847…

  • The whole experience,spotbugsdetectedBUGIs very accurate compared tofindbugsIt’s much better. It’s been promoted in the team.

Public number FunTester, original sharing enthusiasts, Tencent cloud, open source China and nuggets community recommended home page, Zhihu eight-level strong, welcome attention, exchange, prohibit unauthorized reprinting by third parties.

FunTester hot text selection

  • Selenium4 IDE, it’s finally here
  • Dom-based XML file parsing class
  • How to become a Full stack automation engineer
  • Terminate the performance test and print the report
  • Exploration of fixed QPS pressure measurement mode
  • Why do tests miss bugs
  • Automated test lifecycle
  • Fixed QPS pressure test
  • JsonPath validates classes that are both Groovy overloaded operator practices