603 results found
-
Add new value to standard or custom fields via API
In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.
At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.
17 votes -
create a way to filter/report on issue status history
I am looking for an easy way to report on the status history of an issue. As it is now, I can only easily filter on current status when I create reports/filters. I am looking for a way to find issues that were ever in rejected status or were at one time set to "reopened" without having to manually read the history of every issue.
1 vote -
Import via Excel should have an update option as well not only to create new
Currently export a Test or Requirement -- creates new records. User should be able to update via excel for the records that is already existing using Entity ID
11 votes -
Only display step information that failed when creating a bug using JIRA integration , do not include all steps
When creating a bug using JIRA integration currently all steps in the test are pased into the jira description. It would make more sense to only paste the step that failed and the results from that step. this would give the user the information on the actual issue and reduce the amount of editing currently required using jira integration
3 votes -
Create Pie Chart with group of values
I would be interested by having a way to group different values of a field used to create a pie chart in 1 "super value"
To give an example:
For the Requirement items, I would like to have a pie with only 2 values :
- Not Covered
- Covered
As of today, we have: Not Covered, No Run, Passed, Failed...
I would like to be able to present a dashboard to my manager with the value "Covered" including all the values except Not Covered and Not Covered.3 votes -
Adding a What Change options to Reports
Creating a daily report to see what test cases have been changed, so that we can keep our testsets up to date with the new changes in the library.
adding what changed as a report option would simplify the work flow of opening up Project History
1 vote -
We would love the ability to run cURL commands form within Practitest so that we can launch our automation from within a test run.
We would love the ability to run cURL commands form within Practitest so that we can launch our automation from within a test run.
3 votes -
Update the call on issue creation in YouTrack synchronization
PractiTest supports a synchronization with YouTrack, especially for the bug creation (from PractiTest to YouTrack).
There is currently no way to change the call on PractiTest test side.
YouTrack proposes a feature to update object on Event, such as issue creation.
I would need to identify that the issue is coming from PractiTest, and then I would be able to make my change on YouTrack side.The signature includes 2 fields, which are not filled today: externalId and externalUrl, which shall be filled in my opinion when the issue is created from an external tool.
Could you please fill at…
3 votes -
Email notification to cover the changes done at Step description and expected result level
Currently, test modification email notification does not inform the Test admin about the exact changes done at step description and step expected result. This is must needed request . Even Project history does not keep the record of test modification at the level of Steps description and Step expected result
3 votes -
Create the ability to link issues
This was suggested earlier and set to completed, but from the comments it seems to have been completed on the Call to Test feature, not linking issues.
There is the ability to see related issues within PractiTest but not link them. This would be a useful feature to highlight related issues, and generally used where one is superseded by another9 votes -
Create the ability to add multiple instances of a test case to a test set
When creating a manual parameterised test set, multiple instances of a test case need to be added. At present this needs to be done individually. It is suggested that there is an option to 'Add multiple instances' to the dropdown menu by the '+ Add selected tests' (underneath Add all test in view). This triggers an input box to appear where a two digit number can be entered, and all test cases ticked will be added that number of times
13 votes -
Create the ability to import parameters
Rather than having to copy and paste parameters in from a datasheet, it would be good if we could map the parameters for multiple instances of a test case to a datasheet and import them
eg Select 10 instances of a test case, click an 'bulk update parameter' button or similar, which can then map to an excel datasheet22 votes -
Provide the option for the Parameter checkbox to be populated by default
When adding in the parameters there is a checkbox that is unpopulated by default. To enter a value in the parameter field, this needs to be checked.
Although in isolation it is a small thing to have to click the checkbox each time, it soon builds to a significant irritation when preparing multiple test cases15 votes -
Upload a screenshot simply by pasting it to the step screen / upload screen
This will make this process more productive and easy.
Same as you do in JIRA tickets - pasting a screenshot from clipboard within the create screen, automatically uploads it to the ticket.7 votes -
Add descriptions to the fields (custom or System)
When we create custom fields or modify a System field, it would be great to add a Description that we could then view as a tool tip in the entity. This would give more context around the importance or purpose of the field and would give testers a more compelling reason for filling it in.
Right now, we document the purpose and description of each of the fields and filters we have set up in a wiki page. It would be nice to be able to manage this directly from PractiTest.
1 vote -
Request for New Features in Jira View and Integration?
Hello, Can we request to remove text " PractiTest: Linked Results (Runs)" from the view of the main screen and omit from issue type which are not integrated in setting of the project ? We just want to see it on the right pane which is ok
Is there any possibility to add this feature?
Thanks,
Faisal1 vote -
Link an issue to a test case via API
While creation of an issue via API, I would like to link it to a test case which failed.
1 vote -
Create multiple issues by sending one request
I see it is possible to create one issue only by sending one request. I would like to create multiple issues in one request.
2 votes -
user group
Alphabetize user names in groups. Searching for a particular user would be much easier.
1 vote -
Upload requirement multiple times without duplicating
Ability to upload requirement without duplicating, but the changes in the new upload are made on the requirement. History is captured to track what changed, when, how and by whom.
1 vote
- Don't see your idea?