Skip to main content

More on getting started with unit testing

In a previous post I talked about how I was finally able to start writing unit tests.  In this post I will discuss how I went from just starting out to where I am now.  This has involved splitting our database access object into two parts, creating an object factory, and a few mock objects.  I think they are mock objects and not stubs, but I may need to read about that a little more before I finish this post.


As much as possible while getting started I have been trying to do TDD (Test Driven Development).  This means I am following the process of writing tests first and then writing code that makes the tests passed.  I did have to make some tests for some existing code before getting started.
As I mentioned in the first post, at work we use a cfc that I wrote to do most of our database interaction.  If you are familiar with active records in Ruby on Rails it is similar to that.  I don't have much experience with rails but I think it is pretty similar anyway.  It doesn't really matter though for the purposes of my unit testing explanation.
Cfcs that extend that one are used in many places in our system and more places use it all the time.  So I decided it was a good object to start writing tests for.  The problem I ran into right away though was that much of what the cfc does is database activity.
We don't use the cfc directly.  It is always extended so I made an object in my tests folder that extends the database cfc.  Then I made a table in our dev database to use for my tests.  Then I had to setup tests for all the existing functions in the cfc.  After that I had a bunch of unit tests that do actual database activity.   I know I'm not supposed to do that, but at the time it was the only way I could get the tests written.
Now that I had tests I was able to make changes without fear of breaking everything.  Over several weeks or months I continued refactoring the code.  Eventually I reduced the number of methods that actually did database activity.  After that I was able to split the database activity into a separate class.
With that done now I was able to create a mock object for the query methods.   I also created an object factory object that allows me to inject the mock database object.  I think I'll stop here and maybe write up a few more details and some conclusions in another post.

Comments

Popular posts from this blog

Getting Hidden App Data From Your Google Drive

Some Android applications use space on your Google Drive to store data.  You can't see this data by browsing drive the normal way.  You can get access to it if you get the access token from the app and do a few other things.

I use an app to keep some notes and other things.  They require getting the paid version of the app to backup your data.  I wanted to see if I could get it myself without paying for the app.  I found out how to do this from this Stackoverflow post http://stackoverflow.com/questions/22832104/see-hidden-app-data-in-google-drive.  The example there uses php. Since I have been learning Python recently, I decided to see if I could do the same thing with Python.

 There is a pretty good explanation of why you need to go through all the steps you need to go through to get your data in the accepted answer for that post, so I won't go into too much detail about that here.


Using IR codes from Broadlink backup file

This is a continuation of yesterdays post about the Broadlink RM2 wifi remote.  I was able to test out using the codes to control my remote today.  They are stored in JSON format in the broadlink backup file.  The backup file is a zip file.  After you extract it there is a folder named SharedData.  There are several files in the folder.  The one that seems to have all the codes is named jsonIrCode.  The data looks like an array of objects, each with a code and some other information.


Setting Up an Angular 5 site on Github Pages

Getting Started

This article will go over all the steps to setup an Angular site on GitHub pages.  The site will use Angular's AOT compiling and be served from the docs folder of the repository.

To start with you can follow the guide here to setup a new Angular project. Then you will need to setup a repository on Github.com.  The name of the repository doesn't matter, this site will use the docs folder, not the specially named repository with USERNAME.github.io as the name.



Project Changes

After that open up the project in your editor and open the .angular.cli.json file.  Change the "outDir" to "docs".  This is where the files will be created when you build the project.  The contents of .angular.cli.json are shown below with all the changes discussed in the article.

Custom Domain

To use a custom domain for your site you need to create a file name CNAME that contains only the domain name.  The GitHub help page explains how to setup DNS and everything else you …