-
Jared Quinert
- Male
- Melbourne
- Australia
- Share
- Share on Twitter
- Share on Facebook
- Blog Posts (1)
- Discussions (15)
- Events
- Groups (4)
- Videos
Jared Quinert's Groups
-
Aussie Testers
14 members
-
Bloggers
106 members
-
Software Testing Mentors
96 members
-
ANZACS
51 members
Jared Quinert's Discussions
Testing Tools
Replied May 28
My blog
Loading feed
Jared Quinert's Page
Gifts Received
Jared Quinert has not received any gifts yet
Latest Activity
The most important tool is your brain. Automation can only support your thoughts and ideas, not replace them.
Automation is largely a programming task. Chris Pine's 'Learn to program' book - http://pine.fm/LearnToProgram/ is a good introduction, an…
I feel like this is more appropriate :D
A place for Aussie tester's to network.
You can complain about bugs, bosses, trams and the Weather.
As has been alluded to, it's fairly common, but the more sensible places are either -
- setting up spreadsheets with the input data and leaving out the 'how to' steps.
- automating the input.
I've worked with both approaches. It's a lot nicer when…
The thread's old, but thought I'd have my say.
One of agile's premises is that our expected value estimates are almost always imperfect. Based on this, it advocates an iterative, incremental approach in order to quickly validate the assumptions mad…
Session-based testing is an approach to managing exploratory testing. There are other ways, but in my opinion, SBTM's drivers are -
- You require more formality, or a higher level of evidence around your debriefing process.
- You need a higher level…
Even if they discussed it (ie. shared the design), there's still execution, observation, reporting, advocacy and politics. Two testers finding the same bug won't necessarily achieve the same outcome.
To respond to the original post, testers are alw…
Profile Information
- About Me:
- Testing generalist, occasional pro/anti-Agile ranter. I've worked on agile projects for seven years now, and it's a mixed bag. Ther's a lot that's good but it misses the boat completely in some areas. And no, Lean's not the answer, I feel :)
- Are you...?
- available for work, available for project/freelance/contract work
- Twitter profile
- http://twitter.com/xflibble
- Professional Profile (e.g LinkedIn, Xing)
- http://www.linkedin.com/in/jaredquinert
- Experience in years...
- 10+
- Do you specialise in any particular area of Software Testing?
- I'm a generalist, having worked across multiple domains, as an exploratory tester, performance tester and toolsmith
Jared Quinert's Blog
Look elsewhere :)
All my posts are on http://www.software-testing.com.au/blog/
Posted on August 27, 2007 at 12:30pm — 5 Comments
Comment Wall (3 comments)
You need to be a member of Software Testing Club - An Online Software Testing Community to add comments!
Join Software Testing Club - An Online Software Testing Community
- At 3:57am on February 6, 2008,
Jared Quinert said…
- Hi Sarah,
The simple answer is 'Yes'. I have used JIRA for bug tracking.
Mostly though, the projects or organisations in which I've used JIRA have been shooting for an agile approach. On an agile project, I'm *hoping* that the number of bugs that need to be tracked outside an iteration are minimal. Once a bug 'lives' outside of an iteration, then it really becomes work to be done just like any other story, so the distinction between a user story and a bug isn't that important.
I have a few criticisms of JIRA as a tool for agile projects:
- Managing and prioritising backlog is painful.
- Linear workflow isn't what we're aiming for. I think the way that tools model our development process can sometimes be interpreted as the 'right' way to do things. This is definitely a situation in which I don't like to defer my thinking to tools. I don't think JIRA's workflow model is helpful beyond 'Story open' and 'Story closed'. Matt Heusser discussed some of my thoughts on that here: http://xndev.blogspot.com/2007/01/agile-metrics-ii.html
I added some additional notes here: http://quinert.com/blog/index.php?itemid=19
I don't have any experience using JIRA for tracking defects in a traditional (ie. waterfall) development model. I can't see any obvious problems with it in that environment though, other than if you wanted some of the traditional integration with your test process that proprietary test management tools provide.
If you have a more specific question or problem, I'd be happy to try and answer it for you.
- At 2:50am on February 6, 2008,
Sarah said… - Hi Jared - on your blog you refer to using JIRA as a repositiry for high level agile stories - do you also use JIRA for defect tracking? I would like to hear more about your experience using JIRA for this purpose. Thanks, Sarah
- At 2:36pm on November 12, 2007,
Srinivas Radaram said… - HI Jared,
I wanted to get few of my quries clarified, can u pls reply me at srinivas.radaram@gmail.com
Regards,
Srini.
Find Us Elsewhere
Nice Things
Bloggers
© 2010 Created by Rosie Sherry
