At work we currently use Trac to manage our test cases. However, we have quite a few TCs that are listed on test plan wiki pages instead of tickets.
在工作中,我们目前使用Trac来管理我们的测试用例。但是,我们在测试计划维基页面上列出了相当多的TC而不是票证。
My manager has recently become interested in better documenting the results of manual testing. While this is a noble goal, and several of the people on the QA team are quite gung-ho about the idea, I actually feel that the overhead for such a system may be disastrous if not executed correctly. In fact, the only sane non-Trac integrated solution I can think of is just a simple task manager, where we can store and manage more casual results like, "X ran through Component Y on Env blah at this date and there were these problems". I think that porting over several TC numbers and stuff from the wiki would take ages and some kind of system like "X verified TC 23423432 at time Y and it's passing" is only suitable for automated tests when there's that many test cases (and a small team).
我的经理最近对更好地记录手动测试的结果感兴趣。虽然这是一个崇高的目标,并且QA团队中的一些人对这个想法非常了解,但实际上我觉得如果没有正确执行,这样的系统的开销可能是灾难性的。事实上,我能想到的唯一理智的非Trac集成解决方案只是一个简单的任务管理器,我们可以存储和管理更多随意的结果,例如“X在此日期通过Env blah运行组件Y并且存在这些问题”。我认为从wiki移植几个TC数字和东西需要很长时间和某种类型的系统,例如“在时间Y验证TC 23423432并且它正在通过”仅适用于有很多测试用例的自动化测试(和一个小的球队)。
I have seen a few plugins for Trac that allow you to create test plans and the like and report results - but nothing that exciting. Has anyone had experience with these tools? Integration with trac would greatly reduce the overhead, but we still have the issue of not every TC being filed as a ticket, which we'd have to address.
我看过Trac的一些插件,可以让你创建测试计划等,并报告结果 - 但没有什么令人兴奋的。有没有人有这些工具的经验?与trac集成将大大减少开销,但我们仍然存在不是每个TC都作为票据提交的问题,我们必须解决这个问题。
What would you suggest for such a project? Have you been in a similar situation? Your input would be greatly appreciated, as I don't want to be the only nay-sayer on the team and look lazy because of my opinion that over-organizing manual testing with such a small team would be detrimental.
您对这样的项目有什么建议?你有过类似的情况吗?您的意见将非常感激,因为我不想成为团队中唯一的说话者并且看起来很懒惰,因为我认为过度组织这样一个小团队的手动测试会是有害的。
6 个解决方案
#1
You might want to take a look at our test management tool TestRail. TestRail integrates with any web-based bug tracker by allowing you to link test case results to bug reports and we designed TestRail to have a lightweight/fast UI to make managing test cases and recording results as painless as possible (I know that some of the established tools, well, don't shine in this aspect). We also plan to add support for automated tests later on. Here are more details about the Trac integration:
您可能想看一下我们的测试管理工具TestRail。 TestRail通过允许您将测试用例结果链接到错误报告,与任何基于Web的错误跟踪器集成,我们设计了TestRail,使其具有轻量级/快速UI,使管理测试用例和记录结果尽可能轻松(我知道一些已建立的工具,好吧,不要在这方面发光)。我们还计划在以后添加对自动化测试的支持。以下是有关Trac集成的更多详细信息:
#2
TestLink is a really nice way to manage all your test cases; it has Trac integration and is actively maintained.
TestLink是管理所有测试用例的一种非常好的方法;它具有Trac集成并且得到积极维护。
#3
You try this Testlink and Bugzilla Both are open source and easy to use use this links 1. http://teamst.org/ 2. http://www.bugzilla.org/
你试试这个Testlink和Bugzilla这两个都是开源的,易于使用这个链接1. http://teamst.org/ 2. http://www.bugzilla.org/
#4
Check out AceProject. Though it is a complete project management tool, it can come handy for maintaining manual testing results and test cases too.
查看AceProject。虽然它是一个完整的项目管理工具,但它也可以方便地维护手动测试结果和测试用例。
#5
I work with some heavyweight tool which is HP QualityCenter. It lets to organize tests, search them by any property/text, generate tests statistics, some reports, defects management. It is expensive, so may be to much for you, but you should find something else to do test management.
我使用一些重量级工具,即HP QualityCenter。它允许组织测试,通过任何属性/文本搜索它们,生成测试统计信息,一些报告,缺陷管理。这是昂贵的,所以对你来说可能很多,但你应该找到其他的东西来做测试管理。
As for question is it worth... it depends. If it is few months project, maybe it is to much overhead. But regardles of the team size if system is complex and you will be working on it for some time really consider trying some test management system. I work as only tester with 4 developers, so team is relatively small. But what we work on is quite complicated. It is not one single application, but whole system. It is a web app with collection of small tools that are called from master web app. Additionally it is also interaction with MS Project and MS Excel (with collection of our build in tools). There is additional tool for admin tasks. Oracle Hyperion server for reports. Some Citrix virtualization. Bunch of interfaces for interaction with other systems. Just another corporate app. It is 3-4 years old, 0ver 2000 changes/implementations done. Since beginning few people on the team changed, few people form business changed. And there is lots of users.
Without Test Management system we would lose control quickly.
至于问题是否值得......这取决于。如果它是几个月的项目,也许是很多开销。但是如果系统很复杂并且您将在其上工作一段时间,那么团队规模的问题确实会考虑尝试一些测试管理系统。我只与4名开发人员一起工作,所以团队规模相对较小。但我们的工作非常复杂。它不是一个单独的应用程序,而是整个系统。它是一个Web应用程序,包含从主Web应用程序调用的小工具集合。此外,它还与MS Project和MS Excel(我们的内置工具集合)进行交互。管理任务还有其他工具。用于报告的Oracle Hyperion服务器。一些Citrix虚拟化。用于与其他系统交互的一堆接口。只是另一个企业应用。这是3-4岁,完成了2000次更改/实施。从一开始,团队中很少有人改变,很少有人改变业务。并且有很多用户。没有测试管理系统,我们将很快失去控制。
So I would say, you need test management only if you are loosing control over testing activities. Don't try new tool just to have your manager nicer reports. use it if current reports and test management capabilities are not sufficient.
所以我想说,只有在失去对测试活动的控制权时才需要测试管理。不要尝试新工具只是为了让经理获得更好的报告。如果当前报告和测试管理功能不足,请使用它。
#6
Check out FogBugz. It's really really slick. Have used most of the major software for manging testing and it is by far up there in the top 2 or 3.
看看FogBugz。它非常光滑。已经使用了大多数主要软件来进行整理测试,并且它在前2或者3中排在前面。
#1
You might want to take a look at our test management tool TestRail. TestRail integrates with any web-based bug tracker by allowing you to link test case results to bug reports and we designed TestRail to have a lightweight/fast UI to make managing test cases and recording results as painless as possible (I know that some of the established tools, well, don't shine in this aspect). We also plan to add support for automated tests later on. Here are more details about the Trac integration:
您可能想看一下我们的测试管理工具TestRail。 TestRail通过允许您将测试用例结果链接到错误报告,与任何基于Web的错误跟踪器集成,我们设计了TestRail,使其具有轻量级/快速UI,使管理测试用例和记录结果尽可能轻松(我知道一些已建立的工具,好吧,不要在这方面发光)。我们还计划在以后添加对自动化测试的支持。以下是有关Trac集成的更多详细信息:
#2
TestLink is a really nice way to manage all your test cases; it has Trac integration and is actively maintained.
TestLink是管理所有测试用例的一种非常好的方法;它具有Trac集成并且得到积极维护。
#3
You try this Testlink and Bugzilla Both are open source and easy to use use this links 1. http://teamst.org/ 2. http://www.bugzilla.org/
你试试这个Testlink和Bugzilla这两个都是开源的,易于使用这个链接1. http://teamst.org/ 2. http://www.bugzilla.org/
#4
Check out AceProject. Though it is a complete project management tool, it can come handy for maintaining manual testing results and test cases too.
查看AceProject。虽然它是一个完整的项目管理工具,但它也可以方便地维护手动测试结果和测试用例。
#5
I work with some heavyweight tool which is HP QualityCenter. It lets to organize tests, search them by any property/text, generate tests statistics, some reports, defects management. It is expensive, so may be to much for you, but you should find something else to do test management.
我使用一些重量级工具,即HP QualityCenter。它允许组织测试,通过任何属性/文本搜索它们,生成测试统计信息,一些报告,缺陷管理。这是昂贵的,所以对你来说可能很多,但你应该找到其他的东西来做测试管理。
As for question is it worth... it depends. If it is few months project, maybe it is to much overhead. But regardles of the team size if system is complex and you will be working on it for some time really consider trying some test management system. I work as only tester with 4 developers, so team is relatively small. But what we work on is quite complicated. It is not one single application, but whole system. It is a web app with collection of small tools that are called from master web app. Additionally it is also interaction with MS Project and MS Excel (with collection of our build in tools). There is additional tool for admin tasks. Oracle Hyperion server for reports. Some Citrix virtualization. Bunch of interfaces for interaction with other systems. Just another corporate app. It is 3-4 years old, 0ver 2000 changes/implementations done. Since beginning few people on the team changed, few people form business changed. And there is lots of users.
Without Test Management system we would lose control quickly.
至于问题是否值得......这取决于。如果它是几个月的项目,也许是很多开销。但是如果系统很复杂并且您将在其上工作一段时间,那么团队规模的问题确实会考虑尝试一些测试管理系统。我只与4名开发人员一起工作,所以团队规模相对较小。但我们的工作非常复杂。它不是一个单独的应用程序,而是整个系统。它是一个Web应用程序,包含从主Web应用程序调用的小工具集合。此外,它还与MS Project和MS Excel(我们的内置工具集合)进行交互。管理任务还有其他工具。用于报告的Oracle Hyperion服务器。一些Citrix虚拟化。用于与其他系统交互的一堆接口。只是另一个企业应用。这是3-4岁,完成了2000次更改/实施。从一开始,团队中很少有人改变,很少有人改变业务。并且有很多用户。没有测试管理系统,我们将很快失去控制。
So I would say, you need test management only if you are loosing control over testing activities. Don't try new tool just to have your manager nicer reports. use it if current reports and test management capabilities are not sufficient.
所以我想说,只有在失去对测试活动的控制权时才需要测试管理。不要尝试新工具只是为了让经理获得更好的报告。如果当前报告和测试管理功能不足,请使用它。
#6
Check out FogBugz. It's really really slick. Have used most of the major software for manging testing and it is by far up there in the top 2 or 3.
看看FogBugz。它非常光滑。已经使用了大多数主要软件来进行整理测试,并且它在前2或者3中排在前面。