561 results found
-
Huge memory usage on Firefox 56 @Windows 7
I spotted Practitest is the reason of huge memory usage in FF browser with Windows 7. Usage is gradually increasing, especially when I open it in few tabs. It is laggy as well, but only within tabs where I have Practitest.
After closing tabs with Practitest memory is not released.
1 voteIdo Tandy responded
-
4 votes
-
Clicking on link to attachement opens a file instead of give choice open or download
In Firefox browser I spotted following situation - when I click on link to attachment, PractiTest opens a file instead of call browser's dialog with option to choice - open or download a file.
1 vote -
Add Status to Steps
It would be useful to add Status on steps so that a single test can be divided in different steps which should be evaluated singularly
3 votes
Christine
responded
Hi Fabrizio,
Thanks for your feature request.
Could you please clarify it?
Thanks in advance.
Best regards,
Christine -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
9 votes -
Link an Issue automatically as a failed Status of a Requirement.
Edith said to me: With regards to the Requirement, the status will be Failed, but the Issue will not be linked automatically. You can link it manually. I agree with you that the Issue should be linked automatically and will happy if you can add it as a feature request here.
1 vote -
search
I would like to search in a broader context, not just in a specific project, but search through all the projects
2 votes -
Requirement adding/modification must be shown in the history tab of it
I think title explains it :)
1 vote -
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 -
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 -
Dependencies on params
Can we have feature of having different expected results depending on chosen params? It would be very useful in cases where you have similar steps (driven by param) but different exepected results.
1 vote -
1 vote
-
1 vote
-
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 -
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 -
4 votes
-
Auto reassign defect to defect owner, when status change to fixed.
By change defect status to fixed,
system auto reassign defect to defect owner.
Once defect claim to fix, defect return to defect owner responsibility.1 vote -
Add checking of spelling in all text fields - it is not applied in Description (General), Test Name.
7 votes -
New Zap: create tasks on Kanbanery, Trello or other on Test Set creation
With new Zapier integration it would be great to add new trigger: when new Test Set is created it is send as a task to one of the boards like Kanbanery, Trello or other. Where to send can be based on List field in Test Set to allow flexibility.
2 votes
- Don't see your idea?