You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Robert Middleton (Jira)" <lo...@logging.apache.org> on 2022/09/24 13:15:00 UTC

[jira] [Resolved] (LOGCXX-527) Mock the clock for tests

     [ https://issues.apache.org/jira/browse/LOGCXX-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Middleton resolved LOGCXX-527.
-------------------------------------
    Resolution: Fixed

> Mock the clock for tests
> ------------------------
>
>                 Key: LOGCXX-527
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-527
>             Project: Log4cxx
>          Issue Type: Improvement
>            Reporter: Robert Middleton
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> The calls that we have for the clock should be changed to allow for mocking.  This will help to fix an issue with running the tests that require a clock to run, e.g. the rolling file appender tests.  By manually advancing the clock, we should be able to avoid any problems with scheduling differences.
> This is also a good place to remove the apr_* calls and replace them with their C++ standard components.
> See this thread for more information: https://lists.apache.org/thread.html/rfc5c780f0aad3a36eae6261cd54316b050f68e1fcb99853935738f30%40%3Cdev.logging.apache.org%3E
> SO example: https://stackoverflow.com/questions/33606482/are-there-facilities-in-stdchrono-to-assist-with-injecting-system-clock-for-un
> fake clock example: https://github.com/korfuri/fake_clock



--
This message was sent by Atlassian Jira
(v8.20.10#820010)