560 results found
-
Option to add text in Dashboard
It would be useful to have some kind of text summary next to graph in Dashboard:
Example: "this and that test was failed because issue-x (minor), but the build is still released."
Could you please add this feature to the Dashboard?
-Ossi
3 votesIdo Tandy responded -
Sort/filter for sugesstions search result
Once typing query for suggestions search here, sort/filter menu disappears for query results.
Why?1 voteOmri Berkovich respondedHi,
We would pass on your request to our forum providers and let ypu know when we get an ansewr. -
Fields template
I'm working on tests for new feature.
I do not want to fill ALL fields every time I create new test, most of the are the same.
User wants to have an ability to create templates with predefined field values.
Option to make them private/public will also be nice.2 votes -
Care must be taken in titles on Google Chrome. Cursor "jumps" out of location
When I'm editing titles in Google Chrome, if I am not super careful about keeping my cursor pointed to the location I just clicked to edit, my cursor jumps to the end of the title and I end up typing in the wrong location.
1 vote -
Test Sets and Runs --> Test Instances : widen it drastically
It's way too short to know what test it is. It can be expanded but goes back to its minimum size anytime you do anything else. EZ fix with great utility.
1 vote -
When typing requirements numbers into test, link the "Add" button to the Enter key.
I keep forgetting it doesn't save the requirements I just typed and I hit "Enter." It takes me back to the test main page so I have to repeat work. Old habits die hard...
1 vote -
The Test Sets & Runs views should have a column that displays a link/icon when a bug ticket has been opened for a test within the set.
The list of Test Sets should include a column that displays either an icon or ticket link (to Jira or whatever) for sets that have a bug/issue opened. This way at a glance you can see where bug tickets have been created for failed test sets. Within the set itself there also should be a column that displays the bug tickets. Most of the competitor software already have this feature.
1 vote -
recorder
Test Case Recorder
Other test case management tools have a browser plugin that can be used to record web sessions. The sessions can then be edited and used to either create a defect and/or create a test case. This is incredibly useful and facilitates the creation of test cases and bugs. The test cases created this way can include annotated screenshots for expected results as well as videos.
Here is a link to one of your competitor's implementations of this feature: https://chrome.google.com/webstore/detail/qtest-web-explorer/ihoajedonhepnplmfgdkdjohbmadckdk
1 vote -
Anyone assigned to a issue should be automatically rolled into the notification list
It would be nice if anyone assigned to a issue is automatically rolled into the notification list. Or if this is at least configurable from the settings. What happens now is that the person has to manually add themselves as a watcher to start getting notifications and you can configure to see every notification for ever issue with is a bit overkill.
1 voteIdo Tandy responded -
Add "Tags" column to Test Library available columns
We are struggling with getting the result we are after using Search even with all the new filtering options available. We have tried filters and reports but they are all IS or IS NOT vs Contains. In a support chat, using Tags was recommended to us and we are trying it but we cannot display the "Tags" column to the Test Library view; it's not available. This would be incredibly helpful to us if this were added. Thank you.
14 votesIdo Tandy responded -
Allow field 'Actuel result' inside steps to be mandatory
Some results of a step are so important you need to be sure the tester have described the result. By do it possible to make this field mandatory you can manage this situation.
3 votes -
Test name and serial id in JSON
Hi,
We request to have a Test Name and Test Serial ID fields in the JSON sent for Test Run events.
1 voteChristine respondedHi,
Could you please clarify your request?
Thanks in advance.
Best regards,
Christine -
Request for JSON payload change.
Hi,
Requesting a change in the JSON file we receive from the webhook for the below events:
1. All issues changes
2. All tests changes
3. All requirements changesFor these events the JSON doesn't indicate which field has changed and the before and after value of the corresponding field. It would be good to have these fields added in the JSON of the above events.
1 vote -
allow quick info to be shown in test sets and runs like in Test Library
In the Test Library screen if you highlight the ID column you can click info to get a quick over view of the test. This would be good to have when inside a Test Sets and Runs too. Currently you can add the ID column but when highlighting it it doesn't show any info.
This would be useful as it would allow who ever is running the test set to get a brief view of the steps inside each test.
1 voteIdo Tandy responded -
Add number of tests in each folder in folder view
In the folder view from tests you cannot see how many tests are inside a folder until you click on it. It would be good to see the count in the folder view
1 vote -
expend the search feature when adding a test to a test run
When adding tests to a test run you can either select from the entire list of tests or run a pre made filter. It would be nice if this had a few more options such as:
- Free form search
- Select Tests from an existing run
- Pick a Folder to add tests from
2 votes -
Add to the Report a simple metrics of the overall test progress
To display the percentage of the total number of tests that have been executed (test marked as, Passed, Failed, Not Complete)
i.e. 6 total tests, 2 marked as Not Complete, 1 passed and 3 No Run.
Percentage Test Executed = 50%
Along with metrics to capture the Test completed status (Passed Test Vs Total number of tests) as a percentage.
i.e. 6 total tests, 2 marked as Not Complete, 2 passed and 2 No Run.
Percentage Test Completed: 33%
3 votes -
Overall, Practitest should remember and persist column widths and sorts
There are no pages in PT that actually remember the width of columns or sorts. This makes using PT pretty annoying for people who manage or run test sets, issues, or requirements.
61 votes -
Implement ways to manage the automation job queue
Currently, there is no way to see what jobs (test runs) have been started or are in the queue to run. Furthermore, there is no way to cancel a job once it has started. Also, only entire test sets can be sent to the job queue, when there are many times when it would be beneficial to submit only a subset of tests in the test set. For example, when you want to re-run a failed test, there is currently no way to do that without executing the entire test set again.
3 votes -
Better test step UI for running and editing test cases
Step result - Rather than just change the colour of the step name/heading, which gets lost in the links and other text above/below it, shade whole the step area/row.
If step N has a result provided (pass, fail, block), and all the steps between step 0 and step N are blank, set steps ) to N all to Pass. This will reduce the number of clicks a tester has to do in order to work through running a test case.
Allow a step to be flagged as "needing review" while the test is being run so it can be completed…
3 votes
- Don't see your idea?