603 results found
-
4 votes
Ido 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
-
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.
14 votesIdo Tandy
responded
-
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
-
Next test should execute based upon filters and views.
When executing test cases, my testers should be able to filter and order them how they want to run them. So if I mix and match which tester is taking which test they should be able to filter by their name and test name and run the tests in that order. Right now it ignores the order and just goes to next test based upon how they where added to the test set.
4 votes -
I would like to be able to sort test cases alphabetically when adding them to a test set.
My test cases are named based upon area of application. So when adding to the test set I am manually sorting through 50+ test cases per section which I need in chronological order for execution. The ability to sort test cases alphanumerically when adding so I can add them in order by section would be huge for me and my team.
7 votes -
15 votesIdo Tandy
responded
- Don't see your idea?