580 results found
-
Create the ability to add multiple instances of a test case to a test set
When creating a manual parameterised test set, multiple instances of a test case need to be added. At present this needs to be done individually. It is suggested that there is an option to 'Add multiple instances' to the dropdown menu by the '+ Add selected tests' (underneath Add all test in view). This triggers an input box to appear where a two digit number can be entered, and all test cases ticked will be added that number of times
16 votes -
In The Task Board As Well As Filtering by Person why not filter by TestSet Filter & Test Filter -
That way you can multi purpose it for multiple test runs.
15 votes -
Provide the option for the Parameter checkbox to be populated by default
When adding in the parameters there is a checkbox that is unpopulated by default. To enter a value in the parameter field, this needs to be checked.
Although in isolation it is a small thing to have to click the checkbox each time, it soon builds to a significant irritation when preparing multiple test cases15 votes -
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 votes -
Add "Tags" column to Test Library available columns
We are struggling with getting the result we are after using Search even with all the new filtering options available. We have tried filters and reports but they are all IS or IS NOT vs Contains. In a support chat, using Tags was recommended to us and we are trying it but we cannot display the "Tags" column to the Test Library view; it's not available. This would be incredibly helpful to us if this were added. Thank you.
14 votes -
13 votes
-
Adding more fields to panel with PractiTest data in Jira ticket
I'd like to see more columns displayed in JIRA when the linked Tests from PractiTest are displayed - or Steps of a run if it's a bug.
For example, for linked Tests:
- Assigned to
- Tester (of a last run)
For bugs
- Priority (if it's different in PractiTest)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 -
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 -
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 -
Reorder Test Cases in Test Library & preserve the same order when generating the reports.
The user should able to reorder the Test Cases for a project in the Test Library.
My requirement:
I have 3 tests,
Test 1, Test 2, Test 3They are created in some order say, Test 1, Test 2 , & then Test 3,
But my Test 3 is the continuation of Test 1, what I actually meant is Test 3 will start from where I ended in Test 1.
So, I want my tests to be in the below order:
Test 1
Test 3
Test 2I tried several ways to reorder the tests but nothing worked.
Some of…
12 votes -
Improve multi-level bullet list formatting in rich text editor
Currently, rich text editor poorly supports multi-level bullet points, in addition, the formatting looks completely different when creating and when running a test in a test set: making a multi-level list a single-level list
12 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 -
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 -
When cloning a new project, add an option to clone filters
Right now when you try to clone a project from Account settings, you have 4 options:
clone fields, clone users, clone user groups, clone integration settings.It would be also very useful to clone filters. Probably should be related to "clone fields" option
11 votes -
API support for adding multiple test cases with a single call.
In consideration of the limitation of the number of calls that a user can make to the API, it would be wonderful if you could add support for the ability for a single API call to add multiple test cases into the test library with a single API call.
11 votes -
Task Board - Customize with chosen fields
I would appreciate to be able to choose the fields shown for all tasks. For exemple, to be able to see the Priority or other chosen fields.
10 votes -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
10 votes -
Make it possible to change the 'test set' on a run test instance
Add the ability to change the 'test set' that an instance of a test is in, once it has been run
We have some test instances which have been added & run in the wrong test set. We want to move the run instance to a different test set, , for reporting purposes., but not loose the results and run history10 votes -
Upload a screenshot simply by pasting it to the step screen / upload screen
This will make this process more productive and easy.
Same as you do in JIRA tickets - pasting a screenshot from clipboard within the create screen, automatically uploads it to the ticket.10 votes
- Don't see your idea?