We are currently trying to implement QAD (with Reconcile and Track Record) into our QE team. For years we have been working with Word for all our Test Procedures and cases. We are very eager to go paperless and have a system that will link requirements to test and defects. I have successfully rolled out Reconcile and Track Record but I am struggling with QAD (CARS Workbench).
Is there anyone using this suite and is so how are you handling larger QE teams, regression suites, smoke tests etc.
We are finding it difficult to see how this will work for us when we are doing iterative development and we have build cycles of 2 - 3 weeks.
I would be really grateful to anyone who could give me some insight to this product.
**We are using QAD version 5.3.1, TR Version 6.3 and Reconcile Version 2.0**
I'm trying to do the same and am struggling to see how all the elements fit together within QADirector and QACentre Portal.
I'm particularly confused by test cycles.
In my organisation a test cycle is a batch of testing that you do on a release of software during the iterative process of developing/testing prior to release into live environments. Is this the same in QADirector/Portal?
I cant see how I can replicate this in Portal - you seem to need to use the requirements section, but unfortunatley I can't see a way of linking the tests in my test suite to the requirements.
Further to this - in QADirector itself you don't even get the option to view requirements.
Any tips would be greatly appreciated. The online help is useless (The tutorial doesn't even cover this fundamental part of setup) and Compuware support is pretty slow.
I feel you, we have been working hard to try to work through many of our issues. The major issue is that the QAD client and the CARS web are not exactly the same. I have been in touch with compuware and they are releasing a new version of QAD in the spring which will help fill in some of the gaps.
For the moment we are bouncing between the client and the web to accomplish what we need, and have some hacky work arounds.
One area we are struggling in is linking defects logged outside of QAD. In the perfect world maybe all defects will be logged by QE using QAD but that is just not the case. We have teams from Development, service and even customers that will log defects and we then need to link them to the requirements.
To be honest it is not the best tool available for interative development (Compuware even admitted they were not there yet). We have our fingers crossed and are hoping they will improve this (we had a peek and it is getting there).
If there is anything I can help with or if you run across something feel free to email me directly and I will do my best to help.
Cherrooh - please do not encourage people to email you directly. That does not help the larger group. It is much more effective, and also in keeping with the philosophy of SQAForums, to have an open, PUBLIC discussion of issues and answers.
Instead of encouraging people to email you directly, encourage them to post here, and post your advice here as well, so that as many people as possible can benefit from the discussion.
Sorry for encouraging people to email me directly...I did not mean to exclude anyone from help, I would post anything helpful if needed.
To be honest there are many times people direct others to support for assistance...when in a lot of cases we can offer some help...this is really no different. We do not get anything from people calling support.
I get what you are saying for sure, makes total sense but the philosophy of SQAForum should be reminded to everyone. all we can do if people gather information from other sources, is ask that we all come back and share it.
Thanks for the reminder and I will post any information I can here for everyone to read.
We have been using QAD/CARS for about 1.5 years and understand what you are going through. We spent about 2 to 3 months just trying to determine how we wanted to set up out projects. CARS is an improvement over QAD in that is allows you to 'link' (create you test execution suites) from the requirements. We are also looking forward to the new version of QAD (6.0) due out this spring. From what I have been told it is a combination of the current QAD with CARS and will be a client but will support installs of the application and patches from a web site.
don, CSTP, QAD/TP user since 06
Test Partner 6.3; QAD 6.1; QADLoad 5.9