Unit Testing

Consultants Ate My Unit Tests

About six years ago I was working as a solo software developer consultant for a web-based product at a small company. The backend piece involved some ETL from ancient 16-bit FoxPro into SQL Server which helped to provide an easier data schema and robust reporting. This project was not seeking to replace FoxPro since it’s been running the back office business for 10+ years without issue. Rather we opted to perform a nightly data dump into SQL server, since the data would be a lot easier to work with using ASP.NET, a requirement determined by the business, a traditional .NET shop. With this architecture, the webserver was not directly dependent on FoxPro. In the end, each could be maintained individually. Each could fail and not impact the other. Hopefully, neither fail but things happen. On second thought things are going to happen, plan and be prepared.

Unit Testing Allowed Me to Pick Up My Kid Today

As a parent, I cannot afford to waste time at work (my employer does not want me too either). Thus, I try to automate as many tasks as possible. I organize tasks with Trello and synchronize notes, ideas, questions, requirements, and documents using Github, OneNote, and SharePoint. I schedule and run timely meetings. And I try to not waste other people’s time. I also unit test as much as possible. Wait. What? Doesn’t unit testing take up too much time? Doesn’t it impact project timelines?

Hello World! Android Unit Testing with Espresso

Tackling android unit testing has more than one approach. A library file or class file(s) without android dependencies can utilize JUnit or any other Java unit testing framework. However, as soon as the code that you want to test is dependent on Activity Context you write instrumentation tests that execute on actual devices or virtual devices.