February 23, 2016ALM,Agile,Quality Assurance
The Ishikawa, or Fishbone, diagram (or, affectionately known as the “Fishikawa” diagram), is one of the easiest diagrams to create. No special software is needed, per se. The content for the Ishikawa diagram is constructed using The 5 Why’s as discussed in the previous post. The answer to each question can be classified under one of six outside factors which makes up a bone from the fish’s scale.
Quality Assurance is not simply measuring the quality of an application. It’s also measuring the quality of your development. More times than not, development teams become so focused on “fixing bugs” that we “miss the forest for the trees” – we don’t stop to assess the quality of the development process. What good are our bug fixes if we simply introduce new bugs into the system? How often are we introducing new bugs? Is there a feature set or an area of the application that seems to have more bugs than other areas? Is a developer more prone to creating bugs? With all of the tools that we have at our disposal, it amazes me how little quality assurance tracks the actual development quality. Instead, we merely have a backlog of bugs which we keep increasing with each new iteration.
Want to $watch an object in Angular, but ignore changes on certain properties? Here’s a function that will help you out:
And here’s how to use it…
And, finally a jsfiddle example.
I’ve been developing a LOT of Angular applications lately. Some of them are hybrid projects (Angular w/ MVC); some of my projects have been completely separated (Angular for client-side, with a separate project for an API). Regardless, I always want to ensure that my code has been thoroughly tested with unit tests and acceptance (E2E) tests. When developing hybrid projects, my preferred IDE is Visual Studio. When developing a pure, client-side project, my preferred IDE is Visual Studio Code as it has a lot less remnants/artifacts tied to a solution (.vs, .xproj, .csproj, etc.) eliminating the need for a ridiculously large .gitignore file. Additionally, I will use WebStorm depending on the need.
Jasmine is a great framework for providing both unit testing and end-to-end, acceptance testing. Coupled with Karma, Jasmine can monitor file changes to our client-side code and execute tests on every file change in order to ensure that all tests are always passing. In this blog post, I will demonstrate how to set up and use Karma and Jasmine in both development environments.
November 4, 2015C#,ASP.NET,MVC,Visual Studio,ALM,Test Driven Development,Unit Testing
The other day I was writing some unit tests for testing my MVC application’s forms authentication classes. I needed to Mock the System.Web.HttpContext object. There are a couple of ways to do this depending on the version of Visual Studio you are using (i.e. Professional, Premium/Ultimate/Enterprise) and how deep you wish to provide some default data. One takes a little more leg work and requires some manual data setting, but gives you greater control. While the other requires less coding for simple basic use.
November 3, 2015C#,ASP.NET,Visual Studio,ALM,Test Driven Development,Unit Testing
The other day I was writing some unit tests on an MVC project. I needed to mock (fake) an HttpRequest object using the System.Web assembly. However, there was a strange issue in creating the fakes assembly and adding it to my Visual Studio solution. Namely, it didn’t show up.Read more
October 29, 2015C#,MVC,Visual Studio,ALM,Test Driven Development,Behavior Driven Development,Unit Testing
Do your MVC model properties contain attributes? Have you ever wanted to unit test the properties to verify that the ModelState fails or succeeds based on given values? Below is a static method that can be used for your unit tests as you test your models.
October 27, 2015SQL
The other day I needed to install SQL Server 2008 R2 SP1 on a machine. Because I was installing it on a Windows Server 2003, I couldn’t simply install SQL 2008, I needed to install R2 SP1 because SQL Server 2008 doesn’t like being installed on Windows Server 2003. Unfortunately, SQL Server 2008 R2 SP1 doesn’t have a base installer – there’s only an upgrade installer. So, I was required to perform a procedure call “slipstreaming”. A slipstream installation is one in which the upgrade pack is added to the base installer and installed initially instead of installing the base and upgrading. In this way, SQL Server 2008 R2 SP1, because it’s compatible with Windows Server 2003, would not complain at install time.
October 27, 2015SharePoint,PowerShell
I’m currently working with a client for whom I’m upgrading their mixed 2007 and 2010 farm to SharePoint 2013. Unfortunately, a site collection on a SharePoint 2007 farm they no longer have access to was exported instead of backed up. What makes matters worse, whoever performed the export, expanded the .cmp file. My client wanted the files from export.
While there are a few sites that give instructions on how to perform imports (like, here, here and here), as anyone who has worked with SharePoint 2007, it can be very finicky – everything, including the stars, must line up. I also tried “re-compressing” the export file since the .cmp file is nothing more than a .cab file. However, I had additional issues with the resulting .cab file since we were dealing with a 7GB file on a Windows 2003 machine (they don’t play nicely together). I also tried using a tool from Mike Smith to convert the files from the export file. But, being that Mike hadn’t worked on the solution since many years ago, of course, the application was giving me cryptic exception errors.
After all failed attempts, I was finally required to write a PowerShell script that reads the Manifest.xml and converts all of the .dat files to their original filenames in the original SharePoint 2007 file structure. I’ve posted the PowerShell script on GitHub.
October 6, 2015Windows Server,Windows Deployment Services
The other day I was setting up a new Windows Deployment Services image for a TFS/SharePoint Hyper-V environment. The host machine was running Windows Server 2012 R2. Per the normal process, I imported the Install.wim and Boot.wim images from the Windows Server 2012 media to my Install Images and Boot Images folders, respectively, in WDS. This process operated as expected and were imported successfully.
I, then, needed to create a capture image in order to capture my Windows Server 2012 images for redeployment. Therefore, I right-clicked on the Boot.wim image in Windows Deployment Services and clicked on “Create Capture Image…” to create my capture image. The capture image was created successfully, or so I thought…Read more
Subscribe to receive new posts in your inbox.