README.md

libft_rpv

A quick and efficient tester for your libft using Cargo.

Expected file structure

libft
├── libft.a
└── libft_rpv

Usage:

To launch all mandatory tests:

cargo test

To launch only the test of functions containing pattern:

cargo test `pattern`

To add features:

cargo test --features <feature_name_1> --features <feature_name_2>...

Features:

• verbose: Sometimes produces more output when testing
• bonus: Launch all the tests, including bonuses
• fork: Launch all tests in fork.
  Pros: Segfaults can be catched without the tester crashing.
  Cons: Takes more memory and time to execute all tests. Like, a lot of time. But if you can't pass without using forks, then consider fixing them first, before worrying about leaks

Memory leaks check:

After running a cargo test, you can run the quick_valgrind.sh script. It'll take the last executable cargo touched, and launch it into valgrind. You might see bytes leak suppressed. Those comes from cargo itself, or the fork crate that I used. I made ultra specific valgrind suppression files, so it should never conflict with user leaks.

What is not tested by this program

• Norm (As a correcter, be wary, some people found ways of bypass the norminette's check)
• Malloc protection (if a malloc is not protected, it's a potential crash, so it should be a 0) (You can use ./malloc_locator.sh, which is not perfect at all but gives a quick overview.)
• Leaks in case of malloc fail. Be sure to check it yourself, particularly in functions that require lots of allocation, like ft_split

Side note

You already heard it thousands of time, but make sure to create your own test suite. This test suite should only be used for correction purpose. I know that creating tests can get boring, but you'll need it at some point, so learning it now will only benefit you.