Refactor Unit Tests #136

New Issue

sdaveb · 2023-07-19T17:04:06Z

sdaveb commented

2023-07-19 17:04:06 +00:00

Problem Description

Some of the unit tests are sill using Catch2's clunky syntax.
Unit tests have certain warnings disabled because FakeIt and Catch2 were emitting warnings.

Proposed Solution

(if any)

Wrap the syntax around the macros defined in test-includes.hpp
Disable the warnings for the external dependencies using GCC pragmas

## Problem Description - Some of the unit tests are sill using Catch2's clunky syntax. - Unit tests have certain warnings disabled because FakeIt and Catch2 were emitting warnings. ## Proposed Solution ### (if any) - Wrap the syntax around the macros defined in test-includes.hpp - Disable the warnings for the external dependencies using GCC pragmas

sdaveb added this to the Finalize the engine core milestone 2023-07-19 17:04:06 +00:00

sdaveb added the

task

label 2023-07-19 17:04:06 +00:00

sdaveb self-assigned this 2023-07-19 17:04:06 +00:00

sdaveb added this to the libFramework API project 2023-07-19 17:04:07 +00:00

sdaveb changed title from ~~Modernize unit tests so they use the new BEING_TEST_SUITE wrapper macros~~ to Modernize unit tests so they use the new BEGIN_TEST_SUITE wrapper macros

2023-07-20 14:58:33 +00:00

sdaveb changed title from ~~Modernize unit tests so they use the new BEGIN_TEST_SUITE wrapper macros~~ to Refactor Unit Tests

2023-08-02 03:13:51 +00:00

sdaveb referenced this issue from a commit

2023-08-06 15:39:26 +00:00

Disable certain warnings at the file-level rather than build-level

sdaveb referenced this issue from a commit

2023-08-06 15:39:27 +00:00

Refactor component classes and unit-tests.

sdaveb referenced this issue from a commit

2023-08-06 20:21:26 +00:00

Refactor component classes and unit-tests.