Skip to main content

Posts

Showing posts from March, 2013

2 Pros and Cons of RTC

The Pros and Cons of RTC First and foremost I'm gonna elaborate on exactly what this sexy thing is. RTC stands for Rational Team Concert. On the website that link on the left refers to; it calls it an "Agile Application Lifecycle Management Solution". Which I guess kinda makes sense, in the sense that "Agile" seems to be very "in" in the world of Software Testing these days. (I did a bit of a Google search and Google agrees) But then what do I call it, you might ask? I call it a place where documentation gets stored (Source Control) and work items (like Defects, Issues, Change Requests and Risks) are put up. Mind you, I've only been using RTC as a Test Analyst since end of August so I'm sure I haven't fully understood/embraced its intricacies yet. So gotta keep in mind that these Pros and Cons is from that sort of mindset. Pros   My favourite pro would probably the nifty dashboards you can create. Someone from the PMO in my pro

4 Cool Things I learnt from Dr. Alistair Cockburn

4 Cool Things I learnt from Dr. Alistair Cockburn Use Cases to User Stories Last week I went on a 2-day course held by Alistair Cockburn.  I found it pretty intense (being the only TA (Test Analyst), and having to familiarise with all the TLAs (Three Letter Acronyms) and XTLAs (Extended Three Letter Acronyms) but I got there in the end). But before I dive into the cool things I learnt; here's a quick intro to who Dr. Alistair Cockburn is: He's one of the parents of Agile Development. According to Cockburn, if you were to describe Agile in a elevator-spiel it is "early delivery of business value" and "less bureaucracy". Oh and on a random note he's fluent in at least 4 languages (I might've forgotten one), English, German, French and Swedish- so that's pretty darn cool in my books. 1. Developers prefer user stories. Testers and business analysts prefer use cases I found this little tidbit of information rather interesting. Apparent

The joys of 2 screens

Why I love having 2 screens at work Oh 2 screens, how do I love thee? Let me count the ways. You may think that this quote by Elizabeth Barrett Browning is a wee bit over the top to describe my love of 2 screens. But let me tell you this. It's great to work in my role with that extra screen to make testing that much more convenient (and let's be honest: easier.) But to start off with, let me recount my experience on life WITHOUT an extra screen as a test analyst. I REALLY hated it. I saw other test analysts with 2 screens. I looked at them with envy. I'd ask my test lead, why don't I have an extra screen? :( He then told me this was his first project with an extra screen. Flippin heck. I couldn't believe that man. It's so much quicker to test with an extra screen- why would you disturb efficiency by limiting someone to one measly screen?! About 3 months into my project, I came into work and a computer with TWO screens was waiting for me. Shit yeah gi

What is a test analyst?

What is a test analyst? How I try to answer this question when people ask me what a test analyst is. So... what exactly is a test analyst? I get asked this question all the time when I catch up with old uni and high-school friends and to be honest, I do find it a hard question to answer simply. If you were to google this you'd probably find something along the lines of... " The Test Analyst is responsible for designing, developing, and executing test plans and test cases that verify a software conformance to defined acceptance citeria." but then, what exactly does that MEAN? I then try to explain to my friends, I work in IT and am a consultant on IT projects. So then they ask- are you a developer? Do you write code? Nope, sorry. But I do check the code of developers by running tests and making sure the system behaves as it should. So then how do I answer this (still somewhat dreaded question because it can be a bit hard to describe) might you ask? I s