316 results found
-
7 votes
-
enhance 2 way integration with Jira
It would be utmost useful to be able to see any comments devs make in Jira on a bug so that Qa can see it in Practitest. Not just name, description and status.
7 votesDone (for Jira Cloud + Jira Server)
-
Please provide 'Import test' feature available within a Test set.
Currently, we import test cases and test cases are uploaded in test library then, when we create a test set then we need to find out our test cases and link with the test set.
It's little tedious task to find out test cases when there are more than 100 and add to test set.
Please add import test feature within a test set.7 votesThis was released and currently you can add a number of test from the test library into a number of Test Sets at the same time.
-
Keyboard shortcuts support
It would be great if you add keyboard shortcuts support for navigation/editing (like in gmail for instance).
6 votesHi,
Please note that this feature request is completed.
Best regards,
PT Team -
Open API
have Open API for 3-rd party software to communicate with PractiTest
6 votes -
Test Plan-Time field
Customer Request: Add a test time system field, so when u look on a test view, you can see the plan time for running this whole view.
6 votes -
Filters on Custom Views for Requirements
It would be very useful if Custom Views on Requirements could include filters based on field values as for Items and Tests.
E.g. being able to get the requirements applicable to a particular domain that are testable but have not got any associated tests yet.
6 votes -
Filter in adding tests to test sets
In Creating new test set indication is needed which tests are already in that test set. In order to see clear coverage of some feature and be sure that nothing was forgotten.
6 votes -
Support advance search on view query
Ability to create a filter on view manager with only a part of the string
6 votes -
Linking external id (Requirement id) to test library and instances
Linking external id (Requirement id) to test library and instances
6 votes -
Maintain sort and filter on grid
If I have filtered/sorted a grid (ie issues), then click an item (ie an issue) in that grid, then return to the grid, the sort/filter is reset to default. That means I have to reset the sort/filter every time I look at an item on a grid. The filter/sort confiugration should be maintained for each grid during a session (at least).
6 votes -
Improve Jira Integration
We think the following would improve the Jira integration tremendously if implemented:
- In the auto generated issue description (when clicking fail & issue) include the expected resultMake linking existing issues less cumbersome. At the moment users need to:
1) Add the ID
2) Navigate to the issue
3) Edit it with the pt_id
4) refresh in the step
This should all ideally done by PT (itself + the Jira plugin)Full 2 way integration: add a tab in Jira that lists hyperlinks of all the linked PT tests (other tools such as QMetry do this)
6 votes -
6 votes
Hi,
Please see our help page explaining the integration with GitHub:
https://www.practitest.com/help/integrations/github/ -
Be able to insert repeatable/shared steps into a test case, or insert one test into another.
For example, many of my tests include the same first three steps. It would be very convenient if I could create a test or shared steps that have those three steps and then insert them into each test. This way, if those steps changes, I would only need to edit them once, instead of for each test.
6 votesHi,
Please note that we have added the features that were requested in this post.
Feature “Call to Test” allows to call to test steps from another test case when creating or editing a test case. Find more information here: https://www.practitest.com/help/tests/call-to-test/
Feature “Step Parameters” allows to set different parameters for test cases. Find more information here:
https://www.practitest.com/help/tests/step-parameters/ -
Add a history to Test Sets
I need to be able to see if a tester has deleted, added, or reordered test instances to a test set.
6 votes -
Propagate Test Set Fields to the Test Case and Related Issues Instances
Example: System Version (1.0, 2.0, 3.0) custom field added to the test set. If I want to compare the results of all test instances for each Test Set execution based on this field, I need to have that value that I would enter into the Test Set automatically populate any tests in the set, and any issues that are created in the execution. Right now you have to bulk change the test instances with the System Version in order for them to show up in dashboards.
6 votesHi all,
Putting this request to completed since there is no real need to propagate these fields as now you can generate reports and dashboard graphs with taking values from other entities as Test or Test Set.
Thanks,
Yaniv -
add rich formatting in steps
add rich formatting in steps, it is necessary to tap validations
6 votesHi,
Please note that this feature request is completed.
See more information here (https://www.practitest.com/updates/2017/07/moving-to-markdown/).
Best regards,
Christine -
Add JIRA syncing of story status
Make it possible to show the JIRA status of a story which was imported using the JIRA plugin. for example, if a story is accepted on JIRA, we should see this updated in the practitest requirement
6 votesIt is possible to see the Jira (External) Status in PT.
-
Params drop-down
Usually when we use Paramters we already have some set of possibilities in our minds. It would be perfect to have possibility of using drop-down list of possible parameters for given Instance.
6 votes -
Filter to get the Tests linked to a Requirement (N requirements)
We can already see that information through the Traceabilty, but currently I think that It's not possible to create a filter in order to get all the tests linked to a specific/s Requirement/s (for example, in order to create Test Sets for specifics requirements).
We need to create an extra field with a list of requirements (manually added), when this information already exists and we have duplicate information.
I think that the creation of tests by requirements is a very common way of work, and it's not easy to get right now.
Thanks.
6 votesHi,
Thanks for your patience.
Kindly note that we have recently added the ability to create filters with ‘Linked tests’, ‘Linked requirements’ and ‘Linked issues’ as available fields to filter by within the Test Library and the Requirements module.
Thus you will always know what entities linked to your requirements and tests (see a few screenshots attached).
Thanks for improving PractiTest.
Best regards,
Yaniv
- Don't see your idea?