561 results found
-
Project Overview Summary
There should be a project summary section on Summary Home page, which Overview the whole project, such as Project Name, Project Start date, Project End Date, Estimates Time (All Runs), Actual TIme (All Runs), Assigned to, Project Closure Notes / Comments, etc.
3 votesIdo Tandy responded
-
4 votes
-
Implement parameters into test names
I use parameters both to allow for flexible test reuse but also to help identify which portion of an app I'm testing, when different sections are similar. In some cases, this would allow me to use a parameter in the test name instead of in every step of a test.
It would also help with JIRA integrations where the specific section (defined as a parameter in the title) would automatically be added to the issue ticket summary field during the 'Fail & Issue' process.
14 votes -
Ability to get the detail of a comment by API or Webhook
It would be nice if we can get the detail of a comment by API or Webhook.
Right now it seems possible to get the update on a comment by Webhook, but not in detail.7 votes -
Able to use Markdown in comment or any text fields
It would be nice if we can use Markdown in comment or any text fields.
4 votes -
Traceability into Batch Edit
Include in Batch Edit for Test Library the possibility to add a requirement to several Tests at the same time.
On the same way, Include in Batch Edit for Requirements the possibility to add a Test to several requirements at the same time.
Currently it has to be done one by one.
3 votes -
Change Run Status to RUNNING for a Test set when one of its Instance is at RUNNING
On the Test sets overview it is not possible to see if tests are automatically running. It would be nice to have the Run Statuts of a Test set at RUNNING when one of its Instance is at RUNNING.
7 votes -
Import Jira requirement ticket with all it's sub-tickets
In order to provide better coverage of the specifications I do propose to implement:
- Tree-like import that means importing parent and subtickets;
- Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
- Add system field "Traceability" for requirements that will reflect clickable test IDs;
If the solution will be implemented it will simplify test covering process and test covering tracking process;
28 votes -
Allow user to change order of filters
Currently the filters all display alphabetically unfortunately we don't always work this way, It would be helpful to allow you to set the order manually or just use drag and drop to organize them
4 votes -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
9 votes -
Edit custom fields on filtered lists
It would be nice to be able to edit custom fields on filtered lists, as you can with the default system fields. For example, we use Severity and Priority for Issues, and it's very ease to edit the priority on the list for existing issues.
There are a number of steps required to do this for the custom severity field by way of having to use the edit function.
5 votes -
Please make it possible to update a Run of after each step via the API, rather than just at the end.
I have tests with many, many steps in them. Some of the steps take many minutes to complete. It would be very useful if I could update the execution status/results/attachments of particular steps via the API.
Possibly via a PUT request to the appropriate step instance, or maybe to the Run instance.
6 votes -
Enable add a screenshot embedded in the text instead of as an attachment
this will be useful when we would like to show what is the expected results for example or if there is an issue just take a screenshot and show it to our development team
instead of having to save the screenshot and adding it to the issue ...this will be useful also for showing screenshots of the tests and expected results
Thanks.
5 votes -
show/print issue title & ID, for tests with linked issues
I would like to be able to see (and report on) the issue titles and the issue ID number, for issues that are linked to tests (this is especially important for projects that do not have a 2 way issue integration)
If just the issue ID is shown, it means always having to spend time looking up what that issue is.
It is also important to be able to export & print a list of this information and would also be useful to be able to create a filter which allows it to be shown on dashboards.3 votes -
Allow report generation by test set ID
There is currently no API to generate report by test set ID. Generate report by test set ID would greatly enhance our automation process
22 votes -
4 votes
-
Add Test Description on Test Set run view
We discussed it with Joel during his visit in Cambridge, UK. It would be beneficial to see Test Description on Test Set Run view (above the steps). Test Descrption contains essential test information and having them visible on this screen would help to understand the context of the steps without need to click multiple times to see it. Hoovering in upper right corner shows that, however it is unreadable in some cases.
3 votes -
Allow the account admin the ability to create reports/dashboards across projects.
Dashboards and reports should be able to be created to report on multiple projects. If an organization is able to report on all the activity within Practitest, it will allow Executive Leadership the ability to see the entire workload of what is being processed via Practitest.
It really will show the immense activity accomplished during testing as a whole.
10 votes -
Add the ability to edit the default JIRA ticket text
After clicking 'Fail & Issue', a JIRA ticket is created with the 'Summary' field populated automatically with "Bug reported from test: " followed by the test name. This can make the name unnecessarily long or potentially not follow existing naming conventions for a particular JIRA project. It would be nice to set a custom value for this pre-populated text, instead of editing it manually each time. For example, I use "PT Report: " as an abbreviated version. A company might want an even shorter code.
It might also be a handy feature to choose to put this text at the…
5 votes -
Improve parameter handling
Sometimes we include the same test case a couple of times in one test set, but with different parameters. Unfortunately now we must edit those parameters one by one - and this is a lot of clicking.
I can see 2 solutions:
1) Allow modifying parameters directly in test set table
2) On parameters screen differentiate parameters by test case instance/number9 votes
- Don't see your idea?