The Test Developer - An Easy Punchline?

I’ve been reading about and getting involved in conversations on the difference between a traditional lifecycle tester and an agile one. As the way projects with these type of people differ quite drastically in places, there are plenty of ways to describe what an agile tester is - I’m going to stick my neck out and mention one, a developer of tests rather than production code.
It’s a sweeping generalisation because there are a lot of software quality assurance tasks that an agile tester does before they touch an automation tool - they have to work with the team to define the acceptance criteria of the user stories, define and document the test environment to be used, perform exploratory testing on whatever code is available, review developed functionality etc.
However once they’re ’settled into’ the sprint there are developers performing TDD and producing code in a Continuously Integrated Environment and testers producing test code to ensure business-level descriptions/requirements are met.
Read More about: What is Software Testing?
Of course there are all the defects to be tracked and retested, and associated documentation to be produced but I’ve found that when I provide this eight-word description to people new to agile/agile QA/basically non-traditional ideologies in general, a glimmer of comprehension and (almost :-)) acceptance appears.
So, has anyone else found a quick way to describe to someone what an agile tester does? It may sound like a trivial thing to discuss but having been first QA person into several companies now, it’s very good to have ‘buzz-phrases’ to hand that provide quick descriptions to people who still have the mental block.

Comments

Post a Comment

Popular posts from this blog

How can product quality improvement be tracked from sprint to sprint?

I’m interested in defining the best metrics to use for checking whether the product quality is improving as time, and sprints, pass by. One obvious factor is the number of automated tests passing in the continuous integration builds related to the coverage of functions in the code. Or is it? Do the tests literally show the product quality? What if the finished article isn’t what the customer wanted? There are then a suite of tests making sure that the software does something it’s not meant to. Number of defects? Measured against what? The list of possibilities goes on, what I’d like to find out are tried and tested measurables. Does anyone have a list they use in every project? Update by Kenny 08/11/09 :- Ok, I’ll try and answer my own question here (the power of reflection!). There are two scenarios in projects which require different solutions in relation to metrics gathering. They are :- 1) A project run using mature agile methodologies from day 1 2) A project which ...
Read more

Agile v Waterfall - Which Is The More Risky?

I still find it strange that companies unfamiliar with Agile automatically view it as being a methodology that pays no heed to process or ensuring quality of output. From my experience the quality is actually a lot better, the timescales set are achieved more readily and everyone involved has a much greater understanding of the product and its development status at any one time. At present I´m working on a project where I´ve had to split the test team into two due to several companies working to build a complex product together. One team is performing agile QA in a sprint team, the other is working ´the old way´. It´s very interesting to note that all the worry and uncertainty is coming from the team working with the traditional model due to the fact that timeframes having been guesstimated months ago about environments, data and functionality that no-one knew about then. As time marches on we appear to be spending more time in meetings discussing what we once thought was go...
Read more

Details, Fiction and Software testing services

  No matter what DevOps processes, models and applications corporations use, testing is a vital Component of the general DevOps procedure — don't just to be sure code alterations work as envisioned and integrate well — but to make sure the necessity improvements do break the performance.” – How DevOps Transformed Software Testing Whether or not your web site is still in improvement or out inside the wild, we are able to get the job done with any surroundings. Our testers can collaborate along with your developers and task administrators, and in some cases be part of your Jira, Slack, and standup calls. Find out more about our Site testing services. For that reason, the workforce has to analyse the code on the continual foundation to keep the code foundation in a great maintainable state. This will protect against uncovered complex debts, process crashes and highly-priced fixes.” – Sergey Terekhov, Defining and monitoring the code top quality Most of these tests are more expens...
Read more