20 results found
-
Github with Two-Way Integration
Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.
40 votes -
Ability to add a test case to a test set by writing the test number/range
As mentioned with the Ability to add a test case item, we tried filters; it’s cumbersome to have to shift gears and create a new filter every time that we want to look up / search for something new. It clutters things up as then there is the maintenance and scrolling to contend with as well.
26 votes -
clone or copy views in the tests library
For example we have a view with a lot of child views and now We would like to create the same view but with a different parent filter. So we would like to clone the existing tree and modify it instead of creating it from scratch.
17 votes -
Include comments in the PractiTest API
Include comments in the PractiTest API.
17 votes -
Add new value to standard or custom fields via API
In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.
At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.
17 votes -
Ability to get all filters for a project through the API
We need the ability to get all filters for a project through the practitest test API. Currently we are trying to use the API to generate an internal report based on test sets in a test filter.
We can filter the test sets by the filter-id but we have no way to prompt the user which filters are available to generate the report on.
Maybe something like:
https://api.practitest.com/api/v2/projects/YOUR_PROJECT_ID/filters.json16 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 -
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 -
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 -
Copy/Link attachment from test result while generating an issue
Now you have to upload an attachment twice when there are issues to raise. It would be handy if an attachment can be linked or copied to the issue.
10 votes -
keyword search loses many test cases
When I enter a keyword and search, many test cases with the keyword will not show.
Now just crtl+F for every page and it is miserable...9 votes -
Option to remove 'title' field for every test step
Although a small issue, this becomes irritating when we are creating or importing dozens of test cases.
The 'step title' field (it doesn't actually have a name) adds an extra step which seems unnecessary. In my experience it is rare to need to title each and every test step. Please could you have the more standard Description-Expected Result only format when creating test steps?5 votes -
Number of copies adding test to test set
When performing repeatitve testing with step permuatations, it takes ages in the new UI to add the same test into a test set multiple times.
It would be useful to have a 'number of copies' option.
Select the test - add to test set - number of copies = 20
Then 20 instances of the same test are added to the test set3 votes -
Add Test to the Testset inside the test itself
When I'm in the Test, I might decide immediately to add it to the Testset/create a new Testset with it.
Now I need to go back to Test library, select this Test, then click on "Create a Testset"/"Add to existing Testset" buttons.
This is too many clicks, I want to decide whether I want to run my test or not when I'm inside this test.3 votes -
2 way integration with Azure Devops (ADO) Server doesn't exist
Currently we can create a 2 way integration with Azure Devops, but only if Azure is on Cloud.
The integration with Azure Devops Server doesn't work.3 votes -
Improve Fogbugz Integration (Push data to and from Pracitest)
(1) link test cases to externally stored requirements (In fogbugz) and push the externally stored requirement data into Practitest requirements for reporting/dashboard.
(2) Add a Push link next to the Defects field in the Test Run Result screen which pushes a bug report to the external system (FogBugz) without leaving Practitest and make a copy in 'Issues' at the same time for reporting/dashboard.
(3) Hyperlinks to externally held data if only linking to issues/requirements in the external system and not pushing data to and fro (hovering the mouse cursor over a fogbugz case ID in either issues or requirements screen…3 votes -
Test Set table: User should be able to edit fields directly from table
Test Set table: User should be able to edit fields directly from table
2 votes -
Report Center: Missing a free text area for a sub title
(Short report description/summary to be added manually by the reporter)
0 votes -
Ability to resolve comments with indication who resolved them
Ability to review similarly to Word (Add comments, tag, suggest edits, resolve/reject suggestions)
0 votes -
0 votes
- Don't see your idea?