SFML/test/TestUtilities/WindowUtil.hpp

// Header for SFML unit tests.
//
// For a new window module test case, include this header.
// This ensures that string conversions are visible and can be used by doctest for debug output.

#ifndef SFML_TESTUTILITIES_WINDOW_HPP
#define SFML_TESTUTILITIES_WINDOW_HPP

#include <SystemUtil.hpp>

// String conversions for doctest framework
namespace sf
{
class VideoMode;

std::ostream& operator<<(std::ostream& os, const sf::VideoMode& videoMode);
} // namespace sf

#endif // SFML_TESTUTILITIES_WINDOW_HPP
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00			`// Header for SFML unit tests.`
			`//`
Use operator<< for printing during test failure 2021-12-29 13:03:15 +08:00			`// For a new window module test case, include this header.`
Replace Catch with Doctest 2021-12-24 21:31:27 +08:00			`// This ensures that string conversions are visible and can be used by doctest for debug output.`
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00
			`#ifndef SFML_TESTUTILITIES_WINDOW_HPP`
			`#define SFML_TESTUTILITIES_WINDOW_HPP`

Use `<>` for test utilities includes SFML convention is to only use "" includes when the header is in the same directory as the file including it. Because these test util headers are in a separate directory, it makes more sense to include them via <>. 2022-06-26 10:41:32 +08:00			`#include <SystemUtil.hpp>`
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00
Replace Catch with Doctest 2021-12-24 21:31:27 +08:00			`// String conversions for doctest framework`
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00			`namespace sf`
			`{`
Run clang-format 2022-07-05 00:20:58 +08:00			`class VideoMode;`
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00
Run clang-format 2022-07-05 00:20:58 +08:00			`std::ostream& operator<<(std::ostream& os, const sf::VideoMode& videoMode);`
			`} // namespace sf`
Separated test suites into their individual modules - Building per module only requires to have split test utility sections - System module tests are always added, as the system module is always built 2018-08-19 07:30:53 +08:00
			`#endif // SFML_TESTUTILITIES_WINDOW_HPP`