544 results found
-
Upload attachments directly to Jira issues created from PractiTest
It would be nice to have the option to directly add attachments when creating an issue using the Jira integration.
In our case issues created require a certain backup to be attached, right now testers always have to open the created issue in Jira afterwards to add this. This would be made easier if attachments could be uploaded directly when creating an issue from PractiTest.
Possibly even uploading attachments from the test run as well to provide some more background information / possible ease of use.
3 votes -
Should be able to download attachments per test
For auditing purposes would be nice to be able to download the screen shots or attachments for each test.
This way i can send to the auditors during audit season
3 votes -
Allow either cloning or sharing custom fields to step parameters
Mostly custom fields would be used as step parameters. It would be great if we can allow cloning or sharing or copying custom fields to step parameters
3 votes -
Instances : Assigned for filter to be made available
Allow users to create a filter in the Test Sets & Runs module that will only show test sets with instances assigned to them.
This way if a tester has been assigned multiple test instances across different test sets, he can see all of them at one shot instead of going through each test set to find what's allocated to him.
3 votes -
Add a way to Batch Edit Tests. Now you have to go into each test to change a name
Add a way to select a bunch of tests then batch edit them to make a single change to a bunch of tests. That way, you don't have to go into 1 (of say 1000) tests just to modify the test with ONE word. So, if my tests name is Batch Production Phone Edit and I want to change it to Batch Production Phone Edit 1, Then Batch Production Phone Edit 2 etc. etc. I can just select each test and then batch edit to add the numbers to the end of the test title.
3 votes -
3 votes
-
modified test differentiated & Lock "update the original test"
if a test in a test instance is modified, it would have been marked somehow so it would be differentiated from the original test.
In addition that an option to lock "update the original test", so he won't be able to easily update the original test.
Give an option to change a test for a test set for all runs, in a way that it doesn't "call" the test but clones it while giving an option to edit it.
3 votes -
zenhub
2 way integration into zenhub.
3 votes -
Allow for creation of conditional test steps
For example:
Step 5: "Select the folder with today's date"
- Condition: If folder does not exist, follow these steps (link to other steps, or insert in situ).
If the folder does exist, have the ability to skip the does not exist condition.
Sort of like an if-then-else statement inside a Test Case3 votes -
Controlling "Notification List" with PractiTest API
In PractiTest API, "Notification List" of "Issuse" cannot be read and set.
Please take action to expand the scope of use of the PractiTest API.3 votes -
Test Library Filter - show number of test instances in View
When creating / editing a Test Library Filter, in the Custom Field area, I'd like to have Instance Count shown in the Filter View.
3 votes -
Tables, Font sizes, inline attachments in Test cases description and test steps.
The following issues/suggestions related to description and test steps of a testcase(test library, requirement & test set/test execution):
1) In my organization we use JIRA and most of the stories contain data in tables with many rows and columns . When testcase( &requirement) is created from JIRA into PractiTest, data in table is displayed in between || in PractiTest. When the EYE icon in PractiTest, Table is not displayed. It will be great if we can at least display the data in table format when EYE icon is displayed.
2) When we contacted Joel on the help chat, he showed…
3 votes -
Can we specify Test Results file with xBot script run?
We have a field "Results Path" under Automation info tab while adding an xBot Test Case from PractiTest. Can we have a field to specify the Result file to upload during script run?
3 votes -
Add the arrow navigation controls for pages of Test Instances under Test Sets and Run to the bottom of the lists of Test Instances
Add the navigation controls for pages of Test Instance under Test Sets and Run to the bottom of the lists of Test Instances...I am referring to the forward, backward, beginning of file and end of file arrows (that are almost missed being so small) which are next to the drop down for number of Test Instances shown on a page. It is frustrating to scroll to the bottom of a 100 Test Instance list and need to go to the next page only to have to scroll back to the top to access the controls to go to the next…
3 votes -
Add the functionality for the list of pages to maintain the history of which page the user is currently on.
When you are in a specific Test Case, which happens to be on a page which is not the beginning page (Page 1), and you back out of that Test Case, it is very frustrating to be sent back to the very front of the list of pages instead of backing out to the page of Test Cases you were on before selecting one to view. Example: If you are on page 4 in a list of 1000 Test Cases (display 100 Test Cases per page set) and had been looking at one particular Test Case and then back out,…
3 votes -
Allow updates to test cases via the API to function as expected.
Currently, if you attempt to update a test case that is currently in the test library, there are some fields that will not update. For example, if one attempts to update the folllowing fields:
"automated-test-info": {
"automated-test-design": "updatedDataHere"
}The API call returns a success, even though that data was never updated.
3 votes -
Remove the need to save in order to add attachments
Remove the need to save in order to add attachments: "To add attachments to this step you need to save your test first."
3 votes -
Add an import feature that imports the name and description of an external bug tracking issue
Currently we have to manually import the issue name and description and then Sync requirements and bug tracking issue.
A function that creates a new TestSet with the name and description fields imported from YouTrack or another bug tracker and then automatically linked to the Requirement would be great for productivity and streamlining!3 votes -
Add a link to the test via Test:ID
I'm missing the reference from Test Set to Test.
To see previous results of this Test, I have to go to the Test Library. A direct link would be more practical.
In the Test Instances list, there is a column Test:ID. When I go to the ID I want to jump to the Traceability tab of the Test.3 votes -
Can import requirements without applying mandatory fields
If I have a required custom field for a requirement that field is still blank when I import the requirement. I'd expect it to force me to select/enter a value, if it is required.
PractiTest vendor suggested to raise here:
Hello Narasimha,
Following my conversation with the Product Team.
The request to add a verification/error step in case of the Import Jira issue to Requirement is not a request for just an enhancement, but rather a request to change the current functionality.
If implemented, this change might affect many other customers, which do use the Jira integration with Mandatory fields…3 votes
- Don't see your idea?