Hello, First of all, I was looking around for a simple to use, preferably header only, test framework for a library I just started working on, because google test is a pain to set up and maintain and I wanted something much more lightweight. I came across yours and gave it a try. Its only been a couple of days, but so far it is just what I needed. So, thanks! Seeing the "#include <windows.h>" removed is what I meant. The biggest issues that I personally have had with including "windows.h" is when you get to socket and network communications code that is trying to be cross platform. Even libraries like boost asio give problems if you include windows.h along with them, or in the wrong order. So, for the project I am using the test framework for now (which is purely a 3D math library), it is not a problem. The only thing I ran into is the min/max issue. However, if I was to use the framework on some of my other projects, especially the ones that do network communication, I think it would be more of a headache. While I have your attention, I do have a question. I haven't studied the documentation closely yet, but I was trying to do something that failed miserably and I'd like to ask directly if its possible: The library I am using the test framework is all header only templates so that the user can use it with float, double (or long double eventually). It would be great to templatize some of the test cases so that I don't have to duplicate them for each of the supported types. Is that possible? Best regards, Marcel

Actually, the ONLY thing windows.h is used for is printing the result with color in the terminal, so removing it won't cause any issue I'll provide a macro to prevent the inclusion of the windows.h header in the next release before the weekends. For the use case that failed miserably can you open an issue for it with detail and if possible with some code snippet. It currently not possible to templatize a test case, that sounds like a good feature, open an issue on what to expect from the template feature. I'll sure to prioritize the two issues after the upcoming release.

Hello MarcelInTO, I just made a new release, which includes the option to compile without the windows.h header file. By simply defining the macro CESTER_EXCLUDE_WINDOWS_H before including cester.h all features depending on windows.h will use an alternative. See this page https://exoticlibraries.github.io/libcester/docs/selective_compilation.html#do-not-include-windows-h for more detail on how to exclude windows.h

See this test for how to exclude windows.h https://github.com/exoticlibraries/libcester/blob/main/test/test_no_windows_h.c On Fri, Mar 12, 2021 at 9:18 PM Azeez Adewale ***@***.***> wrote: