562 results found
-
Need a duplicate test name warning
Need a warning when creating a test case if the name is already in use. This should be an option in settings, since I know some testers don't need this. However with my team, each name needs to be unique. So having a warning when we are duplicating a test name would be helpful.
5 votesIdo Tandy responded
-
Add Collision detect on Test edition
We have encountered situation when I have edited the Tests while my colleague had it open and editing. I have saved the changes first and when he saved his, mine were lost. It is quite a big problem in distributed large teams. Please take a look.
5 votes -
Add the ability to edit the default JIRA ticket text
After clicking 'Fail & Issue', a JIRA ticket is created with the 'Summary' field populated automatically with "Bug reported from test: " followed by the test name. This can make the name unnecessarily long or potentially not follow existing naming conventions for a particular JIRA project. It would be nice to set a custom value for this pre-populated text, instead of editing it manually each time. For example, I use "PT Report: " as an abbreviated version. A company might want an even shorter code.
It might also be a handy feature to choose to put this text at the…
5 votes -
Enable add a screenshot embedded in the text instead of as an attachment
this will be useful when we would like to show what is the expected results for example or if there is an issue just take a screenshot and show it to our development team
instead of having to save the screenshot and adding it to the issue ...this will be useful also for showing screenshots of the tests and expected results
Thanks.
5 votes -
Edit custom fields on filtered lists
It would be nice to be able to edit custom fields on filtered lists, as you can with the default system fields. For example, we use Severity and Priority for Issues, and it's very ease to edit the priority on the list for existing issues.
There are a number of steps required to do this for the custom severity field by way of having to use the edit function.
5 votes -
Add batch operations to search results
It would be great to be able to perform batch operations to search results.
5 votes -
Translate in french
For your French clients, translate in French.
5 votes -
PractiTest integration with Clubhouse
Have a 2 way integration with Clubhouse
5 votes -
Allow creating a test set based on requirements
Allow creating a test set based on the tests linked to one or more requirements. Example:
- search for all requirements with tag 'ABC'
- select all or some of the requirements
- click the 'Create Test Set' button/link above the resultsAll the tests linked to each checked requirement is put into the test set.
5 votes -
Different types of parameters
Currently we are running into a wall with re-usability. Either we don't use parameters,and there's no re-usability and alot of cloned code for one single functionality, or we use parameters and every test with "Call steps from another test" will have to set up all the parameters on test set run.
I propose a way to set parameter values on a test level. So when we use "Call steps from another test", all the parameters for that called test are possible to be set from within the current test, allowing for a lot more re-usability within tests. Not all should…
5 votes -
Step parameter in preconditions field
We would like to have step parameters in the preconditions field as well.
5 votes -
Add the ability to Create PractiTest Project via REST API
Example Use Case:
I'm a PractiTest Admin at my company. I want to Create
a new PractiTest project. However, I don't want to login to PractiTest UI.
Instead, I want to create the Project via cURL, or Postman, using Python/C#/Java, etc...5 votes -
The ability to sort filters by column on the "All Filters" page
The ability to sort filters by column on the "All Filters" page.
For instance, we currently have 9 pages of filters on PractiTest project, so it's difficult to find specific filters or categories on that page.5 votes -
Dynamic temporary filters (i.e. a search function), especially for the Test Library
Dynamic temporary filters (i.e. a search function), especially for the Test Library. "Goto <Thing>..." requires you to already know the ID of <Thing>, and can't be used to quickly find a related <Thing>
5 votes -
Need Better method to select the parent filter when creating a filter
Need better method to select the parent filter when creating a filter. Right now the entire filter tree(s) is shown as a dash-indented list, which requires quite a bit a scrolling to find the desired filter when the list is large.
5 votes -
Display the result of the last run
In order to start a new test run, it is important to know which issues were documented in the last run.
I would like to see the result field of the last run in the current run.
Maybe as a shadowed text in the result field or a link with a tooltip preview.5 votes -
Option to get the list of instances or runs from dashboard charts
When you click on a slice of a Pie Chart, or a column in a Bar Chart - if this is a chart of tests, test sets, requirements or issues, you'll get redirected to a filtered list related to this pie, or column.
It should also be possible to get with instances and runs.I understand it will look different, because in other cases the result looks like a filter and instances/runs don't have filters, but we still should get some sort of a list to work with.
This would be very useful
5 votes -
4 votes
-
Set a default time zone for the account
When new users are added they are initially set up with the time set to UTC (GMT). For most users this is not appropriate and they need to go into settings to set their own time zone. This even applies to users in the UK who need to select London in order to get the daylight saving time applied automatically in the summer. If we could have the facility for an administrator to set the default time zone for an account then most new users would be set up with the right time.
4 votes -
add the ability to view Requirements in Tree View from Test Library Traceability on click of Show Requirements
We use parents in our requirements so from Requirements I always view as a Tree. When I am in a test case and click the Traceability tab to link to a requirement and I use "Show Requirements" it only shows me a flat list in ID order so I have to maintain an XLS cheat sheet to add so I can see in tree view. It would be a GREAT enhancement to PractiTest to be able to choose Tree View from the Test Case Traceability tab on Show Requirements and save me a ton of time. Thanks :)
4 votes
- Don't see your idea?