Make tests modular and split into a class w class methods.

[M4cs]

I think if we can split input tests and other tests into their own functions it will make the code more readable and easier to maintain.

Inside the Scanner class we need to clean up the payload test code. This links with #1 and #13.

[TotallyNotChase]

@M4cs Hello again! I suggest wrapping this "printing results" code snippet to a function that returns a boolean like so :-

We can then call this function like so:-

That's one part's readability improved! Let's move on to the tests themselves. I'm thinking of merging the 2 tests, as in the 2 payload loops this will cut down the time required for scans by HALF! (Ofcourse, the HTML scan will still only work if and only if self.html_scan is true)
Then we can just wrap each of those tests into a function to improve readability.

This does mean however that there won't be any status updates in the middle saying "Completed query scan" and "Starting HTML scan". Instead we could wrap the final report as a seperate function and finally include the store_results function inside it (btw the store_results function works right?)

That's what I've planned for this issue. This should NOT change anything at all (I've the functional changes in another branch, not done yet), it only rewraps the code. Let me know if you'd like any changes on these screenshots, otherwise I'd open a PR!

[M4cs]

I think this is a good idea 👍🏼