Pages

Friday, November 12, 2010

Is toilet testing a form of load testing or is this just a load of crap?

When a new stadium opens everyone flushes the toilets at the same time. They hope the pipes don't break.

This sounds similar to multiple users hitting the same button at the same time in software testing.

Can we start calling this test "the flusher" or "toilet testing" or am I just full of crap?

Thursday, November 11, 2010

Saturday, October 30, 2010

I just want to use your website not break it

I was reading an advertisement for free phones. We are using prepaid cell phones. I was checking the price of changing from pre paid to a monthly plan. With free phones it would cost over $400 per month for 5 phones that have unlimited minutes, unlimited data, and unlimited text messaging. Doesn't include the expensive phones I see other people using. That seems ridiculously expensive, so I can't afford to buy cell phones for everyone yet.

I had one phone in my shopping cart then added four more. When I clicked Add to Cart I got this error "An error has occurred please refresh your browser". I tried again and did not get the same error. It is very annoying when I see errors using a website. Cryptic error messages seem to follow me everywhere I go.

Friday, October 22, 2010

testing effective dates

This description is similar to the application we are testing:
  1. the employee has an effective date and an expiration date
  2. the employee is assigned to a department
  3. each department has an effective date and an expiration date
  4. the employee is assigned a badge with an effective date and an expiration date
  5. the department is the top level item, then employee, and finally badge
Effective dates of the child items should be within the start and end dates of the parent item. The application is not enforcing this rule, so these dates are allowed:

Department  1/1/2009-1/1/3000
Employee     1/1/2001-1/31/2001
Badge          1/1/2005-12/31/2006

In the real application each field also has a bit field called Blocked to temporarily shut off the ability to use each item. These bit fields are Nullable, which is wrong.  Blocked shouldn't affect the effective dates.

If you deactivate the top level item it should inactivate all child items. When an item is deactivated it sets the expiration date to today.

There is also a rule that says effective date cannot be after the expiration date  - sounds like bad news for these dates:

Department  1/1/2009-11/1/2010
Employee     1/1/2011-1/1/3000
Badge          1/1/2011-1/1/3000

After deactivating the Department Employee and Badge will generate the error message "End date cannot be before start date" and the effective dates are out of order for employee and badge:

Department  1/1/2009-10/22/2010
Employee     1/1/2011-10/22/2010
Badge          1/1/2011-10/22/2010