Thursday, 29 October 2009

In case you haven't already noticed the post on the Software Testing Club website, the Club has decided to start branching out and the first step we have decided to take is to publish a magazine

Here is the official blurb

If you are interested in writing about software testing then why not contribute an article to the Software Testing Club's (STC) new magazine due to be published in January 2010.

The STC are inviting anyone in the software testing community to submit articles for review on any testing subject you want to write about. The STC are accepting articles from anyone working in the testing industry with a testing story to tell. Experienced writers are welcome just as junior testers are. So if you have something to say, post it to the following address: rob@softwaretestingclub.com.

Thursday, 22 October 2009

Maybe he is - carrying on with my research into social media and Web 2.0 I got the error message shown above on Facebook.A quick Google on the error message led me to the Facebook Developers Forum and a thread all about a similar bug. First reported on 2008-09-05 Later in the thread is a plaintive request "Any chance of getting this bug fixed?" , later on "Any progress on this?" and "Any chance that this well ever be fixed? I see this about a third of the time when I post a new comment."

Later on that evening I found a bizarre bug where searching for "fish" returned an error page, searching for "fosh", "fishy", "fash" and "fush" all returned search pages. Worked fine on the wife's computer and on other peoples computers ( I posted a request on Facebook for other people to try a search for "fish" )

So, to summariseBugs that are not fixed for months and monthsRandom BSOF - Blank Search Of Fish

Saturday, 3 October 2009

I just checked out the latest on LinkedIn and saw a question on one of the many testing groups from someone wanting advice on how to write a test plan on security testing.

Nothing really new about this, as one of the moderators of The Software Testing Club and regular reader of SQA forums I'm used to people asking the most basic testing questions ( the 'remove post' function can get some heavy use ).

Wonder what will happen to the person asking the question ? He'll probably get told to use Google, he'll find some basic security plans there, incorporate them into his test plan, send them off to the CEO, CIO, CFO, Old Macdonald and the mild mannered janitor, gets it signed off and yet another app with security flaws hits the market.

A test plan for security testing should be very simple.Find out how important security is to the stakeholders.If it's important, get a security expert in.

Is that a cop-out ? Should all testers be able to do security testing ? Do you do security testing on top of the other testing activities you do - if so, how confident are you that have done it well enough ?

Day 2: Send draft test strategy out for review to CEO, CIO, CFO, D0BEDO, Support Team Manager, Training Team Manager, Documentation Lead, Old McDonald and The Janitor ( a mild-mannered one )

Day 3-5: Spend time explaining difference between test scope and test types to various people. Change font of document after feedback from CEO. Receive Out of Office reply from CFO. Add diagrams to document at request of Old McDonald

Day 6: Send out Final Test Strategy for official sign-off.Receive Out of Office reply from CFO

Day 7: Find company template for Test Plan and write plan

Day 8: Send draft test plan out for review to CEO, CIO, CFO, D0BEDO, Support Team Manager, Training Team Manager, Documentation Lead, Old McDonald and The Janitor ( a mild-mannered one )Receive Out of Office reply from CFO

Day 9-12: Spend time explaining difference between unit, system, integration and UAT testing to various people. Change font of document after feedback from CEO. Receive Out of Office reply from CFO. Add diagrams to document at request of Old McDonald

Day 13: Send out Final Test Plan for official sign-off.Receive Out of Office reply from CFO

Day 14: Fill out form HBR-786-ABC-911-999-FOR to request access to test environment

Day 15: Fill out form RRR-987-ASDF-ASDF-GHJ to request testing resource

Day 16: Form HBR-786-ABC-911-999-FOR returned as I hadn't filled in section 16.5.4

Day 17: Form RRR-987-ASDF-ASDF-GHJ as I hadn't filled in section 14.5.9

Oh dear, just re-read Matt's blog

"Keep in mind, this is an agile shop that delivers working software every two weeks"