testing.stackexchange.com – Testing for a startup?

The following is my response to a question on the now defunct testing.stackexchange.com. The question was "Testing for start-up?" and my answer:

I have worked with startups for most of my career. Considering the clarification that you added to the question, it is a difficult question to answer in the abstract. A lot will depend on the team that exists today and a realistic understanding of the upcoming hiring plans.

First, consider that in a startup most people will need to wear multiple hats at different points in the early stages of the company. While the person’s primary responsibility is testing, consider what else they can do. I would lean towards a professional tester who can help with things like working with beta testers, working with interns, perform system administration tasks on the test systems, etc. It will depend on what skill set already exist within the team.

Second, consider costs – not just the salary of the person you are hiring but what items the person may expect to be in place. I made a hiring mistake at one of my first startups where the person I hired as our primary tester was so wedded to the tool set from his last company (a tool set that the company could not afford), that this person spent as much time trying to justify buying the tool as working on the product. This is probably less of an issue today with so many open source tools but keep it in mind.

Third – laying a foundation. The hire must realize that not only are they coming in to test but they are laying the foundation for how the company will approach testing for a long time. This person will help define the relationship between testing and the other groups. For this reason alone, I would lean away from part time testers or beta test volunteers. They will not be able to lay that foundation.

I would hire a professional tester. This does not exclude the development team from taking an active role in testing. The hire should encourage it.


Scripting Links from November 2011 Software Engineering Notes

The following links were published in the November 2011 ACM SIGSOFT Software Engineering Notes in the "Surfing the Net for Software Engineering Notes" by Mark Doernhoefer. This issues topic was interfaces.


September 2012 mensming Twitter posts

Follow mensming on Twitter

25 Sep
Voice commands crash bank phone system – www.scmagazine.com.au/News/315844,phonetic-attack-commands-crash-bank-phone-lines.aspx

24 Sep
Posted to testingpodcast.com – RBCS: Adv. SW Testing Reviews – testingpodcast.com/agile-testing-challenges-four-years-later-92012/

21 Sep
Posted to testingpodcast.com – TWiST #114: Knight Capital, Part II – testingpodcast.com/twist-114-knight-capital-part-ii/

20 Sep
MS Attack Surface Analyzer – www.securityweek.com/microsoft-releases-attack-surface-analyzer-encourage-secure-software-development

19 Sep
Posted to testingpodcast.comsoftwaretestpodcast.com Episode 38 – testingpodcast.com/episode-38/

18 Sep
Posted to testingpodcast.com – TWiST #113: Knight Capital, Part I – testingpodcast.com/twist-113-knight-capital-part-i/

17 Sep
How Intuit Manages 10 Million Lines of Code – www.drdobbs.com/tools/building-quickbooks-how-intuit-manages-1/240003694

14 Sep
10 reasons why you fix bugs as soon as you find them – dl.dropbox.com/u/3521363/ttp/siete/TTP-7-Infographic.pdf

13 Sep
1 and 2 are used at Conenza – Most Popular Programming Languages – redmonk.com/sogrady/2012/09/12/language-rankings-9-12/

12 Sep
Use the Magic SysRq Key on Linux to Fix Frozen X Servers, Cleanly Reboot, and Run Other Low-Level Commands – bit.ly/Q2i5GK

11 Sep
Great read – Gutenberg the Geek (Kindle Single) by Jeff Jarvis – amzn.to/PkjZ8r

10 Sep
Posted to testingpodcast.com – TWiST #112: Hands on Testing, Part II – testingpodcast.com/twist-112-hands-on-testing-part-ii/

5 Sep
Posted to testingpodcast.comsoftwaretestpodcast.com Episode 37 Part 1 – testingpodcast.com/episode-37-part-1/

4 Sep
Posted to testingpodcast.com – TWiST #111: Hands On Testing, Part I – testingpodcast.com/twist-111-hands-on-testing-part-i/