613 results found
-
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
Ido Tandy
responded
-
search
I would like to search in a broader context, not just in a specific project, but search through all the projects
2 votesIdo Tandy
responded
-
Requirement adding/modification must be shown in the history tab of it
I think title explains it :)
1 voteIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
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 voteIdo Tandy
responded
-
1 voteIdo Tandy
responded
-
3 votesIdo Tandy
responded
-
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.
13 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
4 votesIdo Tandy
responded
-
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 voteIdo Tandy
responded
-
Add checking of spelling in all text fields - it is not applied in Description (General), Test Name.
7 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
Disable Step Outcome Options When Step is Being Added/Edited
When you add a new step to a Test Run, it's so easy to write out the Step, and then immediately click the outcome button. When you do this, everything that was typed was lost. Either make clicking the outcome button save any changes to a Step, or disable them so the user has to either accept the changes or discard them intentionally.
1 voteIdo Tandy
responded
-
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/number12 votesIdo Tandy
responded
-
add ability to drag and drop to tests
the user should have an ability to drag and drop his tests inside a filter in case he wants to arrange his tests in a prioritized order
3 votes -
Configuration of Tester
As an administrator of an account, when I make a new user group for Testers, I would like a feature where the tester is only able to see test sets and runs and not the library.
1 vote -
Give reviewer the option to give a comment
We want to able our MP give feedback about the tests.
the problem is the comment permission and the edit permission are the same one.0 votesIdo Tandy
responded
- Don't see your idea?