How our testers use Mingle
We currently have two people testing Mingle – and both use Mingle to manage their test cycles. As they’ve been using Mingle to test since the very start of the project, we now have over 900 tests, including 231 automated acceptance tests. This coverage lets us continually enhance Mingle, while knowing we won't be breaking existing functionality.
What are some of the key things Mingle provides to a tester? Firstly, we link our defects to stories / requirements. This is simple to do and ensures requirements are on hand when fixing defects. We also link subversion check-ins to defects via commit messages.
When defects are created, we assign properties such as: status, priority, owner and so on. The team can then sort and filter lists of defects using these properties.
We also often add comments to defects. This is particularly useful for distributed team members, who can ask questions and view a comment thread at any time. ‘Print-screen’ images are also added to all defects – as nothing compares to being able to visualize a problem.
An example of what the discussion panel looks like on Mingle
In addition, our team has created custom 'transitions' for defects. These provide a single-click method for testers, project managers and other team members to change the status of each defect. After each iteration, we reflect on how the process works, then add or remove steps as required.
An example of what a bug transition may look like
Finally, we have created status graphs and priority break-down graphs, so all members can easily see the defect status of the project.
In short, Mingle offers testers and quality assurance professionals a considerable number of quality features. After all, ThoughtWorks believes passionately in the importance of testing.
So, why wouldn’t we highlight it as a major part of the Mingle application? Well, I'll let you into a secret. We're currently working on a powerful testing product that will, in time, integrate with Mingle.
Watch this space for more details.
Comments > (HTML is allowed)
-
PremApril 4th, 2007 @ 11:28 AM
How is this different from what I get when I install TestLink, Mantis, Docuwiki, Subversion & Scumbug?
-
Julian BootApril 4th, 2007 @ 12:38 PM
Hi Prem - good question. What Mingle offers is an integrated experience that will give you many of the features that those tools combined provide, as well as other benefits you get from having an aggregated view of the entire project.
-
ToddApril 13th, 2007 @ 02:41 AM
Looks pretty exciting and well thought out. Eager to play with it. There's huge opportunity in this space for software that's easy, well-designed, and even--gasp--enjoyable to use. You guys are on to something!
-
Zac ZavosApril 19th, 2007 @ 05:08 AM
Thanks Todd - you capture exactly what we're aiming for - something that is powerful because the team actually want to use it.
-
Andrei NadinApril 19th, 2007 @ 08:41 AM
One question - one of the probable issues with an Agile software solution can be the ease with which face to face meetings fall away - have you found people using the tool more than the process?
-
Keith SterlingApril 23rd, 2007 @ 05:17 PM
You've re-writen Jira, why ? Not one requirement you've mentioned in this blog is not available in Jira, an infinitely more mature product than Mingle. I suppose its one way to keep the Bench busy
-
Christian RomneyApril 24th, 2007 @ 05:58 PM
Have you guys settled on a pricing model? Will there be a free/basic plan?
-
Zac ZavosApril 25th, 2007 @ 10:24 AM
Hi Keith, There are lots of great software products out there which focus on a specific area, which we wouldn't knock. But Mingle has been built from the ground up with a focus on delivering agile projects. So the core features, such as integrating requirements and defects with source code, drag and drop grid-views and powerful reporting, are things ThoughtWorks has found are needed on agile projects.
-
Zac ZavosApril 25th, 2007 @ 10:37 AM
Hi Christian, There will be a free version for small teams, open source and non-profit organizations. We'll be announcing more details on this leading up to the June release.
-
DavidMay 1st, 2007 @ 05:24 AM
Andrei asks above:
"one of the probable issues with an Agile software solution can be the ease with which face to face meetings fall away...have you found people using the tool more than the process?"
We've been using Mingle to support the building of Mingle since the end of our first iteration and we have not found this to be the case. Face-to-face conversation continues to be our primary means of communication simply because that is how we like to work. We would never tell you that Mingle will give you a development process or allow for less face-to-face communication on your team. Be suspicious of anyone attempting to sell you a tool with such claims!
What Mingle can do is improve the quality of all team communication by providing the entire team a consistent, up-to-date view of your project's status and issues. If your process is broken or your team is not communicating, you really need to fix that before taking a look at Mingle.
-
FilippoMay 15th, 2007 @ 07:18 PM
Will Mingle integrate with Fitnesse?
-
Zac ZavosMay 16th, 2007 @ 12:59 PM
Hi Filippo, Mingle has been built with a plugin architecture in mind, so integrating with something such as Fitnesse is definitely a possibility, though not for the first release.
-
Dave WalkerJune 7th, 2007 @ 02:16 PM
We've just started looking at this and I like what I see. One problem we'll have though is that we use Bugzilla right now, for pretty much everything - cross office and cross departments, so we're not going to drop it. A few people have raised concerns about having to manually link Mingle and Bugzilla together. I see from Zac's response that Mingle has been built with a plugin system - is Bugzilla on the integration list, or do you see it as occupying another niche completely?
Sorry, comments are closed for this article.
