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 Catch2 for debug output.

#pragma once

#include <SystemUtil.hpp>
#include <string>

std::string runDisplayTests();

// String conversions for Catch2
namespace sf
{
class VideoMode;

std::ostream& operator<<(std::ostream& os, const 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			`// 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.`
Switch to Catch2 2023-01-18 12:51:08 +08:00			`// This ensures that string conversions are visible and can be used by Catch2 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
Replaced Header Guards with Pragma Once 2022-12-21 12:17:38 +08:00			`#pragma once`
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
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>`
Switch to Catch2 2023-01-18 12:51:08 +08:00			`#include <string>`
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
Switch to Catch2 2023-01-18 12:51:08 +08:00			`std::string runDisplayTests();`
Add tests for `sf::WindowBase` 2023-02-04 15:06:22 +08:00
Switch to Catch2 2023-01-18 12:51:08 +08:00			`// String conversions for Catch2`
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
Remove unnecessary `sf::` usage 2022-07-05 13:46:34 +08:00			`std::ostream& operator<<(std::ostream& os, const VideoMode& videoMode);`
Run clang-format 2022-07-05 00:20:58 +08:00			`} // namespace sf`