QAComplete Feature Requests

At present user have to Take a screenshot from third party tool, save it locally, then click on upload and find the document where it was saved. It is a process on it own. It would be better if user can take screenshot direclty from QAcomplete tool and don't need to save it locally or just copy and paste direclty in the actual resuts. That will save lot of time.  ... 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

In our organization we use QA Complete to manage our defects and feature requests, and we have external and internal parties who deploy various features to various environments. It would be enormously helpful to be able to use QA Complete to track these deployment activities on the Defect level by enabling the inclusion of a log with entries. See Example below - While there is a history in QA Complete and even custom fields, the fields are not dynamic and there is no place to maintain a log that I can see.   My request would be to allow for either a log creation or the ability to have fields which are dependent on each other or even dynamic - i.e. Deployed to Env xxx on YYY date and intended for zzz release --- OR Check In date - targeted for release xxx -- in environment yyy  See example below of something we started doing to track our deployments (mind you I know there are separate full on configuration management solutions/web applications -- but it would be great if QA Complete had some of these capabilities... -Thank you! - Erik Hendin / Quality Manager @ 32BJ Benefit Funds...  Date Environment Affected Activity Release # (If applicable) Defect IDs deployed Deployed By (internal entity, external vendor, etc) Notes 12/7/2018 V3 Production Release R32P1 See release notes Vendor X Deployment Production of Release 32 (Patch 1 was latest code at that time) 12/11/2018 V3R4UAT CPI Deployment   13938, 13971 Vendor X Resolution of V3 System Datasheet issues 12/12/2018 V3R4UAT Script   Re: 13938, 13971 32BJ/John Smith   12/14/2018 V3QA Script   Re: 13938, 13971 32BJ/Jane Doe Re: script re: Union Representative Seq No attributes ... View more

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

Following features are decreasing the sw useability ever since new visual "upgrade": * Posibility to brows through release tree structure without the need of drop-down (in addition large font makes it impossible to read selected release in the dropdown field) * Interactive icons for "Edit", "Print Friendly", "Email", etc. are shown over the item name and number effectively obstracting it. (It is imposible to demonstrate which defect we are discussing becase when you point on it by mouse, nobody can read the title.)   ... View more

Item edit screens (such as defect edit screen) shall support drag and drop reorder, resize and autoscale features in addition to the number of columns configuration.  The current solution does not allow to configure the default fields (such as Linked Items) and leads to poor readability with multiple columns shown in addition to the fact that the screen layout does not make any use of the screen width.   This leads to poor readability of some fields (typically Linked Items) ... View more

In JIRA there is the ability to add labels to Defect/Tickets so that the user can categorize the defects and search them by these categories. Aside from adding another field, is there a way to do this in QA Complete? I noticed a dropdown option called "Tag" in notes but it does not appear to have the same purpose. In other words, let's say each defect has a theme or multiple themes I want to attribute... then I want to search defects by one or many of these themes... If not, is this something that is on the product roadmap for QA Complete? Re JIRA https://confluence.atlassian.com/confcloud/use-labels-to-organize-your-content-724764874.html Example where this has come up in our company: We have asked our users to create "Pain Point" defects outlining issues they have with one of our applications.   In some cases there are numerous "Pain Points" and topically there are different categories these items fall under - sometimes they are overlapping (one defect might have themes of SSN and Eligibility, another might have SSN and Security, another might have 834 files and Eligibility etc). If we had the ability to label and organize them, it would be quite helpful.     Thank you, Erik ... View more

We would like any failed tests in a test set to automatically rerun. We would like to be able to set the number of times it tries again before marking the test as failed. Some of our tests are flakey and don't run correctly the first time, but do pass on their second run. We would like to eliminate the manual step of rerunning the test set in QA Complete.  ... View more

Hello, I'm using test schedules in order to run automatated tests (TestComplete). I've noticed that I cannot change order of linked Tests/Test Sets. I have to remove them all and add one by one in preferred order. I'd like to request a feature that enables to manage order of linked Tests/Test Sets. In some cases I need to run automated Tests in certain sequence. ... View more

Ex. - A requirement is linked with 4 test cases. When user executes one of the test cases and marks it as 'Passed', the requirement '% Complete' field should be automatically updated to 25%. When all the test cases are marked as 'Passed', the requirement should show as 100% complete and the status of the requirement should change to 'Complete' (New status code needs to be added).  ... View more

Hi, Name mapping is a cool way to save code room on objects paths. My main concern though is that there are too many of them and it's getting messy, and it's hard to find them in the Aliases list. How about adding some sort of  "folders" that would divide them to sections base on module\subject\context and yet are meaningless code-wise? ... View more

At the time the Status of a Defect is set to "Resolved", I'd like to have the capability (via an Escalation rule or Workflow) to reset the value of the "Assigned To" field back to the Owner of the Defect.  Right now this is a manual process which we often get complaints about.  Users ask why the system can't populate the "Assigned To" field programmatically.   I could accomplish this via the Escalation Rule or Workflow if the value of the Defect Owner was included in the list which unfortunately it isn't.                                         ... View more

The highlighted object in Red has a ToolTip 'Clone Group'. When Object is spied, that property value is not associated with ToolTip. However, the Object has many nested objects and one of the nested objects has a property with property value 'Clone Group'.   There should be a way to find Property name if we have a Property value ('Clone Group' in this case) for nested Objects.       ... View more

I like to have QAC open in multiple pages. However, when I am filtering Test sets by Project and release in one window, then open another window, set that to a different Release (same Project), if I update the first page it will then now show the filter of the second page. I want them to remain separate.   To me, the above is weird non-standard behavior for a web app.   m ... 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

We have recently purchased the tool and noticed the below limitations / improvements .   Feature to assign a TAG / labels needs to be added. Assign existing defects to Test cases at the time of execution. Changes made to the test cases in Test sets at the time of execution are no local and are will be reflected in the original test cases. This is defeating the feature of Fast Edit the tool offers. Performance is very slow when trying to load Test sets instances having only 20 test cases.  JIRA Integration - Mapping needs to be done on a field level and status level.  Field level validations are not working as expected for Custom Fields. For a Text field if length 200 characters when we enter 150 characters the front end validation is telling that there are more than 20 characters in the field. UI / Performance for Test management features needs to be improved. If anyone in the group has found a solution or a work around this can you please get back to us.  ... View more

Re-running a failed test set using the Restart Run button (In Run History, click the "Restart Run" button), includes the previously passed test case count in the re-run.    For example, you ran a test set with 3 test cases. On the first run you passed 2 and failed 1 test case. Then you click in on the "Restart Run" button and pass the failed test case. When you look at the run history, it will show you 3 passed test cases. This makes it seem like you re-ran 3 test cases instead of 1.  ... View more