562 results found
-
Generate Reports from "Test sets & Runs"
Sometimes we need to create a fast report just for one Test and/or Test Set.
Would be great allow the generation of a Report directly after the execution of the test, without a filter in order to select just one Test, or Test Set, adding a report action into the Test Instances options or similar.
Regards
6 votes -
Add ability to Import Filters
It would be great to add the ability to import filters. I have lots of filters to groups tests together, the filters are then used when adding tests to TestSets. I have been migrating lots of tests and TestSets to Practitest and the lack of support for this this makes it very slow.
6 votes -
Detailed Report order by
We need to export Reports where the order is not always according to the ID (Mainly Detailed).
Would be great to add a "Order by" option at Filters, Reports configuration.
Thanks
6 votesIdo Tandy responded
-
Please improve Assembla integration
We purchased PractiTest with the assumption there is a one way integration with Assembla. We have had to turn this off as it creates more manual work for our team.
Please could you address:
-When Assembla ticket is updated so is PractiTest
-Show Issues that have been created and linked to Assembla6 votes -
Set requirement filters when importing from Jira
Set requirement filters when importing from Jira
The ability to set filters on requirements when importing from Jira. Currently a new requirement/s can be imported from jira. The requirement/s join a large list of requirements until the user selects and completes a batch edit on the requirement/s to assign filters. Using filters in the requirement tree allows for quick location of all requirements relating to the filter. I propose that practi-test gives you the option to set the filters when importing. improve the import screen to provide a screen similar to the batch edit when importing allowing the user to…6 votes -
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 -
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 -
Better filtering in search functionality - per specific fields in the results.
As a user, I'd like to be able to see the results of my search and not "guess" in which field my keyword was found. For example, if I search for a certain keyword in a Test Description, I'll get the Tests in which this keyword appears in Title, Description, and all kinds of system/custom fields. Sometimes I need to check manually more than 50 Tests and this is quite inconvenient.
Another scenario would be - if I search for the keyword that would appear in Title, I also get the results of all Tests in which this keyword appears…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 -
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
- Don't see your idea?