Hi,
I have just started doing a lot of work in a project which uses GoogleTest for unit testing. It doesn't play nicely with Visual Assist...
Tests are declared with either TEST(Suite, TestName) or TEST_F(TestFixture, TestName), and in the VA Outline pane, they all appear as T which is not helpful...
Also, they have matcher functions and mock methods, which don't play nicely with Document Method:
For example, here's the header generated for a matcher function just now:
////////////////////////////////////////////////////////////////////////////////
///
// Function: TransMatches
///
/// @brief
///
/// @param
/// @param
/// @param
/// @param
/// @param
/// (no parameters)
///
/// @retval
///
////////////////////////////////////////////////////////////////////////////////
MATCHER_P3(TransMatches, command, address, len, "")
{
// Implementation redacted
}
Here TransMatches is the matcher method name, command, address and len are the parameters, and the empty string is some sort of name. It would be good if Visual Assist could understand this. There are assorted MATCHER_Pn macros.
I would expect:
////////////////////////////////////////////////////////////////////////////////
///
// Function: TransMatches
///
/// @brief
///
/// @param command
/// @param address
/// @param len
/// (no parameters)
///
/// @retval
///
////////////////////////////////////////////////////////////////////////////////
MATCHER_P3(TransMatches, command, address, len, "")
...
GoogleTest is at https://google.github.io/googletest/
There may be other test frameworks worth supporting as well.
Thanks,
Ian
Support test frameworks - in particular GoogleTest
Posted - Sep 26 2023 : 06:30:31 AM
