Software Qa Engineer
CurrentI've been working with RedIron Technologies helping in many different ways to create multi-platform integrated solutions for Point of Sale. With all the partner companies we develop alongside, communication is a must, and I am no stranger to a fast-paced, and stressful atmosphere with shifting deadlines.For the first 2 months, a partner and I learned how the main software product was architected, and developed a plan to bring Continuous Integration (Jenkins), Package Management (Nuget), and multi .NET framework targeting into the whole process. We automated the creation of MSI installer files through the might of WIX, and dropped all of this into the dev process at the same time at the 6 month mark. Along the way, I researched a lot of tools to make development easier, and we eventually created Nuget packages with MSBuild target files that modify the behaviour when you build csproj and vcxproj files. We hooked StyleCop into one such package so that our devs can't escape the warnings and are forced to clean their code.After that, I learned that using System.Reflection, you can discover test files for NUnit to run (data driven testing with XML). I did test driven development for a while after that until we had a huge demand for quality in the process. I've since been mixing my time between acceptance testing and setting up GUI automation tests using AutoHotkey coupled with NUnit for validation. Something I've learned on the way, is that End to End testing is costly. To mitigate the cost you can mix very small bits of automation into your manual testing which can save tons of time in the long run.
