601 results found
-
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 -
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 votes
Ido Tandy
responded
-
Support creating filters on 'Instances'
Currently filter Types supported: Issue, Test, TestSet, Requirement. Can you also please add 'Instance' to the filter type support. We include quite a few custom fields on our instances and it would be nice to create a filter using these custom fields for all the instances.
14 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
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 -
Add API to upload .trx files
standard .net test runners can produce .trx files e.g.
vstest.console.exe /logger:trx foo.dll
dotnet vstest --logger:trx foo.dll
These are just XML files. We currently have to parse these xml files and perform hundreds of individual uploads, waiting 60 seconds every time the server throttles with HTTP 429
It would be better if .trx files could just be uploaded to practitest to produce a run of a test set, and the parsing was done on the server.
13 votes -
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
13 votes -
13 votesIdo Tandy
responded
-
Add "Automation" checkbox to filters
It is not currently possible to filter test cases based on the "Automation" checkbox on the test case. Please add the ability to filter test cases by that element.
13 votesIdo Tandy
responded
-
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 -
Generating Test Cases From Jira into Requirements
The ability to go into the 'Requirements' section in PractiTest and have an option to 'Generate From Jira'. This would grab an attachment (Excel, CSV etc) from the Jira ticket, import it into PractiTest, generate a test case from it and link it to the requirement
13 votesIdo Tandy
responded
-
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 -
Width of Test Instance Name column in a Test Set is defined by the longest Name
Currently, when you enter an existing test set, the Test Instance Name column is very narrow, cutting off most text of the test name. I constantly have to increase the Test Instance Name column EVERY time I reload the test set page. It's very annoying. At the very least, it would be nice if the column width would be remembered while I'm actively so I don't have to constantly increase it.
13 votesIdo Tandy
responded
-
Clone parent folder structure to child project if does not exist
As a practitest user, I want to clone my test cases and attributes, specifically folder location.
Acceptance Criteria:
If the folder structure does not exist, create the folder directory (a unix example would be mkdir -p /root/parent/leaf where if only /root exists, the rest of the directory is created.
Provide an option not to create and place in the folder structure13 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 votesIdo Tandy
responded
-
Add step numbers on to Step when re ordering
When clicking on Reorder Steps for a Test - the steps appear as a long list without the Step Number next to them. This makes it hard for the User to know which Step to swap around. Please could we add the Step Number to the title of the Step.
12 votesThe reordering feature will be enhanced in the new Test Form, allowing you to easily reorder items within the Steps tab using drag-and-drop functionality. We're actively working on this, and it will be released in the coming months.
-
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 -
Import via Excel should have an update option as well not only to create new
Currently export a Test or Requirement -- creates new records. User should be able to update via excel for the records that is already existing using Entity ID
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
- Don't see your idea?