Implement unit tests and CI with GitHub Actions

[GianIac]

Add basic test coverage for:

• obfuscate_string! macro behavior
• obfuscate_flow! integration
• Utility methods

Also, set up a GitHub Actions workflow that runs cargo test on every push or pull request.
CI is crucial to ensure library stability as it evolves.

[bordolot]

Would you like unit tests to be placed inside in each corresponding file as is suggested in the rust-book or in a separate folder alongside the integration tests?

[GianIac]

Let’s follow the Rust Book convention: keep unit tests alongside the code in each corresponding file (under a #[cfg(test)] mod tests), and reserve the tests/ directory for integration tests. This keeps tests close to the code and works well with GitHub reviews.

[bordolot]

I'm wondering which functions/methods should we include in UNIT tests?

In the rust_code_obfuscator_core crate:

• I think all functions in crypto module should be tested.
• Do you think this fmt method from errors method should be tested?
• In obfuscator we have two macros which you mentioned: obfuscate_string! and obfuscate_flow!. I think they should be tested in integration tests. But do we really need to test them? What's done for now is just changing the names of macros defined in the cyptify crate. Shouldn't we assume that this macros are already tested. I looked at the cyptify crate and I noticed that these crates were somehow tested, but it's hard for me to assess how well it was done now.
• Does generate_obf_suffix should be tested? Its extremely simple...

In the obfuscator_derive crate:

• A marco in this crate should be tested in integration. Do you agree?

In the obfuscator_cli crate:
Do you agree that all functions in file_io, processor, project_mode and utils should be unit tested?

For now I write some tests for the crypto module in the rust_code_obfuscator_core crate. And I could create a PR.

[bordolot]

I started writing tests for the file_io module.

I want to create some temp files to test the gather_rust_files function. I'm wondering what would be better:

• creating our own utility test functions for creation and deleting test files e.g. in a tests/tempdata folder
• or, using the tempfile library which automates the entire process?