It'd be better to check if a tool exists before running the actual plugin. This will be significantly reduce the run-time in distributions that are not pen-testing oriented. For example, Ubuntu does not have arachni pre-installed but arachni scans seem to run during analysis resulting in errors.
Expected Behavior
OWTF should report that the tool is missing and the test will be skipped.
Current Behavior
OWTF runs the command and returns an error message :

Possible Solution
Check for installation before scanning.
Steps to Reproduce (for bugs)
- Run OWTF without certain tools installed.
- Add target
- Notice that the tests are done assuming all tools are installed. ( Takes up unnecessary time)
Your Environment
- Installation method used: Manual
- Version/branch used: develop
- Operating System and version (like Kali, Debian, ArchLinux, etc): Ubuntu 15.10
- pip/setuptools version: pip-8.1.1
- sudo access: Yes
It'd be better to check if a tool exists before running the actual plugin. This will be significantly reduce the run-time in distributions that are not pen-testing oriented. For example, Ubuntu does not have arachni pre-installed but arachni scans seem to run during analysis resulting in errors.
Expected Behavior
OWTF should report that the tool is missing and the test will be skipped.
Current Behavior
OWTF runs the command and returns an error message :

Possible Solution
Check for installation before scanning.
Steps to Reproduce (for bugs)
Your Environment