QAComplete Feature Requests

Currently (QAC 11.0 or older) in order to get complete Release report for example, you need to link manually all requirements and test cases which are in scope for this release. In our team we assumed logically that if you have Test sets associated to test cases and you map these Sets to a release the Tests  scenarios will be automatically associated with this release. If we have to run say full regression testing of all existing test cases in one release (like few thousands), that means that we have to link manually all these test cases to the release. The link between the above work items should em improved and automated.   Example below:   ... View more

Requesting a new Testing Results Report that provides the following:  Contains a drop-down list of the Releases for the applicable QAComplete project. Once a Release is selected, the report lists the Requirements linked to the selected Release. Under each linked Requirement, the report lists the Test Cases (Test ID & Title) linked to the applicable Requirement(s). For each Test Case listed, the Test Results are included that only pertains to the Release selected.  Via "Legacy Reports", "Adhoc-Detail", "Requirements Report", we can generate the above report except it doesn't support item #4.  I submitted a support ticket (Case #00235269) but was told it was unlikely any future work will occur in the Legacy Report section.  As such I request the capability of creating this report in the Reports UI but I need your votes to make it happen.       Our organization is deeply committed with the capability of linking Requirements to Releases and linking Test Cases to the applicable Requirements.  In fact, we've included the above report as part of our SDLC making it a required deliverable before a service request can be completed.  We purchased QAComplete because this functionality (Requirements Traceability) supported our objective in a new Test Management tool.  Overall, QAComplete supports this functionality but from our perspective falls short in acccurately reporting it.     Thank you for your consideration.   ... View more

Many organizations rely on requirements documents in Word to communicate requirements to the business for review and approval. In my organization, for example, we do no have (nor is it likely we will ever have) the business log into QAComplete (or any other requirements/testing tool) to review requirements. All such reviews are conducted via Word documents.   Currently, my only option via QAComplete is to export project requirements to Excel and then copy/paste these into a Word template used for requirements. This works, but is awkward at best.   Adding the ability to generate a Word-based requirements document from a template would make the requirements part of the tool much more useful to business analysts. ... View more

At present we can copy Test Set from one project to another. But there is no way of copying TestSet. For organization they have mutiple module which might need to run across same Standards and Framework related testing. Each time for 50 plus module I have to manually create same Test Sets which I already created for others. There should be easier way to copy those TestCase as long as the folder structure is same as previous project. Or should be a way to import it.  ... View more

At present develoepers are not using QA complete to find out the defects. I have to send them the list of defects. I didn't find any way to send Screenshot along with TESTSETS that were ran for which we added screenshot under Actual Results. So, we have to manually create another word document to send it to Developers with all defects along with the Word document which has screenshots. I noticed under "Run History" for each test sets we can click on "Printer Friendly" option that can be saved as PDF to developers but it is missing a screesnhot which were added during run. Please find a way to include the screenshots with that "Printer Friendl"y report or find a way just to extract "Printer Friend" version of defects only with screenshots. That will help us eliminate creation of another word document which is time consuming.  ... View more

We recently began using QAComplete, and are missing a screenshot tool that our former QA app had available right on the test/defect ribbon bar.  We could select the icon to launch a feature allowing us to capture our screen, or a portion of our screen, and then automatically attach the picture to the defect, test, or individual test step - all without having to navigate away from the tool or save an image.  This is the #1 request we're getting from our users as we roll it out.    Do we know if there are any plans to include a screenshot tool in a future release?   Thank you! Jamie ... View more

I’d like to suggest a potential improvement of introducing bulk link items feature. For instance right now if I want to link a test to requirement I need to do it one by one. It would be great to have option in Fast Edit > Update multiple items > Link multiple items to Requirement/Agile Task etc. ... View more

Let’s say that I have two releases, Alpha and Beta. I run my tests sets for the Alpha release and all test sets pass. I have not executed any test sets for the Beta release yet. In the navigation pane on the left, I select the release Alpha and choose last run status as one of the fields to display on the test set listing. All test sets show as being passed. So far so good. Now I switch the release in the navigation pane to Beta and the last run status column still shows all test sets as being passed. This is very confusing, as no test set has been run yet for the Beta release. The last run status should show “not run” or nothing, but not “passed” or “failed”.   Now I execute all test sets for the Beta release and they all fail. In the navigation column on the left, I select the Alpha release. The last run status for all tests shows as failed, which is not appropriate for the Alpha release.   This can be very confusing. It would be VERY helpful if the software could look at the run history records and determine the last run status that is appropriate for the release selected.   This same issue exists on the test library dashboard chart called “Tests by Last Run Status (Current Project)”. ... View more

We have about 2500 tests at this time.  As the process of connecting that many tests, even organized into test sets, is cumbersome (creating another suggestion for that issue), it would extremely helpful to be able to clone a release or iteration to another release or iteration, and carry across the linked items (we only use tests, not sprints or requirements).  That way, even though I would have to manually link all the tests to a release, at least for the next release, I could clone and be done, and just add any new tests (or test sets). ... View more

The last run status on a Test Set can be confusing, especially for a newbie like me 🙂   I started a test run, some tests failed and I ended the run Run History shows status = failed (good and accurate) Test set list in right nav shows failed (good and accurate) I started the test run again, did not End Run, just Save & Close Run History shows status = In Progress (good and accurate) Test set list in right nav shows failed (not current, not accurate and confusing)       ... View more

Rename Pause Run and Start Run in Test Runner to Pause Timer and Start Timer as the test run can be edited despite the buttons names. ... View more

We have the option to inactivate Releases and Test Cases, why not provide that capability for Requirements?   ... View more

We are not used to use the am/pm notation and I keep getting confused if my scheduled tests will be run in the morning, or afternoon. So I would like to have an option that the 24 hour notation is used everywhere. ... View more

I would like a report similar to the 'Test Coverage Run by Test Set' however, I would like the report to display only the last result.   So, if I have a release with multiple builds this report currently consolidates all results.  For example, if the release has 2 builds:  -          The first build might result in 10 Passes and 10 Fails -          The second build might result in 10 passes – we may or may not re-run the already passed tests.   In this scenario the report for the release will display a total of 20 passes and 10 fails – I would like it to show just the last recorded status – irrespective of the build it was run in.   ... View more

Dont make the 'Time Out' value mandatory in the 'Add Automation' window. I have tests that vary widely in the time they take to run, it is not possible to pick a magic value that works for all tests. Also, I have  wait and auto timeout settings configured in Test Complete which are more than adequate for quitting a test if it doesnt repsond after a certain amount of time. This setting at best seems pointless, at worst is seems to be duplicating functionality that is already in Test Complete. ... View more

Many of our tests have more than six lines per step.  We can't see these in the Step frame of the right panel of the Test Runner without scrolling, which is annoying.  It's more important to us to see everything in the Step frame than see what's in the Expected and Actual Results panels.  It's not practical for us to hover over the step in the left nav because sometimes we have to copy/paste text from the Step box. Also, the lines in the test step were entered single-spaced in the Test Editor and the Test Runner shows it as double-spaced.   I suggest that you change this panel to allow the user to pull down the line in the center of the frame to act as dynamic resizing of the top of the frame that contains the Step box.  This will let the user see more in the Step box and less of the Expected and Actual Results boxes, or the reverse if they choose. ... View more

Linking requirements to tests is a time-consuming task - there is no quick and easy way to do it. It would be great if you could include the path/name of the requirement(s) a test should be linked to in the CSV file that is used to upload tests into QA Complete.  The prerequisite would be that the requirements are loaded prior to loading the tests. ... View more

With our project, we have a very dynamic system. That being said in order to simulate proper users with realistic fields, we have to build around 50 + users to manually and automate test. QAComplete does not offer a way for us to utilize a single test case, lets say for the example of Logging into a system with username and password.  The username and password can be tokenized however, it is tokenized once. We want a method in which we can define the parameters in a test case from a test set.  The test set will simulate User1s experiance but it will constantly use the test case for logging in.  Perhaps testcomplete offers something like this?  We essentially want to treat specific test cases like functions with parameters ... View more

QAC has predetermined required fields; denoted (Required).  These cannot be made optional.  While I understand the intetion behind this, I do not wish Work Phone to be a (Required) field when creating a user.     ... View more