592 results found
-
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
Ido 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.
16 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
-
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 -
allowing people (not just account owner) to export attachments
Currently only account owner can export attachments. This doesn't make sense. The system should allow more types of users to export attachments.
1 voteIdo Tandy
responded
-
Allow importing comments from spread sheet
Currently I can import all issues/defects to PractiTest but the comment column can't be imported. This is really a hassle. Comments are really important to track the progress of a defect. Highly suggest that this feature be developed!!
1 voteIdo Tandy
responded
-
Tests fields values should be saved. It is very annoying to fill the same values again and again every test we r running.
For every test we r running there r a lot of fields we need to fill- build, version, detected by….
We need to fill them manually every time. It is very annoying.
My suggestion that it will work like in QC – the fields value should be saved until I will fill something else.
It can save a lot of time and energy.1 voteIdo Tandy
responded
-
Add support for internal links
Currently when you add link as attachment to test or step it is always prefixed with "http://". I would like to have option to add internal links to the server locations so not http connection. Can you please remove adding http protocol in attachments?
6 votes -
Add Collision detect on Test edition
We have encountered situation when I have edited the Tests while my colleague had it open and editing. I have saved the changes first and when he saved his, mine were lost. It is quite a big problem in distributed large teams. Please take a look.
5 votes -
Synchronize PractiTest fields with JIRA fields (field mapping)
There are several fields in JIRA that we need to be reflected in PractiTest. In particular we use a fix in version field to associate releases in Jira and we need that field to be updated in the corresponding PractiTest ticket. Other fields such as priority should be mapped and synchronized.
We spend a copious amount of time with each release/sprint updating Requirements in PractiTest to reflect what the PMs have assigned for the current development cycle. Each time a requirement falls out of scope or a new on is added, we have to manually update PractiTest.
17 votes -
Need a duplicate test name warning
Need a warning when creating a test case if the name is already in use. This should be an option in settings, since I know some testers don't need this. However with my team, each name needs to be unique. So having a warning when we are duplicating a test name would be helpful.
5 votesIdo Tandy
responded
- Don't see your idea?