62 results found
-
Integrate practi test with footprint?
footprint is a ticketmenent system that we use and wanted to check if its possible to integrate with practitest
3 votesnot at this point
-
Comment for test rejection
When test status is changed from "Draft" to "To Repair" or "Obsolete" a comment should be attached explaining for the reason.
11 votesA comment can be added but we don’t think we will add the option to make it mandatory at this point
-
Add version control Tab
as a all in one tool (this my preferred approach...) i suggest to add a verion control tab which contain all the diffrent component verions (could be link to issues & tests too...) & will have option to attach related documents as how to install,release notes,fixed isuues reports & so on...it could be very helpful
4 votesOut of current scope of the tool
-
13 votes
Batch edit is planned only for the grid views
-
clone step
Create an option to clone an existing step usage: minor edit actions in steps.
3 votesNot planned
-
0 votes
-
ctrl+Z option isn't working if window minimized
Website should have the ability to let his users to undo/redo changes to the writen text
2 votesNot planned
-
Add pool of tests
Have a pool of tests / test sets wherein users can just select which one to add to their new project. This avoids exporting and importing tests / steps per project.
3 votesI’m declining this because it’s very close to ‘migrate tests between projects’:
http://practitest.uservoice.com/forums/27423-general/suggestions/398960-migrate-tests-between-projects?ref=title -
The size of the field should be flexible
If user write more then the size of the field
instead of sidepan he should have the ability to see fully what he wrote.Field should be set by styled by css min-height option
1 voteThis may be the case mostly for titles, and it will be handled as part of the new GUI project to be released in a couple of months
-
In some cases the expected result may be more then one
In does cases I'll be glad to add additional expected result to the same step
1 voteIt is correct that this may be the case, but in order to keep the system simple we choose to leave it as is. In any case you can define multiple options by using – or + or any other signs before the lines
-
Pre-populate test data from(linked) requirements data.
Pre-populate test data from(linked) requirements data.
Similar to the 'clone test' functionality but using a related requirement as the basis of the new test instead of another test. Particularly the requirement title - test title, requirement description - test description, as well as relevant fields (eg: requirement product component - test product component, etc etc). Perhaps the user could map custom fields together, eg: Map requirements field A to test field A (as long as they are the same type and with the same list values if a list)
0 votes -
Allow project admins to override the email notification policies for specific group(s) within a proj
Allow project admins to override the email notification policies for specific group(s) within a project
1 voteYou now have notification lists that you can add users to them, but we don’t intend to push emails to users who choose not to receive them.
-
2 votes
We are looking at keeping the workflow effective yet simple, and so we are not planning on adding this feature
-
Would like to validate that if a checkbox is selected Before closing (the issue), that a specific fi
Would like to validate that if a checkbox is selected Before closing (the issue), that a specific field (or fields) needs to be filled out.
1 voteWe are looking at keeping the functionality effective yet simple, and so we are not planning on adding this feature
-
"Root Cause " field should shld be added.
It will be good if "Issues" are supplemented by Root Cause for it. This will help in giving proper justification in while creating Metrics or say Client report.
2 votessince this can be achieve as a custom-field, I’m closing this request.
-
Ability to add different fields to different Issues types
There should be an option to have different fields for different issue's types (Task/Defect/Enhancement), since not all fields are relevant for each type.
4 votesAt this point we want to keep the product simple and so we are not planning on adding this feature.
-
Add WiKi Mechanism
A mechanism which will allow to add all kind of text elements, starting from general description, project description, defect severity and/or priority description, rule of thumb, and WE, would be extremely useful.
1 voteWe already support rich edit on description fields, and we don’t plan to support wiki pages. You can add links to wiki pages if needed.
-
5 votes
We do not plan to release PractiTest’s GUI in other languages. Languages are supported as users can work with any language they choose
-
work log
work log to monitor user time spent on testing & development. Get reports and connect it to client billing
3 votesWe don’t believe in creating a big brother kind of feature.
-
Export Tests in MS-Word format
Our testers and developers are used to reviewing tests in MS-Word format (not only in excel).
1 voteWe support to export entities in PDF format via the PRINT functionality
- Don't see your idea?