It's good to have lots of tools in your toolbox. But I tend go through periods of time where I'm using a smaller set of tools a large percent of the time.
For instance, lately we've been using these tools quite a bit:
WinTask
http://www.wintask.com
BareTail
http://www.baremetalsoft.com/baretail/index.php
BareGrep
http://www.baremetalsoft.com/baregrep/index.php
PL/SQL Developer
http://www.allroundautomations.com/plsqldev.html
WinMerge
http://winmerge.org/
SharePoint
http://sharepoint.microsoft.com
Bugzilla
http://www.bugzilla.org/
MWSnap
http://www.mirekw.com/winfreeware/mwsnap.html
This article originally appeared in my blog: All Things Quality
For instance, lately we've been using these tools quite a bit:
WinTask
http://www.wintask.com
We use WinTask for most of our website automation tasks, regression tests, etc. It's very easy to use, yet amazingly powerful.
BareTail
http://www.baremetalsoft.com/baretail/index.php
Our systems tend to have fairly comprehensive logs which provide a lot of useful information for analyzing the results of tests. BareTail makes it easy to watch several logs simultaneously, and highlight areas of interest.
BareGrep
http://www.baremetalsoft.com/baregrep/index.php
Our systems tend to have a lot of configuration files. BareGrep makes it easy to search through them and find the desired settings.
PL/SQL Developer
http://www.allroundautomations.com/plsqldev.html
We use this for pretty much all of our analysis of database activity, for creating test data, for testing stored procedures, etc.
WinMerge
http://winmerge.org/
Often our testing involves comparing the recent output to baselines. Sometimes the output comes from our system-under-test, sometimes the output is created during our automated tests. WinMerge makes comparison with the baseline, and analysis of the differences, very efficient.
SharePoint
http://sharepoint.microsoft.com
We keep our development and test assets (Requirements, Specs, Test Plans, Schedules, Checklists, etc) in SharePoint.
Bugzilla
http://www.bugzilla.org/
Our bug-tracking tool of choice.
MWSnap
http://www.mirekw.com/winfreeware/mwsnap.html
We're currently using MWSnap for screenshots, typically for attaching to bug reports.
This article originally appeared in my blog: All Things Quality
My name is Joe Strazzere and I'm currently a Director of Quality Assurance. I like to lead, to test, and occasionally to write about leading and testing. Find me at http://strazzere.blogspot.com/. |
Its great to hear about some new tools. Thanks!
ReplyDeleteThank you for the post, I was looking for tools like BareTail and BareGrep.
ReplyDeleteGlad you liked it. I use BareTail every day.
ReplyDeleteDo you script automated testing using BareGrep'scommand line capability?
DeleteActually, I haven't tried that. I'll have to look into it.
DeleteJoe, any thoughts on building your own bug tracking software under sharepoint using microsoft infopath? I've considered this, I've also considered just keeping bugzilla and datamining it from sharepoint to do other forms... but, sadly, sharepoint doesn't play well with mySql so therefore I seem to be screwed. Any ideas of a work around?
ReplyDeleteSorry, Bryan. So far, we have chosen not to try and interface Bugzilla and SharePoint. We had considered using some SharePoint forms for our bug tracking, but we don't have the in-house expertise to make it come out better than just sticking with Bugzilla.
DeleteHi Joe,
ReplyDeleteAny performance tool you are using?
Thanks
Tzafi
Tzafi - lately, we've mostly used internally-developed tools for the little performance testing we've been doing.
DeleteWe have used OpenSTA in the past. That worked out pretty well.
Thanks Job for your prompt reply and congratulation too!
ReplyDeleteI'm looking for a performance open source tool which will not require to write much of scripting...any knowledge about this kind of tool beside Jmeter?
Thanks.
Sorry, no.
DeleteOpenSTA can record scripts quickly, so doesn't require much script writing. Other than that, I don't have a suggestion for an open source tool.