Programming

5 readers

2 users here now

This magazine is dedicated to discussions on programming languages, software development, and coding. Whether you are a beginner programmer or an experienced developer, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as coding languages, software engineering, web development, and more. From the latest trends and frameworks to tips and tricks for debugging, this category covers a wide range of topics related to programming.

founded 2 years ago

Have you ever mocked your logger in a test, or wished you could? That is something like (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by bluGill@kbin.social to c/programming@kbin.social

4 comments fedilink hide all child comments

Have you ever mocked your logger in a test, or wished you could? That is something like

TEST(some test name)

    mockLogger logger

    logger.expect_call(log("some string"))

    DoSomething(logger)

#programming

top 4 comments

sorted by: hot top controversial new old

[–] DmMacniel@feddit.de 0 points 1 year ago (1 children)

Why would you want to mock a logger? Aren't the different Log Levels already enough?

[–] bluGill@kbin.social 1 points 1 year ago

@DmMacniel so you can prove some interesting thing is really logged? maybe someone else has a different reason.

[–] tve@mastodon.social 0 points 1 year ago (1 children)

@bluGill If you have a need to mock a logger, you probably should have an interface dedicated to those logs.

It is also recommended to have dedicated loggers used in each domain, rather than allowing logging everything and everywhere, which may lead to sanitizing log inputs everywhere to be in control and not expose any security issues.

But in many cases that may also be overkill. As always, it depends.

[–] bluGill@kbin.social 1 points 1 year ago

@tve I didn't ask how to do it, I asked if anyone else has done it.