Standard-of-Iron/tests

Standard of Iron - Test Suite

This directory contains unit and integration tests for the Standard of Iron project using Google Test.

Structure

tests/
├── core/              # Core engine tests
│   └── serialization_test.cpp  # Entity/World serialization tests
├── db/                # Database tests
│   └── save_storage_test.cpp   # SQLite save/load tests
└── CMakeLists.txt     # Test build configuration

Running Tests

Build and Run All Tests

make test

Run Tests Directly

cd build
./bin/standard_of_iron_tests

Run Specific Tests

# Run only serialization tests
./bin/standard_of_iron_tests --gtest_filter=SerializationTest.*

# Run only database tests
./bin/standard_of_iron_tests --gtest_filter=SaveStorageTest.*

# Run a specific test case
./bin/standard_of_iron_tests --gtest_filter=SerializationTest.EntitySerializationBasic

Verbose Output

./bin/standard_of_iron_tests --gtest_color=yes

Test Categories

Core Serialization Tests (core/serialization_test.cpp)

Tests for JSON serialization and deserialization of game objects:

• Entity serialization: Basic entity save/load
• Component serialization: All component types fully tested
  • TransformComponent (position, rotation, scale)
  • RenderableComponent (mesh, texture, visibility, color)
  • UnitComponent (health, speed, vision, nation)
  • MovementComponent (targets, paths, velocity)
  • AttackComponent (range, damage, combat modes)
  • AttackTargetComponent (target tracking, chase behavior)
  • PatrolComponent (waypoints, patrol state)
  • ProductionComponent (build queues, rally points)
  • BuildingComponent (building marker)
  • AIControlledComponent (AI flag)
  • CaptureComponent (capture progress, player state)
• Round-trip testing: Serialize→Deserialize→Verify data integrity for all components
• Complete entity: Test entity with all components attached
• Edge cases: Missing fields, malformed JSON, default values
• File I/O: Save to file and load from file

Database Integration Tests (db/save_storage_test.cpp)

Tests for SQLite-based save game storage:

• Initialization: In-memory database setup
• Save/Load: Store and retrieve save slots
• Schema management: Database schema creation and validation
• Error handling: Non-existent slots, constraint violations
• Complex data: Large saves, complex metadata, special characters
• CRUD operations: List, delete, and overwrite slots

Adding New Tests

1. Create a New Test File

#include <gtest/gtest.h>
// Include necessary headers

class MyFeatureTest : public ::testing::Test {
protected:
    void SetUp() override {
        // Setup code
    }

    void TearDown() override {
        // Cleanup code
    }
};

TEST_F(MyFeatureTest, TestCase) {
    // Test code
    EXPECT_EQ(expected, actual);
}

2. Add to CMakeLists.txt

add_executable(standard_of_iron_tests
    core/serialization_test.cpp
    db/save_storage_test.cpp
    your_category/your_test.cpp  # Add your test here
)

3. Rebuild and Run

make test

Test Conventions

Naming

• Test suite names should match the class/feature being tested
• Test case names should describe what is being tested
• Use descriptive names: TEST_F(SerializationTest, EntityDeserializationRoundTrip)

Assertions

• Use EXPECT_* for non-fatal assertions (test continues)
• Use ASSERT_* for fatal assertions (test stops)
• Common assertions:
  • EXPECT_EQ(a, b) - equality
  • EXPECT_TRUE(condition) - boolean true
  • EXPECT_FLOAT_EQ(a, b) - floating-point equality
  • EXPECT_NE(a, b) - not equal

Test Organization

• Group related tests in the same test fixture
• Use descriptive test names
• Test one thing per test case
• Keep tests independent

Dependencies

The test suite uses:

• Google Test (v1.14.0) - Testing framework
• Qt6/Qt5 - Core, Gui, SQL modules
• engine_core - Core game engine library
• game_systems - Game systems library

Continuous Integration

Tests are automatically run in CI when:

• Pull requests are created
• Code is pushed to main branch
• Release builds are created

Coverage

Current test coverage focuses on:

• ✅ Complete entity and component serialization (all 11 serializable components)
  • TransformComponent, RenderableComponent, UnitComponent
  • MovementComponent, AttackComponent, AttackTargetComponent
  • PatrolComponent, ProductionComponent, BuildingComponent
  • AIControlledComponent, CaptureComponent
• ✅ World serialization (multi-entity persistence)
• ✅ SQLite save/load operations (in-memory testing)
• ✅ Database CRUD operations (create, read, update, delete)
• ✅ Error handling and edge cases (missing fields, malformed JSON)
• ✅ Round-trip testing for data integrity (all components)

Future coverage should include:

• Terrain serialization
• AI system testing
• Combat system testing
• Pathfinding tests
• Production system tests

Troubleshooting

Tests Not Found

If tests aren't being discovered:

rm -rf build
make configure
make build

Database Lock Errors

Tests use in-memory databases (:memory:), so file locks shouldn't occur. If they do:

• Check for orphaned test processes
• Restart your terminal

Qt-related Errors

Ensure Qt development packages are installed:

make install  # Installs dependencies

References

• Google Test Documentation
• Google Test Primer
• Google Test Advanced Guide