601 results found
-
Allow parameters to pull values from custom fields or value lists
Parameters and permutations are great, but frustratingly separate. It would be good to allow parameters to use values defined in a list for a custom field, or a new artifact for this purpose. Maybe they could also be passed inline with the parameter instantiation:
{{myParam:[1,2,4,8]}}6 votes -
Permutation of a test set
While creating a Permutation of a test set, after selecting all the field values of the new permutation and clicking on the Next button. On the next page, I get a list of all permutations which can only be selected but not editable. It will be good if the user can also edit it and give a Test Set name whatever suits. Because this feature is not available currently, I have to create the Test Set first and then edit it to change the test set name which suits my requirements.
6 votes -
When filter with date type field, user can select today() instead of select specific date on calendar.
I need to create a filter to collect all test result older than 4 days. Tried to filter with Last Run field but I can't see suitable operator. It must be good if we can use today() instead of select specific date on calendar or there is operator such as: Before the last X days...
6 votes -
Add tables support
add an option to create, and modify a table in a test's description, expected results and actual results.
and also to paste a table directly to any of these fields.
6 votes -
Calculate a field based on the values of other fields
I am imagining the following to avoid using the green monster.
Issue form with the following fields:
• Reach (value dropdown 20)
• Impact(value dropdown 0.5)
• Confidence (value dropdown 100)
• Estimate (value dropdown 10)
• Score (calculation: 200.5100/10=100 from the above fields)6 votes
Ido Tandy
responded
-
Print entities with images
With the "Print" feature, we can print or create a pdf file of selected items like requirements.
It would be nice if the attached images are included in the pdf, not a link or the name of the image.6 votes -
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
6 votes -
Need the ability to Create/Read/Update/Delete filters through the API
Need the ability to Create/Read/Update/Delete filters through the API
6 votes -
Mapping Jira issue type with Practitest field
When we sync Jira issue to Practitest - whether it's going to be an issue, or a requirement - we can only see which type it is in Jira in Description field.
If we could map it to custom field in Practitest, it will help us organizing them in Practitest per issue types, for example, with Filters.For example, we sync both Stories and Epics as Requirements, I want to build a filter (autofilter for example) which shows which Requirements are Stories and which are Epics.
6 votes -
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 -
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 votesIdo Tandy
responded
-
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 votesIdo 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
- Don't see your idea?