A tester for the project ft_containers at 42
Every functions in the std::uninitialized family will show KOs in the tester because they don't use the allocator passed as a template argument to the container. It will show 'Called destroy on uninitialized memory'.
Set the location of your containers folder in config.sh (variable FT_CONTAINERS)
The tester expects every header files at the root of the folder assigned to FT_CONTAINERS
Every header files are expected to follow STL file names (vector -> vector.hpp, map -> map.hpp, type_traits -> type_traits.hpp, ...)
Run every tests:
./test_containers.sh
Run one or more container tests:
./test_containers.sh <CONTAINER_1> ... <CONTAINER_N>
Run individual tests:
./test_files.sh <CONTAINER> <TEST_1> ... <TEST_N>
Run every benchmark:
./benchmark_containers.sh
Run one or more container benchmarks:
./benchmark_containers.sh <CONTAINER_1> ... <CONTAINER_N>
Run individual benchmarks:
./benchmark_files.sh <CONTAINER> <BENCHMARK_1> ... <BENCHMARK_N>
Examples:
./test_containers.sh vector stack ...
./test_files.sh vector erase clear ...
./benchmark_containers.sh vector map ...
./benchmark_files.sh vector erase insert ...
You can create an executable (debug.out) for debugging a particular test with:
./debug_test.sh <CONTAINER> <TEST>
Example:
./debug_test.sh vector erase
This tester doesn't check for things that shouldn't compile, it only uses the containers in ways that must work. Anyone willing to add this feature is welcome to do so.
It also tracks allocations/dealloctions as well as construction/destruction calls. So, for leak detection/object tracking to work, every allocations, deallocations, contructions and destructions have to be done with the allocator passed as a template argument. This applies to every containers. You should thus verify that all the calls to an allocator are using the template argument allocator and not std::allocator.
Leaks are tracked and bad use of Allocator::construct/Allocator::destroy (Allocator is the template parameter for the container's allocator). Construct calls on initialized memory is a bug because the destructor of T will NOT be called on the old value nor will the operator=. Also, destroy calls on uninitialized memory is also a bug because its calling a destructor on garbage values.
For example, consider this struct:
struct object
{
int* ptr;
object()
{
ptr = new int[10]();
}
object(const object&)
{
ptr = new int[10]();
}
~object()
{
delete[] ptr;
}
};
A vector of the struct object (ft::vector<object>) would leak memory everytime the destructor isn't called. Thus when the tester reports N number of alive objects, consider it to be a bug. This also happens when Allocator::construct is called on already initialized memory.
Issues and pull requests are welcome for improvements and bugfixes!