585 results found
-
Allow testers to add values
Admins are the only ones allowed to add values but sometimes they are unavailable. Not every tester has admin rights. To react flexibly to changing requirements, testers should be able to create values.
2 votes -
Add a link to the test via Test:ID
I'm missing the reference from Test Set to Test.
To see previous results of this Test, I have to go to the Test Library. A direct link would be more practical.
In the Test Instances list, there is a column Test:ID. When I go to the ID I want to jump to the Traceability tab of the Test.3 votes -
Add an import feature that imports the name and description of an external bug tracking issue
Currently we have to manually import the issue name and description and then Sync requirements and bug tracking issue.
A function that creates a new TestSet with the name and description fields imported from YouTrack or another bug tracker and then automatically linked to the Requirement would be great for productivity and streamlining!3 votes -
Allow the ability to reference existing PractiTest tests from the file for upload
For instances where you are uploading new test cases, it may be beneficial to have the ability to reference existing test cases, without the need to repeat these steps in the upload process. This may improve the maintainability of the Test Library.
1 vote -
Data Driven Testing
Allow custom user fields to be able to read from an external file. This should allow testing to be driven by the user data and hopefully increase the flexibility of the PractiTest.
1 vote -
Remove the need to save in order to add attachments
Remove the need to save in order to add attachments: "To add attachments to this step you need to save your test first."
3 votes -
Ability to Filter by Last Modified User
I'd like to see the ability to filter by last modified user. We have the ability to filter by last modified date, but I don't see a way to filter by last modified user.
1 vote -
API support for adding multiple test cases with a single call.
In consideration of the limitation of the number of calls that a user can make to the API, it would be wonderful if you could add support for the ability for a single API call to add multiple test cases into the test library with a single API call.
11 votes -
Customize the issue text
add the ability to create a template to the issue creation fields, texts. It would be really great to make a better transparency of the informations in it. Decide what information would you like to use automatically ..etc
1 vote -
Clone a step in a Test edition
Add the possibility to simply clone a step. for instance a 'clone step below' option that would copy/paste the test step fields and allows to edit them
1 vote -
Firecracker integration | add fields to configuration by XML properties and not only attributes
The idea is to be able to add custom modifications to the practitest configuration when using firecracker by using the XML properties in addition to current option by using XML attributes
13 votes -
Link Requirements via Batch Edit
When doing a batch Edit I would like to be able to link the requirement in the edit functionality. That will help streamline the process of tracing backwards and forwards, making managing these projects easier!
4 votes -
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 -
Allow updates to test cases via the API to function as expected.
Currently, if you attempt to update a test case that is currently in the test library, there are some fields that will not update. For example, if one attempts to update the folllowing fields:
"automated-test-info": {
"automated-test-design": "updatedDataHere"
}The API call returns a success, even though that data was never updated.
3 votes -
Test Library Filter - show number of test instances in View
When creating / editing a Test Library Filter, in the Custom Field area, I'd like to have Instance Count shown in the Filter View.
3 votes -
10 votes
-
Controlling "Notification List" with PractiTest API
In PractiTest API, "Notification List" of "Issuse" cannot be read and set.
Please take action to expand the scope of use of the PractiTest API.3 votes -
Extend Auto Filter to User Type of fields
Auto Filter is a really interesting feature, but is today limited to the "List" type, and some other types may be usable for this, such as "User" Type
I actually created a User Custom field (Reviewer) and it would be interesting to provide a filter to the different reviewers for their current list of review to do...It would be also interesting (but may be more complicated) to be able to generate Auto filter based on Cross Filter based on Auto filter...
Again, we have a referent on the requirements, (User custom field), and we could create auto filter with…
7 votes -
Add Ability to Convert Scripted Test into Exploratory
It would help if users could convert Scripted Tests into Exploratory. We only started using Exploratory tests in the past year so if we could convert Scripted tests into exploratory that would help.
4 votes -
Add the functionality for the list of pages to maintain the history of which page the user is currently on.
When you are in a specific Test Case, which happens to be on a page which is not the beginning page (Page 1), and you back out of that Test Case, it is very frustrating to be sent back to the very front of the list of pages instead of backing out to the page of Test Cases you were on before selecting one to view. Example: If you are on page 4 in a list of 1000 Test Cases (display 100 Test Cases per page set) and had been looking at one particular Test Case and then back out,…
3 votes
- Don't see your idea?