Category Archives: QA Related
Posts related to Software Quality Assurance
This tweet came across my feed recently and I emphatically agreed:
It occurs to me, however, that we as testers sometimes don’t see ourselves falling into the category of needing such advice. There’s the oft repeated “coding the right thing rather than coding the thing right”:
We throw together a script that walks through the application, that performs a particular use case, and we run it and we have this sense of security that if it passes, we are ensuring good code is going out the door.
But are we, as testers, doing due diligence with our code, the same way we expect the developers to? Are we doing design reviews to ensure we’re actually coding the right thing? Are we getting code reviews? Are we reviewing and refactoring our own code as the application code changes? Are we pair programming? From what I’ve seen, some of us are. Many are not.
We cannot advocate that “test code is as important as application code” if we don’t treat it as such. We can teach almost anyone how to write a script to automate use cases of an application. We should be teaching them how to think more – what will this code actually do? What does it accomplish? If it passes, what does it prove? Am I actually asserting anything, or am I just having it click buttons and fill in fields with no actual check in place? It is one thing to write a script to assist you in manual testing – perhaps to get you to a certain point so that you can get to the real testing quicker. It is another to write such a script and treat it as the test itself.
If you write test automation, I challenge you to reconsider what your code actually accomplishes, what a passing check means. Reconsider the design and architecture choices made. What did you mean to do? What did you miss?
I challenge you to treat your code as if it is application code. I challenge you to treat your code as you want the developers you work with to treat theirs. And remember that test automation is not testing (at least not until the machines take over) – you need a brain to test.
A few months ago, I received an email from someone that attended my very first conference talk, at QA or the Highway in February. They were from $Company, and lead a QA team there. They thought that my talk would be great for their team to hear, and asked that I come to speak to the team. Instant freakout! That was my first time speaking at a conference! Holy shit!
I replied that I was interested for sure, and we set a day and time. I got my talk ready, by making a few changes from the conference, updating a few points and adding some things.
I also started setting up a drinkup for the time I would be there, to catch up with testers in the Columbus area. That turned out to be an excellent decision. And Mr. Keith Klain introduced me to the Per Scholas folks in Columbus, and asked that I stop by and speak to them as well – a casual conversation about being a tester and just being a IT professional. And that he’d pay for the drinks! Bonus!
So now I was on a mini speaking tour. Time for the Imposter Syndrome to kick in…
I drove down on Father’s Day, checked in to the hotel, and went to the bar. The original one we chose was closed, so we moved on to another – we’re testers, we adapt well to adverse situations!
Now for the conversation at the bar. I met up with Damian Synadinos and Diana Wendruff – two awesome folks in the test arena in the Columbus area. We talked about why I was in town, and who I was speaking to. Damian offered some advice that proved incredibly valuable to me – this could be a “quick fix” by management, try to make everyone get along by bringing in this speaker. Some of the folks there in QA are *not* testers by profession, they probably don’t want to be there. That, in itself, was extremely helpful. I had not thought about it yet, but here’s what I realized:
speaking at a conference, people have chosen to be there or at least chose to be at your session, and can walk out at any time if they feel it doesn’t apply to them. Speaking at a company, people are most likely made to attend your talk. They have other stuff to do, and if they don’t want to be there or it doesn’t apply to them, they can’t leave – they can only sit there. You’re giving it your all, showing your passion to them, and some of them just don’t care. Maybe even resent you.
AND THAT’S OK!
Speaking in front of an audience like that was intensely different than at the conference. At the conference, the attendees were engaged and interested, and they laughed at my jokes! At this company, I was just like “management” to most of them – throwing a message at them that they didn’t care about or believe in.
Now I’m not saying every person that I spoke to there felt this way – there were a few attentive faces. But for the most part, it was the “ugh, I’d rather be doing my job right now” face. Without that realization – without that conversation at the bar! – I wouldn’t have been prepared. I would right now probably still be crying from the experience 😛 Lesson here – always get drinks with your buddies! Or something…
Then I went, directly after, to Per Scholas. Per Scholas is an amazing program that provides IT training and job placement to low income folks. This audience was the complete opposite of who I spoke to earlier in the day – they were excited to have someone come in to speak to them that was doing in the real world something that they could do in the very near future. I gave a quick rundown of my resume essentially, and opened it up for questions. Some great, intelligent questions and excellent conversation. They asked for my contact information and business cards (nobody at $Company did!) which I happily provided – I’m happy to answer any of their questions privately, or connect with them on LinkedIn. They are an awesome group of women and men that have a very bright future ahead of them, thanks to the Per Scholas program.
A few of the points I tried to make there:
- You absolutely do NOT have to know how to code to be a great tester
- However, knowing how code comes together will help you (the process of dev)
- When I was hiring for testers, I was looking for:
- Passion for software quality – beta testing games? providing bug reports for software you use every day?
- Excited by puzzles – if you have to figure something out, you don’t get frustrated easily
- Intelligent and willing to learn – I don’t care if you have a degree, but if you’re not willing to learn buh-bye
- Admit when you’re wrong or don’t know – srsly, don’t lie or inflate your abilities. It won’t end well
- Some technical aptitude – you have to be able to figure out how to troubleshoot. Or Google well 😛
- Network network network! Look for meetup groups. Networking is how I got into this industry!
All in all, my mini speaking tour was great. I gained a lot of experience speaking in front of a not-so-accepting crowd, and got to meet the amazing Per Scholas organizers and students, and of course drinks with some great testers (paid for by Keith Klain!).
I’ll be speaking at the Quicken Loans internal Technology Conference in July, and then again at CAST in August. Then I think I’m done for the year! And I’m getting married next year, so probably not doing much next year… Though I started 2014 with the hopes of speaking at a single conference, and am ending up speaking at 3 plus privately for a company and Per Scholas. So who knows!
Hey all – let’s get this going. If you’re interested in speaking – either full session, leading a workshop, or doing a lightning talk, let me know.
I’ll get started on the location, day and time. I’d like to do this monthly!
W00t w00t let’s do this!
ETA: Here’s the meetup group!
Last year I wrote up a post with my 2013 goals and resolutions. I wanted to review what I had actually done, so here we are!
Achieve a better work/life balance. This will be the most difficult of all of my goals…
- With my new job, I think I’ve gotten this a bit more under control. It’s easy for me to work 50+ hour weeks, but I try to keep myself to 45 hours when it’s not busy time
Attend CAST, KalamazooX, IT in the D, and maybe some other conferences too
- I attended KalamazooX on the initial list. I also went to StarWest, which wasn’t even on my radar before because it was something I couldn’t personally afford. Thanks to my new job this year, I got to go!
Submit a talk to a conference and/or user group
- Done! 3 or 4 times, even!
Actually do above talk
- I did the lightning talk version at the Great Lakes Area .NET User Group. I was also accepted to do the full version of the talk at QA or the Highway in February 2014 😀 I also did a series of 99 second talks on the same topic (dev vs. qa) for Software Testing Club (note – they’re horrible!)
Submit articles to QA publication
- I was published! In the 10th issue of The Testing Planet I wrote about Leadership (actually The 10 Habits of a Highly Ineffective Leader, which pulls from my experience over the years)
Attend at least one GiveCamp; I didn’t attend any this year and I’m jonesing for it!
- Was on the planning committee and attended the Ann Arbor GiveCamp. Huzzah!
Assist in coordination of and/or attend Detroit GiveCamp
- I was part of this, but the whole thing got sidetracked
Seek out new opportunities…
- I got a new job! At Quicken Loans! Which I LOVE!
Finally write that Android app I’ve been thinking about for a while
- Nope, didn’t happen
Write more code in general. Ruby, Java, C, and of course my favorite, Perl.
- A bit, in C# with Coded UI tests. And VBScript for QTP (blech)
Continue to be involved in the QA community
- Yeah, for the most part, this is happening 😛
Hire some people that actually know WTF they’re doing
- I left there. I hope they have good QA 😛
Actually go to the gym I have a membership for >.<
- Yeah, I went like a few times. Still paying for it, still don’t go *shrug*
Be a better leader
- Constant work in progress on this one
So 2013 has treated me pretty well in my professional career. I look forward to speaking at QA or the Highway and whatever else this year throws my way!
Posted in QA Related