Archive for the ‘Blogging’ Category

Converted from DasBlog to WordPress


WordPress Logo Well, I’ve gone and done it. I’ve moved from DasBlog to WordPress, which means moving from the server in my office closet to being hosted at Conversion was pretty straight forward:

  1. Converted DasBlog content to BlogML using the DasBlog to BlogML Converter
  2. Did miscelaneous link cleanup in the BlogML file (removed port 8080 internal references, etc)
  3. Imported the BlogML file into WordPress using BlogML Importer WordPress plug-in
  4. Ran Web Link Validator to find broken URLs, and then fixed them
  5. Reviewed Google’s impression of my site through Google Webmaster Tools, and fixed it’s complaints

The whole port 8080 thing I had going on… those links aren’t going to resolve anymore since I’m doing shared hosting and have no control over the ports (in order to forward). Lesson learned, it is what it is.

Now it’s time to create a new QA Insight WordPress theme! HTML5 & CSS3 here I come.

Top 5 Reasons QA Insight Has Gone Dark


Hey there! I’m still part of your feed? It’s been a while my friend.

As I prepare to speak at StarWest this year, I’m reminded by my bio that “Brent enjoys blogging and cartooning about his QA, testing, and development experiences on“. Though I haven’t blogged in quite some time, I truly still do love writing here, but things change & priorities change. I have 5 good reason why this blog has “gone dry”. Alright some are reasons, some are excuses. Here goes:

  1. Go Daddy: It’s where I work, and it consumes me (in a good way). It’s a great place to work, with never ending challenges, and the sky is the limit. You can be involved and successful as you want/dare to be. I’ve chosen to write  2 of my own tickets. One says “software automation” and the other says “agile process via Kanban“. Those 2 tickets consume quite a bit of time for me. On top of that, my required day job involves working on the “Nebula” team which builds and supports the internal Go Daddy Cloud Storage (JBOD), which is used by many public facing Go Daddy products. I can write hundreds of posts on this stuff. Lets see what happens after the blog revamp.
  2. Blog Revamp: If you haven’t noticed, this blog has been hosted out of the closet of my home. The port 8080 forwarding thing messes all sorts of stuff up (stats, search, etc.). I need to port this content from dasblog to WordPress and get it out of my closet (hmmm. wonder where I should host? Yes, I’ll be dog fooding-it at Go Daddy). This mountain of work has been a huge blog writing demotivater for me. As I type now, the CPU fan in the little pizza box that this site is hosted on is squealing. It’s doomed, the site could go down today, next month, or next year. All I know is that I’ve got to get this project moving. Hosting and conversion first, theming later. Taking the time to do so, means sacrificing the family.
  3. Family: The wife and kids, boy do I love them. Writing about QA and testing usually happens at night when they are in bed, so I don’t sacrifice my time with them. Seems simple enough, until I realized that my lack of physical fitness has a huge impact on my life (insomnia, back and neck pain, mild depression).
  4. Physical Fitness: Write about QA at night, then get up at 4:50 AM to workout. Boy-oh-boy, that equals tired. Family, work, health, then blogging, can you guess which one suffers?
  5. Religion/Faith: I’ve had a spiritual reawakening in the last few years. I sincerely have a REAL commitment to God now. It honestly has changed my life, my perspective, my parenting skills, and my marriage. Though this is last on the list, its actually the most important time consumer on the list. On top of the bullets above, attending, serving (teaching 1st grade), bible studies, and a Guatemala mission trip are also taking up my time (through Mission Community Church).

So, that with said, rest in comfort knowing that I’m still alive, doing better than ever, and still fighting the good fight (Testing & Quality). Please look forward to a summary post talking about what I’ve been doing at Go Daddy in the last 2 years. Hopefully there will be more to follow once this blog is converted to a hosted WordPress account. Until then.

Go Daddy’s QA Blog:


Things have been a bit quite here at QAInsight for the last few months wouldn’t you agree? As always the days and nights are never quite long enough to get all those things I want done.

I have one excuse though.

Actually I have more than one but I’m only going to share one with you:

I’ve been working undercover with the FBI and Viacom to help parse Google/YouTube logs to obtain logons which relate to IPs, which point to people who are uploading copyrighted content. A mass effort to prepare for the largest bust in digital history.

No… Just kidding.

Really, I’m kidding don’t start with that death threat stuff. I’ve already had three this week.

Apparently the insightful QA advice found on said Software QA blog has increased defect finding and input by QA Engineers across the globe  and developers are angry. Go figure, they want to eliminate me because apparently I’m the ring-leader that has slowed down their development process and release to production.

It’s just a blog. I set forth ideas, I didn’t do the defect finding. Please spare my life. Please? I have kids.

In fear of my life I’m going to lie low a while.

In the meantime, take some more QA advice from me and go check out Go Daddy’s new QA blog They have a QA army of 50 talented individuals. I expect to see some good stuff come from these peeps.

Oh… By the way, if you’re a developer and you see posts on where the author is “Brent Strange”…

IT’S NOT ME. It’s another Brent Strange. Ironically this one does QA too. Go figure.

15 popular posts you may have missed in 2007



Another year has come and gone for To highlight the year, here are 15 popular posts you may have missed in 2007:

Testing Thoughts
Selling quality to the project team
Agile for 30 minutes: Agile defect reporting
Is QA Better at Writing Product Specifications?
Emotional Attachment to Robots, Focus on the Tests Not the Robot
Death By 1000 Cuts, Bad Software Due to Many Low Severity Defects
Keep it Small With a software testing club
Proper use of the sleep method in automation

Testing How To
How to test for database schema differences
How to detect Web service changes between builds
Find installer defects quickly by reviewing key MSI database tables

Testing Tools
Report on dirs, files, and file properties with File Property Reporter
MSI installer testing tool: MSI Database Reader & Reporter
Brent’s Web testing toolbox


How much is an ass-load?
The wonders of caffeinated soap

Comments are working again


Comments are working again. I narrowed it down to the search form I had on this page. For some reason the plain and simple <form></form> tag, using Internet Explorer, and .NET 2.0 causes the following error:

System.ArgumentException: Invalid postback or callback argument. Event validation is enabled using in configuration or <%@ Page EnableEventValidation=”true” %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
at System.Web.UI.ClientScriptManager.ValidateEvent (String uniqueId, String argument)
at System.Web.UI.Control.ValidateEvent (String uniqueID, String eventArgument)
at System.Web.UI.WebControls.TextBox.LoadPostData (String postDataKey, NameValueCollection postCollection)
at System.Web.UI.WebControls.TextBox.System. Web.UI.IPostBackDataHandler.LoadPostData(String postDataKey, NameValueCollection postCollection)
at System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
while processing

So, for now, no searching from the site. But at least you can comment! You can always search the site using Google though:

I’ve been avoiding blogging for a while now due to being so frustrated with the comment issue (I probably spent 4 hours, here and there, debugging this thing).  I have a few posts in the queue that will be coming your way soon.

Comments are broken


Comments are broken on when using Internet Explorer, so technically it’s not a BLOG anymore (according to the blogging “experts”). As I work to make comments work, use FireFox to leave comments or as always, feel free to email me. Email information is on the right.

How Open Source Failed Me


For about 2 1/2 years now my wife and I have been keeping a blog for our son Jace. Over at  (notice how all the post images are broken when you go there)  we document the life of Jace and post pictures for 2 reasons:

1. So we can easily share with family
2. Now, 20 years from now, and hopefully forever Jace will have an online “baby book”

In my mind, number 2 being the most important. Why number 2 is such a big deal to me is because my Mom put together and kept 5 baby books for me, from birth to about 13 years old, and those baby books mean a lot when you get older and want to reflect on your past. I want to do the same for my son.

In pursuit of the same but a little more cutting edge than the modern day scrap-booking, I figured the online blog format was the best way to go but needed an image sharing solution. I chose DasBlog for the blog and nGallery for the image sharing solution. Both open source.

DasBlog rocks, it’s a great piece of software with truly dedicated and talented people. nGallery on the other hand… Well it was a great piece of software, it did exactly what I needed but then it was taken over by Community Server and now it is NOT part of the open source/free world.

So here is my issue. This last week I upgraded to DasBlog 2.0  which uses .Net 2.0 but my open source nGallery uses .Net 1.1. I am unable to get both the .Net 2.0 and .Net 1.1 applications  to play nicely in the same sandbox. Even with their own vdirs and application pools. So, now I have a blog/baby book with broken references to a .Net 1.1 nGallery picture gallery. Trying to keep up with the latest in technology hosed me. Suck. So much for a baby book to last decades.

The reality of it is that when I started the blog I didn’t put much thought into how to make an online application/baby book last forever. I am now…I need a solution. Something that will be there when my son is old enough to care. Even if I found a way to fix the problem at hand I am still worried about the future.  What if DasBlog sells out and 10 years from now I’m forced into .Net 8.0 with no backwards compatibility? Screwed again.

What do I do?

Pay for a service? How do I know if they’ll be there in 20 years?

Build and manage my own applications? I don’t have the time.

Am I stupid to put our precious memories on the Internet?

Google Adsense Sandbox 1.0


Amit Agarwal, analyst, geek and professional blogger has created for us an Adsense Sandbox. This Google Adsense Preview Tool allows you to type in keywords and see 25 contextual and geo-targeted Google Adsense ads.

I can see this to be helpful if you’re trying to target a specific ad, or trying to get a specific ad off your page. I’m not too Adsense savvy, so I suppose there are other good uses too.

Phillip Forteza has entered the Blogosphere


I’ve always admired fellow coworker and QA engineer Phillip Forteza for his enthusiastic and positive attitude. Sitting in my cube 10 feet away, I could hear Phillip interact with coworkers and customers; his interaction always upbeat, caring, and real. I really admire that. I wish we could always ooze positive emotion like Phillip, especially myself.

Perusing my blog logs I encountered that Phillip had started a blog. Excited to see another fellow coworker’s musings, I found my way to his site and read all of his posts. I LOVE IT. It’s Phillip to the T (Phillip to the P?). So far Phillip’s musings are life lessons and each post a positive, uplifting addition to your day. Go check him out at A Day in the Life of PF3.

Post navigation