46 results found
-
Firecracker integration | add fields to configuration by XML properties and not only attributes
The idea is to be able to add custom modifications to the practitest configuration when using firecracker by using the XML properties in addition to current option by using XML attributes
13 votes -
Give users the ability to add custom fields at Test Step Level.
You should give the users to add fields at test step level.
They should be allowed to Add things like Test Data for a particular step like Large Queries it it. For us the Test Precondition or Test Description or Test Name cannot be used for that purpose.
13 votes -
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 votes -
Give permissions for individual fields to certain users
I want to be able to give certain team members permission to edit picklists on only some fields ? eg) we have a custom field 'Run on Build' that we want all team members to be able to add values to, but don't want them to be able to have general access to edit values of all other fields
11 votes -
Integration with Katalon Studio
I am exploring the open source Automation tool Katalon Studio for automating test cases for mobile and web applications. I would greatly appreciate if Practitest can provide 2 way integration with this tool.
11 votes -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
10 votes -
9 votes
-
Add defect search functionality to Add Existing Issue to Test flow
When linking a defect to an executed (failed) test, you do not always remember the defect ID. This is an annoying way to currently link defects.
On the link existing issue step, it would help greatly if we could bring up a list of all defects and be able to sort and search them by date/title/description.8 votes -
Add the ability to add custom fields and modify columns for Test Instances Run History
Right now, we only have:
- "Run date"
- "Status"
- "Tester"whenever we look at the test run history for instances. It'd be neat to have the option to add custom fields so we can better track previous runs.
For example: I want to be able to add "Commit hash" and "branch" to test instances run history so I can see the last GitHub commit that was tested.
7 votes -
Filters by users which are no longer part of this project
Filters by users which are no longer part of this project
7 votes -
Need the ability to Create/Read/Update/Delete filters through the API
Need the ability to Create/Read/Update/Delete filters through the API
6 votes -
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
6 votes -
Create an option in the report center sector for generating a report with our companies logo as default at the right top corner
So when i go to the Report Center that it will be possible to upload our logo in a report.
6 votes -
Improve functionality of editing and updating tests from runs
I find the current functionality of updating your test while executing it a bit clunky. Now I do understand that it is meant for small changes where big test overhauls should only be done in the test Steps tab but still I think there are some improvements to be made.
1) If a step has been edited during a run, PT should ask the user if he wishes to 'Update Original test' before navigating away from the page. I find that I often update a step but forget to click the button to update the test at the end.
2)…4 votes -
Add status for users in user setup
In current version the basis for access and invoicing is users defined in the user setup. In a project when testers are involved now and then, the administrator must manually remove the users to have control of the costs. When the users is supposed to do testing activities later, the admin must then manually add all users. This is very time consuming in big projects. However, it should be possible to set a user inactive by changing a status that will prevent the user from having access to the project and also will exclude this user from the payment.
4 votes -
Set a default time zone for the account
When new users are added they are initially set up with the time set to UTC (GMT). For most users this is not appropriate and they need to go into settings to set their own time zone. This even applies to users in the UK who need to select London in order to get the daylight saving time applied automatically in the summer. If we could have the facility for an administrator to set the default time zone for an account then most new users would be set up with the right time.
4 votes -
Non-critical Step
Add ability to define a step as a non-critical step, and thus a failure on this step would not fail the test.
3 votes -
Export Project history
It would be nice to have an option to export Project History as an excel file, according to the filtered results.
3 votes -
Enhance the Export All Users (report/download) to include last log on date of each user. This report can be found on the Manage Users tab.
Add last log on by each user to the Export All Users report/download report under Manage All users. Will help to manage both active and inactive users.
3 votes -
An ability to link existing issue to the Fast Run results
Sometimes we fail many instance in our Test Set at once due to a serious bugs that affects them all.
Fast Run is a good option to Fail many instances in one go, but then we need to attach a link to existing bug to each of the runs created.3 votes
- Don't see your idea?