Module dependencies in Expert Mode

[torabi12]

Is your feature request related to a problem? Please describe.

I tested all modules one by one and found some dependencies. S13 requires S12 and S14 requires S12 and S13:

S20 needs S115:

S25 uses S24:

S109 requires S108:

S116 wanted to use S115:

Each modul can be selected one by one and if the user does not have the knowledge of exactly which module does what, they cannot effectively select for the test.

Describe the solution you'd like

It would be nice to have a way to display the dependencies in the list if someone is using the expert mode:

Describe alternatives you've considered

I think the framed solution would show the related modules well, but if someone selects one that has a dependency it could also be selected automatically.

Additional context

• If you choose expert mode, no module is selected by default. I think that in practise we often need almost all modules and want to leave some out, so the list of modules should be all selected except for S120_cwe_checker, and then we should just manually select the one or ones we don't want to use in the actual test execution. Functions such as select all, deselect all and reverse selection could also help the user to manage the list.

• If the module_blacklist.txt file exists then EMBArk could take into account the disabled modules and in this case gray out them on the page so that they cannot be selected. At the moment even though they are disabled in the text file, they still run when manually selected.

• I think the following modules are missing from the page but the scripts are in modules folder:

S17_apk_check.sh S26_kernel_vuln_verifier.sh S36_lighttpd.sh

[m-1-k-3]

As it is called "Expert mode" the expert should know what todo. We put this on our future todo list. Pull requests are welcome.

[BenediktMKuehne]

Putting this into a wiki page for now. expert-mode