Type parametrised test cases v2

[JoeyGrajciar]

Description

This PR adds the support, docs and some unit tests for type parametrised test cases. This implementation supports arbitrary count of types.

Introduces TEMPLATE_TEST_CASE and TEMPLATE_TEST_CASE_METHOD macros. Usage of these macros is very similar to TEST_CASE and TEST_CASE_METHOD. Difference is that name and description (even empty string) is required as types for test are specified at the end.

Example:

struct Bar {}; 

TEMPLATE_TEST_CASE("Templated test","",int,float, std::string, Bar)
{
    std::vector<TestType> v( 5 );
    REQUIRE( v.size() == 5 );
    REQUIRE( v.capacity() >= 5 );
}

template<typename T>
struct TemplateFixture
{
    TemplateFixture() : m_a( 1 ) {}

    int m_a;
}

TEMPLATE_TEST_CASE_METHOD(TemplateFixture,
    "A TEMPLATE_TEST_CASE_METHOD based test run that fails", 
    "[.][class][template][failing]", int, float, double)
{
        REQUIRE( TemplateFixture<TestType>::m_a == 2 );
}

Difference to #1425 is that now there will test invoker registered for each type specified. Former PR added one test invoker with multiple sections for each type, calling the templated test function with type.

Implementation of these test cases was heavily inspired by Doctest.

GitHub Issues

#46 #357 #850 ...

[codecov]

Codecov Report

Merging #1437 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1437      +/-   ##
==========================================
- Coverage   80.31%   80.28%   -0.03%     
==========================================
  Files         120      120              
  Lines        3403     3403              
==========================================
- Hits         2733     2732       -1     
- Misses        670      671       +1

[myrgy]

Is there any progress with that PR?
Is it going to be merged?
Thanks

[JoeyGrajciar]

@myrgy after some minor improvements it is now waiting on review :) please be patient :) feel free to pull locally these changes and do some tests with it and share your opinions about it :)

[horenmar]

This is first set of notes, I still have to dive into the macro hell.

[horenmar]

Found only two, small, nitpicks in the implementation itself. Not sure if it means that I don't understand the preprocessor enough, or that there were only these two. 😃

I'll check the modified documentation tomorrow.