Status:
New Idea
Submitted on
ā06-05-2018
06:22 AM
Submitted by
msternak
on
ā06-05-2018
06:22 AM
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
Status:
New Idea
Submitted on
ā05-16-2017
10:57 AM
Submitted by
sheba0907
on
ā05-16-2017
10:57 AM
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
Status:
New Idea
Submitted on
ā07-04-2016
12:33 PM
Submitted by
rachel_hughes
on
ā07-04-2016
12:33 PM
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
Status:
Accepted for Discussion
Submitted on
ā06-22-2015
09:56 AM
Submitted by
kwiegandt
on
ā06-22-2015
09:56 AM
It would help us cut down on duplication if we could link to an item in another project.
... View more
Status:
Accepted for Discussion
Submitted on
ā05-26-2015
07:20 AM
Submitted by
GrumpyGit
on
ā05-26-2015
07:20 AM
Can you please reduce the SmartBear Banner at the top of the page. This will enable us to see more of what we have purchased the product for.. Can you also reduce the of the Customer Company logo box (bottom left hand corner). It's nice to have our logo on screen but if we can configure the size of the box or turn it off it makes the product more usabale. Thanx
... View more
Status:
New Idea
Submitted on
ā04-02-2015
08:59 AM
Submitted by
bromeijn0011
on
ā04-02-2015
08:59 AM
Why is it that there still is no mobile app for ALM or qacomplete? It's a shame, because most competitors do have it and it can become a breaking point for us.
... View more
See more ideas labeled with:
Status:
New Idea
Submitted on
ā01-09-2018
04:23 AM
Submitted by
mijex71989
on
ā01-09-2018
04:23 AM
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 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
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
Status:
New Idea
Submitted on
ā01-05-2017
08:25 AM
Submitted by
lrayTalen
on
ā01-05-2017
08:25 AM
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
Status:
Accepted for Discussion
Submitted on
ā10-30-2015
07:18 AM
Submitted by
vpaka
on
ā10-30-2015
07:18 AM
Color Code alert on all Linked Items when there is a change in existing Requirements has been created and assigned with a Standard priority. We will respond to you as soon as possible. [Case - 00140954] Most of the time Business Analysts modify requirements or add additional Information to the requirements. It would be really nice to have a feature which would highlight the change and affected Items for user and Project benefit. Recomendation - highlight all those linked Items with a "YELLOW" color so that all related Users, once logged into QAComplete, can see and acknowledge the change
... View more
Status:
Accepted for Discussion
Submitted on
ā08-17-2015
08:15 AM
Submitted by
vpaka
on
ā08-17-2015
08:15 AM
It would be a really good feature to have an abiltiy to link an existing active defect that causing the test to fail during the Test Execution from the Test Set. Currently all we can see is "Auto Create Defect" window. This would be really helpful in failing test case and continue to excute the restof the test cases from test set by simply adding an existing defect to it
... View more
Status:
Accepted for Discussion
Submitted on
ā06-22-2015
06:30 AM
Submitted by
kwiegandt
on
ā06-22-2015
06:30 AM
In the Test Library, I can display all tests linked to a release or not linked to a release by using a filter. This is not intuitive to many of our testers. To be consistent with the other entities in the system, it would be helpful to have a Releases tab in the navigation pane on the left before the Folders tab as is the case for Test Sets.
... View more
QAC does not allow any user to be fully deleted from the system. Currently, deleting a user results in the "Active User?" field not haveing a green check mark. The reason behind this is maintaining historical record if someone created, ran, or otherwise modified anything within the system. What if you have an account that never executed tests, created tests, etc; i.e. not associated with the historical record of any object? In my case, I created a test account to try the security configuration after making changes, but prior to exposing end users to them. If I no longer need this account I would like to remove it entirely.
... View more
Status:
Selected for Development
Submitted on
ā04-20-2015
03:20 AM
Submitted by
jana_horackova
on
ā04-20-2015
03:20 AM
I would like to add the Test Case Priority parameter displaying at the Test Runner window. Now, is not displayed and it is not possible to change by application administrator settings. We need to see it, when we work with test cases at running test set, because we have the different priority test cases in the one test set and when run started, we choose the test cases one by one by their priority, ideally. And we don`t use a way to dispense a test cases by a priority to separate test sets. Please join this proposal to change. Thanks Jana
... View more
We have the option to inactivate Releases and Test Cases, why not provide that capability for Requirements?
... View more
See more ideas labeled with:
Status:
New Idea
Submitted on
ā11-30-2017
07:45 AM
Submitted by
Novari-QA
on
ā11-30-2017
07:45 AM
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
Status:
New Idea
Submitted on
ā05-18-2017
07:45 AM
Submitted by
sheba0907
on
ā05-18-2017
07:45 AM
There are so many different screens and buttons and choices when entering a Test Set Suite or a Test Case or a Test Step it can be confusing on where you are at times. add a new step, I select the test and go to steps. The button only says Edit Steps and after you select it, only then do you get an option to add a step. Would be nice if the button said Add/Edit steps like it does when it says Add/Edit Tests. when in a screen, when what user is doing is displayed at the very top left of the screen, would be nice if it were a bit more visible
... View more
Currently when using tokens during the test run a person cannot tell what are the token values and what aren't. It would be useful to have token values visually identified in some way in the test step during a test run. They could be bolded, highlighted, underlined, different color font, or somthing.
... View more
Status:
Accepted for Discussion
Submitted on
ā07-06-2015
09:48 AM
Submitted by
TBValdez
on
ā07-06-2015
09:48 AM
Recommending that the reporting feature within QA Complete be updated with more flexibility and user friendliness. One thing our QA team does for reporting is generate test metrics reports which list the Test Set Name or Test Name, the # of Tests (not runs), # passed, # failed, # blocked. While we understand the logic behind displaying the values off the # of runs for the tests for reporting purposes, our customers and project teams do not want to know that we executed a test set 3 times and it failed twice. They want to know the # of total tests (baseline #), # passed, # failed, # blocked and not based off of execution. They do not want to see that we ran Test A, itertion #30, 6 times. For example, if Test Set A has 5 tests but with tokenization has 300 test iterations the report needs to display 5 tests for this Test Set and note the # failed, # passed, # blocked. Right now the canned reports in QA Complete are displaying this based on the tokenization iterations which is too detailed. We have spent hours working with these reports but with reporting being built around Crystal Reports this limits our ability to build the report we need.
... View more