Static testing is a form of software testing which is performed in a static environment i.e., verification of a software product for flaws without execution of the main code. In order to facilitate this task in a quicker manner, across different working languages, we give you a list of some of the most commonly used tools for static testing with a brief description of their specialities.
| Sl.No. | Tools | Specialities |
|---|---|---|
| 1. | RIPS | This tool is useful for PHP based platforms and detects sinks and guards against SQL injection and cross site scripting.
Pros:
Cons:
|
| 2. | YASCA (Yet Another Source Code Analyser) | This is a useful tool to check for security bugs in C++ & Java based products.
Pros:
Cons:
|
| 3. | YASCA (Yet Another Source Code Analyser) | This tool helps in detection of errors or flaws in JAVA applications.
Pros:
Cons:
|
| 4. | Visual Code Grepper | This code security tool works admirably well with products based on PHP,C++, Java and Visual basic to detect issues related with the code by speedily scanning and describing them in detail.
Pros:
Cons:
|
| 5. | DevBug | Another tool useful for PHP platforms, this tool was originally written in JavaScript.
Pros:
Cons:
|
| 6. | Flawfinder | Flawfinder is a useful tool for sorting out security issues in C language based applications depending on the risk level. This tool is written in Python and utilises a command line interface.
Pros:
Cons:
|
| 7. | Brakeman | This tool is for detecting security vulnerabilities in ROR (Ruby on rails) platform at any stage of product development.
Pros:
Cons:
|
| 8. | CPPCheck | Another tool based on C/C++ platform, this test is used for checking non standard codes which fail to be detected by a compiler.
Pros:
Cons:
|
.png)
.png)
Advertisement:
