Testing the project

[DanielBoye]

Would like some more thoughts into making integration tests and unit test for the project. I've been checking this out now and have a suggestion.

So we have some integration tests that will focus on evaluating the interactions and compatibility of various components within our project. The tests here are high-level so we can ish simulate some real-world scenarios for a ctf, and that is done by testing different modules work together. So it could really help with identifying potential bugs and uncover issues that might not be visible in isolated unit testing (as for running the whole project). A scenario for is is that you update some function and test that, but it does not break itself, it breaks another part of the program.

If we go for this we can just make a new file named integration_tests.rs within the test/ directory. In this file, we can have our test cases for the codebase.

And the unit tests will be for testing the individual functions like runner or CLI I think. Here we just test the individual units of code within its own kind of isolation. This is just done to check the specific functions, methods, or small groups of related functions under various inputs and conditions, for example, testing of different types and formats of an exploit that can throw us different scenarios.

Just some thoughts I had since the workflow part I think does not nearly need the same level of work, since there we can just add cargo test unit_test.rs if we just want the unit test to run under a specific condition.