14 Answers
14

We've recently released a tool called TestWave that might be of interest to you. You can link your tests designs to both requirements and releases. You can then reuse that test design in multiple test sets or releases. There's a free 30 day trial on the web site too.

You might want to take a look at tool at our test case management tool, its called Test Collab.

We have a unique feature which basically allows you to link Test Suites across multiple projects.

I can describe this feature best by our own example. Our development involves a reusable layer which is used across all our projects, so there are some test cases/suites which are repeated across multiple projects, say 'Verify CSS/JS Compression', now to avoid writing same case across all child projects everytime, we just link its parent test suite to the child project. And child project always shows up that test suite listed inside it. Here's a little screenshot to make it more clear:

Maybe its not exactly as per your requirements, but I think it'll solve the problem.

I don't know which specific tools meet that criteria, but perhaps a simple way to search for the tool you are looking for would be to find any test management tool that supports categories for it's test cases. I know that the home baked solution I used previously would allow me to add any number of categories to a test case and then I could query and filter on those categories. It sounds like this would give you what you are asking for.

Cool, I will look for those keywords and see what looks good. I am certainly open to product suggestions too that have "category" functionality. I don't have experience evaluating any QA tools. I am a programmer in a growing company that finds itself needing to keep track of way more "tests" than we used to as we develop more complex systems.
–
jgv999Nov 4 '11 at 22:16

It's a bit late for this to be of assistance to the original poster, but for anyone else looking for something similar I would recommend having a look at Enterprise Tester. Disclosure: I work for the company that develop it.

It is very flexible and offers the structure and re-use requested above. You can grab a free 30-day trial of Enterprise Tester from our site or get started with a $10 license. We also offer free Open Source / Charity licenses for those that qualify.

Yes, Jenkins job-server can accomplish much of what you need. Your tests can be written with anything and then stored in something like a Subversion source control repository. Then, Jenkins can check out tests and run them based on arguments that you give to the scripts that launch those tests. Each project could have its own set of multiple tests suites and display its own test set in a separate tab within the Jenkins UI.

@Ankjur-Chandra - I haven't used QC or Test Director for a while now, but I don't recall it matching all the requirements in the question. Do you want to explain why you feel this suggestion matches jgv999's needs? Otherwise it's not a very useful suggestion for them.
–
testerab♦Nov 5 '11 at 17:34

@testerab, Thanks! I could not figure out how this would work based on the documentation I pulled back. I appreciate the input.
–
jgv999Nov 7 '11 at 15:51

This is possible to do if you have TFS2010 and the Microsoft Test Lab Manager. So long as all your team projects are held within a single collection, you can create a test suite by querying any Test Case work items, regardless of which team project they were created under.

You may have to do some tweaking to the work items and put some thought into how you set TFS up, but it should be possible to do what you have asked.

We've recently launched a new testing tool, Testpad, that might help in this scenario.

Testpad uses a structered-checklist approach to
organise tests, including being able to draft and save checklists (scripts) as templates.

You could use its templates in two ways as a solution to your problem:

a) define one big template with various sections for different sets of tests (some generic, some specific to different products, some specific to different client/product combinations); and then have testers instantiate (i.e. start a script by copying) this template and deleting all the sections that don't apply (very easy in Testpad), OR

b) define a family of templates, with a template for each of the various sets of tests you've got; and then have testers run the relevant subset of templates.

Neither option is exactly assigning test case to multiple projects, as it's instead copying cases out of a template, but depending on your process, might nevertheless fit the bill.

QC is a good test management tool.. you can use it to map the testcase to the specific requirement and execute the test case directly from there, also it has many more features. you can use the 30 days trial version to start with. its easily downloadable from the hp site.

You should check out TestWave (www.testwave.co.uk). There are various options for having tests in multiple projects, such as copying them between projects, or creating a release for each of your customers within the same project.

SQS-TEST/Professional provides several means to answer these questions:

you can add your own attributes (like "test for customer:" or "test for product:") to test cases and filter test cases by using these attributes.

you can link test cases with requirements they cover, so could use "Requirements for customer X" and "Requirements for product Y" to link test cases to (that means high level test cases as well as low level test cases). In test execution, you can than generate manual testing tasks for all test cases that cover a set of requirements, which gives you the desired test cases.

or, working with multiple projects, you can create a base project with all your test cases that you work on and then synchronize all test cases from this base project into a customer specific project. To decide which test cases are synchronized needs an intial configuration step and afterwards is tool-supported.

PractiTest is a powerful yet easy to use Test management tool that supports sharing tests between projects.
Use the link to read more about it or contact PractiTest support if you like to setup a demo to review it.