284 results found
-
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 -
Search by Tc#
Search field should give results by Tc# ID
6 votesHi Siva,
Kindly note that we already have the option to search by ID within Test Library, Requirements, Test Sets & Runs and Issues.
Please see the ‘Goto Test’ option next to the blue button called ‘+New Test’.
Thanks
Christine -
Issues
Creating an issue in JIRA should take more than 1000 characters(This should include all steps from test Set in PractiTest)
6 votes -
Extend width of column on Requirements when adding from a Test script
Our Requirements all start with 'As a user I want to be able to...' and this is all that is shown as the column isnt wide enough to display the whole requirement. A hover over the requirement to display the full name would also resolve this issue.
6 votes -
See the status of an issue in Test Instance
When opening a test instance, we see the issues linked to it but not the status. Status is visible only when clicking on "To view other instances of this test, click here" that will show up duplicate info.
Suggestion to see the status directly in the test instance page.6 votes -
Be able to rename files directly when using "Press ctrl+v to paste"
When we paste a print screen as a file, the name is by default image.png. Sometimes we paste more then one and it would be good to be able to change the name to something more meaningful. Now we have to save it before loading it if we want to show a name for the file.
6 votesIt is now possible to rename attachments
-
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 -
5 votes
-
Exporting the STATS and GRAPHS in report format.
It will be great if STATS along with GRAPHS can be exported to some report format. This will help the user to generate his status report and share it amongst all stake -holder from where they can get an idea about overall status of project.
5 votes -
Expand the Name column on the 'show requirements' section of the Traceability Tab.
Currently when you click show requirements in the traceability tab on a test, the requirement name is cropped to 26 or so chars. This means if you have long requirement names it is difficult to identify the exact requirement unless you do it by ID. Would be good if this column/table was expanded across the screen.
5 votes -
5 votes
-
5 votes
-
adding attachmant to a test set
once you have a test set deriving from the main test, i need the ability to add an attachment to the test set.
you can add one to the main test but that won't help.5 votes -
make testing progress graph available on dashboard
There is a testing progress graph in the test library stats section showing tests passed, failed etc. over time. It would be really useful to have this type of graph available to add to the dashboard.
5 votesHi,
it is available now on dashboard. Find more information about that here:
https://www.practitest.com/help/reporting/dashboard-items/ -
Add Parameters columns to the "Test Instances" tables in the "Test Set"
Using parameters will save users test sets maintenance and duplications.
Problem is that in the current view – when running same test several times in a test set using different parameters , user has to manually enter each and every test to learn what are the specific parameters required for that specific test. Having the parameters shown in the "Test Instances" tables will solve the above issue (as user will have a clear view of the differences between the test instances),eliminate duplications of same tests run w/ same parameters and better filtering.5 votes -
Clone test in test editing and search results screen
How do you clone one test? Currently you have to (1) do a search, (2) identify the ID of the test, (3) then go to the test library, (4) navigate to the page where the test can be found and (5) clone the test. Please mind that step 4 may involve trying several pages before you hit the one where the test is listed. This is not very practical. Therefore I propose that a "Clone this test" link or button is added to two places:
1. The search results page and;
2. The General tab of the test editing screen.…
5 votes
- Don't see your idea?