test_monitoring_adapter.cpp File Reference

Unit tests for monitoring_adapter (Phase 3) More...

#include "../../database/integrated/adapters/monitoring_adapter.h"
#include <chrono>
#include <iostream>
#include <cassert>

Include dependency graph for test_monitoring_adapter.cpp:

Go to the source code of this file.

Macros
#define	TEST(name)
#define	RUN_TEST(name)
#define	ASSERT_TRUE(condition)
#define	ASSERT_FALSE(condition)

Functions
void	test_configuration_construction ()
void	test_adapter_construction ()
void	test_api_availability_basic ()
void	test_api_availability_metrics ()
void	test_api_availability_health ()
void	test_api_availability_prometheus ()
void	test_api_availability_reset ()
void	test_multiple_instances ()
void	test_move_semantics ()
void	test_destructor_safety ()
int	main ()

Variables
int	tests_passed = 0
int	tests_failed = 0

Detailed Description

Unit tests for monitoring_adapter (Phase 3)

These are lightweight API tests that verify the adapter interface without requiring the actual monitoring_system to be available.

For full integration testing with monitoring_system, run the integration test suite instead.

Definition in file test_monitoring_adapter.cpp.

Macro Definition Documentation

ASSERT_FALSE

#define ASSERT_FALSE

(

condition

)

Value:

ASSERT_TRUE(!(condition))

Definition at line 47 of file test_monitoring_adapter.cpp.

ASSERT_TRUE

#define ASSERT_TRUE

(

condition

)

Value:

    if (!(condition)) { \
        throw std::runtime_error("Assertion failed: " #condition); \
    }

Definition at line 42 of file test_monitoring_adapter.cpp.

#define ASSERT_TRUE(condition) \
    if (!(condition)) { \
        throw std::runtime_error("Assertion failed: " #condition); \
    }

Referenced by test_configuration_construction().

RUN_TEST

#define RUN_TEST

(

name

)

Value:

    do { \
        std::cout << "Running test: " << #name << " ... "; \
        try { \
            test_##name(); \
            std::cout << "PASSED\n"; \
            tests_passed++; \
        } catch (const std::exception& e) { \
            std::cout << "FAILED: " << e.what() << "\n"; \
            tests_failed++; \
        } \
    } while(0)

Definition at line 29 of file test_monitoring_adapter.cpp.

#define RUN_TEST(name) \
    do { \
        std::cout << "Running test: " << #name << " ... "; \
        try { \
            test_##name(); \
            std::cout << "PASSED\n"; \
            tests_passed++; \
        } catch (const std::exception& e) { \
            std::cout << "FAILED: " << e.what() << "\n"; \
            tests_failed++; \
        } \
    } while(0)

Referenced by main().

TEST

#define TEST

(

name

)

Value:

void test_##name()

Definition at line 28 of file test_monitoring_adapter.cpp.

Function Documentation

main()

int main

(

)

Definition at line 199 of file test_monitoring_adapter.cpp.

           {
    std::cout << "=== Monitoring Adapter API Tests (Phase 3) ===\n";
    std::cout << "Note: These tests verify API availability only.\n";
    std::cout << "For full integration testing, run integration test suite.\n\n";
 
    RUN_TEST(configuration_construction);
    RUN_TEST(adapter_construction);
    RUN_TEST(api_availability_basic);
    RUN_TEST(api_availability_metrics);
    RUN_TEST(api_availability_health);
    RUN_TEST(api_availability_prometheus);
    RUN_TEST(api_availability_reset);
    RUN_TEST(multiple_instances);
    RUN_TEST(move_semantics);
    RUN_TEST(destructor_safety);
 
    std::cout << "\n=== Test Summary ===\n";
    std::cout << "Passed: " << tests_passed << "\n";
    std::cout << "Failed: " << tests_failed << "\n";
 
    if (tests_failed == 0) {
        std::cout << "=== All tests passed! ✓ ===\n";
        return 0;
    } else {
        std::cout << "=== Some tests failed! ✗ ===\n";
        return 1;
    }
}

References RUN_TEST, tests_failed, and tests_passed.

test_adapter_construction()

void test_adapter_construction

(

)

Definition at line 68 of file test_monitoring_adapter.cpp.

                           {
    db_monitoring_config config;
    config.enable_metrics = true;
 
    // Should be able to construct adapter
    monitoring_adapter monitor(config);
 
    // Construction should succeed
    // Note: Actual initialization may require monitoring_system
}

References database::integrated::db_monitoring_config::enable_metrics.

test_api_availability_basic()

void test_api_availability_basic

(

)

Definition at line 80 of file test_monitoring_adapter.cpp.

                             {
    db_monitoring_config config;
    config.enable_metrics = false; // Disable to avoid external dependencies
 
    monitoring_adapter monitor(config);
 
    // These methods should be available (may no-op if monitoring disabled)
    monitor.record_connection_acquired();
    monitor.record_connection_released();
    monitor.record_query_execution(std::chrono::microseconds(100), true);
    monitor.record_transaction_begin();
    monitor.record_transaction_commit();
    monitor.record_transaction_rollback();
    monitor.update_pool_stats(1, 5, 10);
 
    // If we get here without crash, API is available
}

References database::integrated::db_monitoring_config::enable_metrics, database::integrated::adapters::monitoring_adapter::record_connection_acquired(), database::integrated::adapters::monitoring_adapter::record_connection_released(), database::integrated::adapters::monitoring_adapter::record_query_execution(), database::integrated::adapters::monitoring_adapter::record_transaction_begin(), database::integrated::adapters::monitoring_adapter::record_transaction_commit(), database::integrated::adapters::monitoring_adapter::record_transaction_rollback(), and database::integrated::adapters::monitoring_adapter::update_pool_stats().

Here is the call graph for this function:

test_api_availability_health()

void test_api_availability_health

(

)

Definition at line 114 of file test_monitoring_adapter.cpp.

                              {
    db_monitoring_config config;
    config.enable_health_checks = false;
 
    monitoring_adapter monitor(config);
 
    // Should be able to call health check (may return unhealthy if not init)
    auto health_result = monitor.check_health();
    // Result structure should be valid even if health check failed
}

References database::integrated::adapters::monitoring_adapter::check_health(), and database::integrated::db_monitoring_config::enable_health_checks.

Here is the call graph for this function:

test_api_availability_metrics()

void test_api_availability_metrics

(

)

Definition at line 99 of file test_monitoring_adapter.cpp.

                               {
    db_monitoring_config config;
    config.enable_metrics = false;
 
    monitoring_adapter monitor(config);
 
    // Should be able to call these methods (may return default/empty values)
    auto metrics_result = monitor.get_database_metrics();
    // Result may be ok or error depending on initialization state
 
    auto metrics_snapshot_result = monitor.get_metrics();
    // Result may be ok or error depending on initialization state
}

References database::integrated::db_monitoring_config::enable_metrics, database::integrated::adapters::monitoring_adapter::get_database_metrics(), and database::integrated::adapters::monitoring_adapter::get_metrics().

Here is the call graph for this function:

test_api_availability_prometheus()

void test_api_availability_prometheus

(

)

Definition at line 126 of file test_monitoring_adapter.cpp.

                                  {
    db_monitoring_config config;
    config.enable_prometheus_export = false;
 
    monitoring_adapter monitor(config);
 
    // Should be able to call prometheus export (may return empty string)
    auto prometheus_text = monitor.export_prometheus_metrics();
    // Should return a string (may be empty)
}

References database::integrated::db_monitoring_config::enable_prometheus_export, and database::integrated::adapters::monitoring_adapter::export_prometheus_metrics().

Here is the call graph for this function:

test_api_availability_reset()

void test_api_availability_reset

(

)

Definition at line 138 of file test_monitoring_adapter.cpp.

                             {
    db_monitoring_config config;
    config.enable_metrics = false;
 
    monitoring_adapter monitor(config);
 
    // Should be able to call reset without crash
    monitor.reset();
}

References database::integrated::db_monitoring_config::enable_metrics, and database::integrated::adapters::monitoring_adapter::reset().

Here is the call graph for this function:

test_configuration_construction()

void test_configuration_construction

(

)

Definition at line 54 of file test_monitoring_adapter.cpp.

                                 {
    db_monitoring_config config;
    config.enable_metrics = true;
    config.enable_profiling = true;
    config.enable_health_checks = true;
    config.metrics_interval = std::chrono::seconds(60);
    config.enable_prometheus_export = true;
 
    // Should be able to create config without errors
    ASSERT_TRUE(config.enable_metrics == true);
    ASSERT_TRUE(config.metrics_interval.count() == 60);
}

References ASSERT_TRUE, database::integrated::db_monitoring_config::enable_health_checks, database::integrated::db_monitoring_config::enable_metrics, database::integrated::db_monitoring_config::enable_profiling, database::integrated::db_monitoring_config::enable_prometheus_export, and database::integrated::db_monitoring_config::metrics_interval.

test_destructor_safety()

void test_destructor_safety

(

)

Definition at line 180 of file test_monitoring_adapter.cpp.

                        {
    // Test that adapter can be constructed and destroyed safely
    {
        db_monitoring_config config;
        config.enable_metrics = false;
 
        monitoring_adapter monitor(config);
        monitor.record_connection_acquired();
 
        // Destructor will be called here
    }
 
    // Should not crash
}

References database::integrated::db_monitoring_config::enable_metrics, and database::integrated::adapters::monitoring_adapter::record_connection_acquired().

Here is the call graph for this function:

test_move_semantics()

void test_move_semantics

(

)

Definition at line 166 of file test_monitoring_adapter.cpp.

                     {
    db_monitoring_config config;
    config.enable_metrics = false;
 
    monitoring_adapter monitor1(config);
 
    // Should support move construction
    monitoring_adapter monitor2(std::move(monitor1));
 
    // Moved-to instance should be usable
    monitor2.record_connection_acquired();
}

References database::integrated::db_monitoring_config::enable_metrics, and database::integrated::adapters::monitoring_adapter::record_connection_acquired().

Here is the call graph for this function:

test_multiple_instances()

void test_multiple_instances

(

)

Definition at line 149 of file test_monitoring_adapter.cpp.

                         {
    db_monitoring_config config1;
    config1.enable_metrics = false;
 
    db_monitoring_config config2;
    config2.enable_metrics = false;
 
    // Should be able to create multiple adapters
    monitoring_adapter monitor1(config1);
    monitoring_adapter monitor2(config2);
 
    // Both should be usable
    monitor1.record_connection_acquired();
    monitor2.record_connection_acquired();
}

References database::integrated::db_monitoring_config::enable_metrics, and database::integrated::adapters::monitoring_adapter::record_connection_acquired().

Here is the call graph for this function:

Variable Documentation

tests_failed

int tests_failed = 0

Definition at line 26 of file test_monitoring_adapter.cpp.

Referenced by main().

tests_passed

int tests_passed = 0

Definition at line 25 of file test_monitoring_adapter.cpp.

Referenced by main().