contains a collection of temporal efficiency tests for the implemented ID2T attacks except EternalBlue and MS17.
introduces a new method for ID2TAttackTest, which is a generic temporal efficiency test.
It also introduces support for IP ranges as valid input for the IP attack parameter.
To run the suite, you currently have to be in the code directory and execute:
python -m unittest Test/efficiency_testing.py
or
python3 -m unittest Test/efficiency_testing.py
This is to separate the efficiency tests from the unit tests. During the refactoring I will add a script like the "run_tests" script we already implemented for the unit tests.
Please take note that SQLiAttack seems to have fluctuations in run time about every tenth run. This results in a failing efficiency test from time to time. I will look into this problem though.
This pull request ...:
* contains a collection of temporal efficiency tests for the implemented ID2T attacks except EternalBlue and MS17.
* introduces a new method for ID2TAttackTest, which is a generic temporal efficiency test.
It also introduces support for IP ranges as valid input for the IP attack parameter.
To run the suite, you currently have to be in the code directory and execute:
python -m unittest Test/efficiency_testing.py
or
python3 -m unittest Test/efficiency_testing.py
This is to separate the efficiency tests from the unit tests. During the refactoring I will add a script like the "run_tests" script we already implemented for the unit tests.
Please take note that SQLiAttack seems to have fluctuations in run time about every tenth run. This results in a failing efficiency test from time to time. I will look into this problem though.
This pull request ...:
It also introduces support for IP ranges as valid input for the IP attack parameter.
To run the suite, you currently have to be in the code directory and execute:
or
This is to separate the efficiency tests from the unit tests. During the refactoring I will add a script like the "run_tests" script we already implemented for the unit tests.
Please take note that SQLiAttack seems to have fluctuations in run time about every tenth run. This results in a failing efficiency test from time to time. I will look into this problem though.