You've been asked to develop an LED Driver for ACME Co.'s new device. The hardware isn't ready yet, but the specs are looking pretty good.
The device will have 8 memory mapped, single color, LEDs. The pins are active HIGH.
The low bit maps to LED1; high bit to LED8.
| Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| LED | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
Since the target hardware isn't available yet, the tests must be runnable from the host OS. We do know that we'll be using the Atmel ATxmega128a1 mcu though, so the solution must also compile with the avr-gcc compiler.
For convenience, a docker image is provided with these dependencies pre-installed. The following command will start the build tools container and mount the current working directory.
# from the project root directory
docker run --rm -it -v ${PWD}:/mount rubberduck/led-driver-kataFeel free to add any tools you feel you need, but please make sure they are added to the Dockerfile.
Given the LEDs are off When requested Then all of the LEDs are turned on
Given the LEDs are on When requested Then all of the LEDs are turned off
Given an LED is off When requested Then that LED is turned on And all other LEDs are in their original state
Given an LED is on When requested Then that LED is turned off And all other LEDs are in their original state
When the driver is initialized Then all of the LEDs should be off
There was a bug in the spec. It turns out that the pins are active LOW, not HIGH. All our lights are on when they should be off and vice versa. Go fix the bug.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License