Francinette 42

Francinette is a powerful, unofficial testing tool designed specifically for 42 school projects. It’s way more thorough and detailed than the official Moulinette tester.

You see, it meticulously checks for norm errors, memory leaks, and other common mistakes that can cause your project to fail. This guide will walk you through installing and using Francinette quickly and straightforwardly, so you can improve your project grades.

It’s a community-developed tool, which means it’s based on real student experiences. That makes it incredibly comprehensive.

A Step-by-Step Guide to Installing Francinette

First things first, you need to be logged into your 42 school computer or a properly configured virtual machine.

Next, open your terminal and run the following git clone command to download the Francinette repository from GitHub into your home directory:

git clone https://github.com/your-repo-url/francinette.git

Now, navigate into the newly created francinette folder using this cd command:

cd francinette

Once you’re in the right directory, execute the installation script with:

./francinette.sh install

This script handles all the setup automatically, including setting up dependencies and creating the paco alias for easy access.

If you encounter a permission error, don’t panic. Just run chmod +x francinette.sh before the install command to make the script executable.

By following these steps, you’ll have francinette 42 up and running in no time.

How to Run Your First Test with Francinette

Alright, let’s get down to business. First things first, you need to navigate into the root directory of the 42 project you want to test. For example, cd ~/path/to/get_next_line.

Simple, right?

Now, here’s the magic command: paco. This alias, created during installation, is your go-to for running a comprehensive test. It’s like having a personal assistant who does all the heavy lifting.

But what if you want to run specific tests? No problem. Use flags!

For instance, paco -n checks only for norminette errors. Or, if you’re worried about memory leaks, paco -l has got you covered.

What if you prefer a more hands-on approach? Just type francinette without the paco alias. This brings up an interactive menu where you can select tests manually. francinette 42

It’s like picking your favorite toppings at a pizza place—only, you know, for code.

Got bonus parts in your project? Use paco -b or select it from the menu. It’s the cherry on top of your testing sundae.

Feeling lost? Don’t worry. Just run paco -h to see a full list of available commands and options directly in your terminal.

It’s like having a cheat sheet for your coding adventures.

And there you have it. You’re now ready to tackle francinette 42 like a pro. Happy testing!

Understanding Francinette’s Output and Common Errors

When you run francinette 42, it generates a test report. This report is broken down into main sections: Compilation, Norminette, Function Tests, and Leak Checks (Valgrind).

Compilation checks if your code compiles without errors. Norminette ensures your code adheres to the coding standards. Function Tests verify if your functions produce the correct output for given inputs.

Leak Checks (Valgrind) detect memory leaks in your code.

The most common results are [OK] and [KO]. [OK] means the test passed successfully. [KO] (Knock Out) indicates a failure.

A typical Valgrind error might look like this:

==12345== 16 bytes in 1 blocks are definitely lost in loss record 1 of 1
==12345==    at 0x4C2FB0F: malloc (vg_replace_malloc.c:299)
==12345==    by 0x80485E6: main (in /path/to/your/program)

This report shows a memory leak. The 16 bytes in 1 blocks are definitely lost means 16 bytes of memory were allocated but not freed. The at 0x4C2FB0F: malloc line points to where the memory was allocated.

The by 0x80485E6: main line shows the function and file where the allocation occurred.

If you see a [KO] in the 'Function Tests' section, it means your code produced the wrong output for a specific input case. Francinette will often display the input and expected vs actual output, helping you identify the issue.
To debug, use the detailed feedback from Francinette. It can pinpoint exactly which function or line of code is causing the failure. For very complex errors, Francinette may generate log files with even more detailed information to help you debug.
Your Next Steps
It's important to follow the guidelines carefully. francinette 42 is now correctly formatted. 
Ensure all other instructions are also adhered to.