Troubleshooting IO issues using LoggingIoAbstraction
Within the MockIoAbstraction.h header there is an implementation of BasicIoAbstraction that delegates through a logging layer. If you are having difficulty determining what your code is sending and receiving, this could be useful.
Unit testing support within the library
This library itself is quite well tested using AUnit, and further it makes unit testing your code easier. There is a MockIoAbstraction that provides very easy support for mocking out an IoAbstraction.
There is a simulated version of task manager that can assist with getting hold of the registered tasks and a few other useful utility methods.
There is a simulated version of the EepromAbstraction, this uses a small amount of memory to store the state, to avoid writes to ROM during testing.
These Mock interfaces are fully documented in the reference docs.
Other pages within this category
- Timed blink - IO Abstraction library example
- Simple Collection - btree list
- Rotary encoder with non-polling (interrupt based) switches from PCF8574
- IoAbstraction: Using matrix keyboards and keypads
- Arduino Button presses that are handled like events
- Liquid Crystal fork example using IO Abstraction library - examples
- PCF8574 i2c - IO Abstraction library example
- EEPROM implementations that are seamless between 8 and 32 bit
- IoAbstraction - Cross platform build support
- Using Arduino Pins and Io Expanders at the same time
- Working with Analog input events in IoAbstraction
- IoAbstraction Analog Core documentation
- IoAbstraction: Arduino Pins, IO Expanders, Shift Registers using same code
- IoAbstraction: Switches and rotary encoder documentation
- IoAbstraction: troubleshooting and unit testing
You'll also find me on:
Contact Us
