585 results found
-
When cloning project, separate between cloning fields and their values
Right now when I, account owner, am cloning a project, I only have permission "Clone custom and system fields", and the values also are being cloned.
I'd like to have an option to leave the values empty, if they're not related to the new project.
Like two different options:
"Clone custom and system fields"
"Clone values in fields"Similar to what you have for user groups:
"Clone groups and Issue workflow
Clone Users in Cloned groups"6 votes -
Copy custom fields with values from one project to another
Sometimes, as an account owner, I need to add a new custom field to every project. The behavior of this custom field is the same and so are its values, it doesn't differ between projects. Right now I need to recreate such a custom field manually, no matter how many values it has.
It would be much easier if there would be an option to copy the custom field from another project, with all the values.6 votes -
Mandate screenshot or attachments to be saved during test step exeuction
The ability to mandate in the test library, at test step level, that a screenshot or attachment must be saved at the step during exeuction.
During execution it should not be possible to proceed if the screnshot or attachment has not been added.
This is crucial for compliance where test evidence is checked by auditors.6 votes -
Ability to link an issue to multiple test executions
Sometimes when a specific bug is found, we understand due to a nature of our testing that it will be found in other test runs as well, and would like to update these runs in batch.
For example, if it's the same test, we'd like to be able to link this bug to the same step in the run in all the existing runs.6 votes -
Fix test set to use full width of any monitor (as it did before new UI)
Lots of people on IT uses large width monitors, and before the new UI was possible to really take advantage of it on test set, considering number of columns and wide data.
After the new UI the test set displays on the middle of my monitor, with two giant empty blocks on the sizes (left and right), and now my columns are smaller and I'm no longer able to read all my information. It got worse! Very bad!
Please, please, fix that ASAP!
6 votes -
add the ability to use multi-lists as a child of a linked list
Currently, linked lists only support standard lists as the child item. There should be an option to add both lists types as the child of a linked list.
5 votes -
Add bulk of test to a requirement tractability
in the same mechanize as add test to a test set, instead of picking them one by one like today
5 votes
Ido Tandy
responded
-
to identify updates on requirements
I would like to be able to recognize updates when I am uploading requirements. So when I have uploaded for instance 10 requirements to Practitest by using a 1.0 version of an excel, and I update the document and do a re-upload of for instance a 1.1 version. I would want Practitest to recognize existing requirements and identify changed and new requirements. This would enable me to see what testcases are affected (and should be modified/ deleted) and what requirements need new testcases.
5 votes -
Option to remove 'title' field for every test step
Although a small issue, this becomes irritating when we are creating or importing dozens of test cases.
The 'step title' field (it doesn't actually have a name) adds an extra step which seems unnecessary. In my experience it is rare to need to title each and every test step. Please could you have the more standard Description-Expected Result only format when creating test steps?5 votes -
5 votes
-
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 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
Add batch operations to search results
It would be great to be able to perform batch operations to search results.
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
- Don't see your idea?