Test-Driving CuTest Unit testing framework (and it's memory leak issues)

I am currently evaluating CuTest as I was supposed to use it for embedded systems development. Using a memory leak detector, I found out that there is a memory leak when suites are nested. I forked it and made some modifications on the CuTest source code to resolve the memory leak. The changes are very simple and was tested very lightly as of the moment. Source Code Link  

Nevertheless, CuTest is a very good lightweight unit testing library.

RSA Encryption/Decryption Example Implementation for C#

Link to source code

Here is a very simple example implementation of RSA in C# using Private and Public key Encryption/Decryption. I also added an interface to be able to quickly switch between storage/loading of public/private keys  either to/from memory or XML files.

AT Command Script Processor's Source Code (new github address)

I placed the source code here.  Compiled with Visual Studio 2013 Community Edition. So far this was tested on the following devices:
- AT GSM Modems
- Bus Pirate
- ESP8266 (AT commands)

The link above contains the link for the Windows executable as well.

Programming Xilinx CoolRunner CPLD XC2C128 via Bus Pirate v3

For the past few days, I am having difficulties to make Bus Pirate v3 work with the stock XSVFplayer frmware JTAG from Dangerous Prototype's website. I fetched the latest source code from the SVN and modified the firmware. Now, my Bus Pirate can upload XSVF files generated by Xilinx ISE to my Xilinx Coolrunner xc2c128 CPLD.

I uploaded the hex file here Link. I used PicKit2 to upload the firmware and I didn't use the Bus Pirate's bootloader.

Protobuf-net - Did I initialize that list or not?

Protobuf-net is a very great binary serializer for .NET. I use it heavily on my project (memory, file, and over-the-wire serialization).

One of the confusions I recently had is that after I initialized a List, I assumed that it will be serialized into the stream. However, having a zero-length List, it always return null whenever protobuf deserializes the stream. I had seen some developers do a null checking or implement null-coalescing operator operations after they deserialize the stream and those null checking are scattered through-out the code (which violates the DRY principle and is ugly).

One very simple work-around for this is to provide a standard constructor and initialize the List on that constructor. Here is a sample unit test code which demonstrates that.

Special thanks to the protobuf-net author: Marc Gravell

My C# Naming Conventions

I would like to share the naming conventions that I am using for C#. Link

I use this as a guideline to be able to make my code more readable (especially for big projects) and to be able to identify the type of variable or method in one glance.

Moq (and primitive mocking) Demo

Here is a simple demonstration of using Moq and using a primitive mocking approach.  Link


The 1st approach (using Moq), takes a bit of a learning curve, but it is worth doing it.

The 2nd approach is easier, but at the expense of creating additional dummy class/es.