An advanced unit-test written in c++ for 42 school's ft_containers project or other c++ containers.
For the 'list' container we generate 162555 tests for example.
As explained below we use threads and forks to speed up the testing.
-
Change path to your container's '.hpp' in 'main.hpp'
-
Optional: Set G_ERROR_LIMIT in 'main.cpp' to keep testing until the error limit is attained
-
Optional: Set G_STOP_AT_TEST in 'main.cpp' to keep testing independently of errors
Launch non-const unittest
make <list/stack/map/queue/vector>
See results by comparing '/output/me' with '/output/real'.
Infinite loop results can be checked in 'output/tmp_my' and 'output/tmp_real'.
See tests in '/src'.
Launch const unittest
make const
You should have a certain amount of compilation errors not more or less.
Because this unittest is very advanced I doubt it will be used by others, as validating it is probably way more complex than what is demanded in 42 school project ft_containers.
Using processes to test segfaults and sigabort, so that the error gets catched and exits the child process.
For error messages that cannot be catched like memory freed not allocated, we redirect the stderr to /dev/null.
Infinte loops cannot be catched unfortunately, but result can be viewed in output/tmp_my and output/tmp_real.
Temp files are used, if program blocks and ctrl-c is used to quit program, tmp files won't be deleted and can be viewed to debug, useful for infinite loops.
Threads used with the failed idea of increasing the programs speed, failed due to impossibility to write to multiple fds at the same time.
But in the end threads increased program speed a lot by increasing the speed of fork.
Fork gets slower as parent process uses more memory both stack and heap memory, due to its copying feature, using threads detaches from parent process and speeds up the forks, threads increased program speed 5X.
When excess test errors are written to file, fills up computer memory and creates bug.
Solution is to not check in the end but after each test and only write errors to files, max number errors before quiting.
Combination of tests are generated based on different container objects.
To test vector container correctly set its buffer_size to 10.
Allocator_type.
Undefined behavior; unintialized memory, SIGABORT, SEGFAULT, ...
Max size as you can have different answer than real one. You must be able to explain, your own implementation of it.
Destructor is not tested and memeory leaks are not tested.
Special types like std::string.