613 results found
-
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 -
option for cloning traceability (linking between requirements and tests)
Whenever I need to clone Tests or Requirements I have to do double work of adding back linking between entities an option for cloning not only attachments but also linking between Requirements and Tests would help.
26 votes -
option for adding new values to custom fields without overwriting old values
For batch editing of Tests/Requirements I need to add values to my custom fields, but they get overwritten with the new value and information gets lost unfortunately!
An option for adding values but preserving old values would help a lot.21 votes -
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 -
Add the arrow navigation controls for pages of Test Instances under Test Sets and Run to the bottom of the lists of Test Instances
Add the navigation controls for pages of Test Instance under Test Sets and Run to the bottom of the lists of Test Instances...I am referring to the forward, backward, beginning of file and end of file arrows (that are almost missed being so small) which are next to the drop down for number of Test Instances shown on a page. It is frustrating to scroll to the bottom of a 100 Test Instance list and need to go to the next page only to have to scroll back to the top to access the controls to go to the next…
3 votes -
Allow the ability to search for a specific Test:ID number in the Search available in the Top Main Menu Bar.
If you have a large number of tests in your Library and you are wanting to edit or revise a specific Test ID, it would be more efficient to allow the searching for the Test:ID rather than having to note details from the title of the test and search against that...easier and quicker to remember a number...
3 votes -
Can we specify Test Results file with xBot script run?
We have a field "Results Path" under Automation info tab while adding an xBot Test Case from PractiTest. Can we have a field to specify the Result file to upload during script run?
3 votes -
Tables, Font sizes, inline attachments in Test cases description and test steps.
The following issues/suggestions related to description and test steps of a testcase(test library, requirement & test set/test execution):
1) In my organization we use JIRA and most of the stories contain data in tables with many rows and columns . When testcase( &requirement) is created from JIRA into PractiTest, data in table is displayed in between || in PractiTest. When the EYE icon in PractiTest, Table is not displayed. It will be great if we can at least display the data in table format when EYE icon is displayed.
2) When we contacted Joel on the help chat, he showed…
3 votes -
API instance run count
For a particular Run Instance, I'd like to get number of runs for that instance.
0 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
-
Provide Ability to Require Guide Points in Exploratory Testing
When creating Exploratory Tests, we would like the ability to make Guide Points a required field. Sometimes users may only fill out the Test Charter when it would be beneficial to include Guide Points.
1 vote
- Don't see your idea?