Skip to content

Latest commit

 

History

History
28 lines (15 loc) · 1.49 KB

File Logger.md

File metadata and controls

28 lines (15 loc) · 1.49 KB

File Logger Kata

Source: https://github.com/ardalis/kata-catalog

Background

This kata is designed to help develop skill with using mock objects appropriately. The initial steps can be completed using direct infrastructure code, but later steps become increasingly difficult to test without the ability to mock out certain dependencies.

Instructions

  1. Write a class 'FileLogger' with one method, Log(string message).

  2. When this method is called, it should append the message to the end of a file, "log.txt", located in the same folder as the running application (or tests).

  3. If the file doesn't exist, create it. If it does exist, use it and append to it.

  4. Now update the method so that it writes to a file called logYYYYMMDD.txt, where YYYYMMDD corresponds to the current date.

  5. Verify that a new file is created if it doesn't exist on each new day.

  6. The IT manager doesn't want to have to open multiple files on Mondays. Any time logging is occurring on a Saturday or Sunday, have it log to a file called "weekend.txt". If it already exists, it can just append to it.

  7. Actually, the manager just gave us new requirements. The first time you log to a file on a new weekend, make sure you start with a fresh "weekend.txt" file. Rename the old one based on the date of the Saturday of that weekend, e.g. weekend-YYYYMMDD.txt.

Resources