18
T18 Special Topics 10/6/16 13:30 A Day in the Life of a Test Architect Presented by: Lee Hawkins Dell Software Brought to you by: 350 Corporate Way, Suite 400, Orange Park, FL 32073 8882688770 9042780524 [email protected] http://www.starwest.techwell.com/

A Day in the Life of a Test Architect

Embed Size (px)

Citation preview

Page 1: A Day in the Life of a Test Architect

       T18  Special  Topics  10/6/16  13:30            

A  Day  in  the  Life  of  a  Test  Architect  Presented  by:    

 

  Lee  Hawkins      

Dell  Software    

Brought  to  you  by:        

   

   

350  Corporate  Way,  Suite  400,  Orange  Park,  FL  32073    888-­‐-­‐-­‐268-­‐-­‐-­‐8770  ·∙·∙  904-­‐-­‐-­‐278-­‐-­‐-­‐0524  -­‐  [email protected]  -­‐  http://www.starwest.techwell.com/      

 

       

Page 2: A Day in the Life of a Test Architect

Lee  Hawkins      The  principal  test  architect  for  Dell  Software,  based  in  Melbourne,  Australia,  Lee  Hawkins  is  responsible  for  testing  direction  and  strategy  across  the  group.  In  the  IT  industry  since  1996  in  both  development  and  testing  roles,  Lee's  testing  career  really  started  in  2007  after  attending  Rapid  Software  Testing  with  Michael  Bolton.  Lee  is  the  cofounder  of  the  TEAM  meetup  group  in  Melbourne,  a  co-­‐organizer  of  the  Australian  Testing  Days  conference,  and  a  frequent  speaker  at  international  testing  conferences.  He  blogs  on  testing  at  Rockin'  And  Testing  All  Over  The  World.  When  not  testing,  Lee  is  an  avid  follower  of  the  UK  rock  band,  Status  Quo;  hence  his  Twitter  handle  @therockertester.    

Page 3: A Day in the Life of a Test Architect

A Day in the Life of a Test Architect

Dr Lee Hawkins Principal Test Architect

Dell Software, Melbourne

Page 4: A Day in the Life of a Test Architect

2 Dell - Internal Use - Confidential

My journey “It is the story that matters not just the ending.” (Paul Lockhart)

Paul Lockhart “A Mathematician's Lament: How School Cheats Us Out of Our Most Fascinating and Imaginative Art Form”

Page 5: A Day in the Life of a Test Architect

3 Dell - Internal Use - Confidential

PhD Developer

IBM UK

Migrate to Australia

Senior Tester Quest Software

Test Lead Quest Software

Rapid Software Testing

Test Architect Quest Software/

Dell Software

Principal Test Architect Dell Software

How I became a test architect

1992-1996 1996-1999 1999

1999-2004 2004-2008 2007

2008-2013 2013-

Page 6: A Day in the Life of a Test Architect

4 Dell - Internal Use - Confidential

How I became a test architect – so what?

• You often don’t end up where you think you will. (And that is probably a good thing.)

• There are always opportunities if you look for them or make them happen.

• Look out for pivotal moments – attending “Rapid Software Testing” was mine.

• Becoming a professional in software testing involves continuous learning. Don’t make the mistake of believing you’re an “expert”.

• Do your current job really well and also demonstrate you can do more (this is how “Test Architect” became a thing at Quest).

Page 7: A Day in the Life of a Test Architect

5 Dell - Internal Use - Confidential

A day in the life

Page 8: A Day in the Life of a Test Architect

6 Dell - Internal Use - Confidential

8am-9am: preparing my day

• I have a long commute including one hour on a long-distance train service.

• This time helps to prepare my day.

• Catch up on overnight Twitter action (thanks to time zones).

• Gives me ideas for blog posts.

• Note CFPs for any interesting conferences.

• I was reluctant to engage on social media, but was persuaded to join Twitter during a peer conference, now my main source of news about software testing.

Image: Marcus Wong http://railgallery.wongm.com/

Page 9: A Day in the Life of a Test Architect

7 Dell - Internal Use - Confidential

9am-10am: talking testing

• In senior level management meetings, I am there to represent testing:

–Technical leadership

–Strategic direction

–Advocating for changes in approach

–Resourcing

–Process improvement

Image: http://www.finca-spanien.net/virtualoffice.htm

Page 10: A Day in the Life of a Test Architect

8 Dell - Internal Use - Confidential

10am-12pm: evangelizing

• Big part of my job as Test Architect

• Creating reference materials

• Writing wiki articles

• Writing up case studies

• Internal testing promotion:

–Explaining the need for testers (yes, even in agile teams)

–Describing what good testing looks like (to me)

–Blogging internally to give testers within the organization a “go to” place for information about current testing trends, who they should be following, etc.

Image: http://www.wheelofwellbeing.org/activities/well-being-spread-word

Page 11: A Day in the Life of a Test Architect

9 Dell - Internal Use - Confidential

12pm-1pm: engaging with community

• Knowledge sharing:

–Software testing training for Epic Assist (autism spectrum)

–Connect with other testers

–Present at another company

–Talk with a new speaker

• TEAM organizers catch up:

–Next meetup

–Conference planning Image: http://www.cremamagazine.com.au/st-ali-melbourne

Page 12: A Day in the Life of a Test Architect

10 Dell - Internal Use - Confidential

1pm-3pm: presenting to offshore team

• Melbourne is expensive - all testers in my group in lower cost locations (viz. China & Czech Republic).

• Most are quite junior and require a lot of mentoring and training – especially in China.

• Visit these sites frequently.

• Both broad and deep sessions, as required:

–Three pillars: exploratory testing for new features, risk-based regression testing, and automation (in CI)

–Session-based exploratory testing

–Risk-based testing (tooling support via Enterprise Tester)

–Using oracles and heuristics

–Using mind maps for test planning and reporting

Image: http://www.servitic.cl/

Page 13: A Day in the Life of a Test Architect

11 Dell - Internal Use - Confidential

3pm-4pm: conference proposals & prep

• The good news: more & more testing conferences across the globe. The bad news: you can’t go to them all!

• Twitter as my main source of “calls for proposals/papers” (CFPs)

• Typically respond to 6-8 per year.

• Keep a backlog of ideas from:

–Interactions with other testers,

–What I see on social media, and

–Reading blogs, articles, etc.

• Keep “current” presentations down to one or two during the year. Typically working on a presentation for at least one conference I’ve been accepted into.

Image: http://pptmag.com/blog/presentation-skills-preparing-and-organizing-the-content/

Page 14: A Day in the Life of a Test Architect

12 Dell - Internal Use - Confidential

4pm-5pm: personal branding

• Take advantage of social networks but don’t be ruled by them. Be consistent across platforms.

• I focus on Twitter & LinkedIn.

• Personal (Wordpress) blog:

–Cadence: one or two posts per month

–Report on testing events

–Posts motivated by current trends and inspiration from tweets and other blogs I follow.

• Become known for your unique values and passions.

• Act in alignment with your personal brand to build credibility.

Image: http://smurfitschoolblog.com/tag/personal-branding/

Page 15: A Day in the Life of a Test Architect

13 Dell - Internal Use - Confidential

5pm-8pm: attending testing meetup

• TEAM meetup group formed mid-2015.

• Promotes context-driven testing principles.

• Mission “Connecting Testers”

• Meetup runs once a month.

• 30-50 people.

• Relies on sponsors for venues and refreshments.

• Presentations (a great place for new presenters to practice), debates, short workshops, dice game, networking.

• Very rewarding to see a community of like-minded software testers being formed & growing stronger.

Page 16: A Day in the Life of a Test Architect

14 Dell - Internal Use - Confidential

Summary

Page 17: A Day in the Life of a Test Architect

15 Dell - Internal Use - Confidential

Takeaways

• It’s possible to have a long & rewarding career in software testing (even if you don’t start out with this intention).

• There are many ways to engage with the testing community and you will be welcomed for your active participation.

• There are many different schools of thought around what makes good testing, so find the ones that make sense to you and then learn all you can to become an excellent tester.

• Don’t be afraid – to ask for help, to step out of your comfort zone, to make your opinions public.

Testing is not a dead end career!

Page 18: A Day in the Life of a Test Architect

16 Dell - Internal Use - Confidential

Contact me Q&A

[email protected]

@therockertester

therockertester.wordpress.com

www.meetup.com/Test-Engineering-Alliance-Melbourne

www.TestEngineeringAlliance.com

Australian Testing Days 2016