613 results found
-
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 -
Extend Auto Filter to User Type of fields
Auto Filter is a really interesting feature, but is today limited to the "List" type, and some other types may be usable for this, such as "User" Type
I actually created a User Custom field (Reviewer) and it would be interesting to provide a filter to the different reviewers for their current list of review to do...It would be also interesting (but may be more complicated) to be able to generate Auto filter based on Cross Filter based on Auto filter...
Again, we have a referent on the requirements, (User custom field), and we could create auto filter with…
7 votes -
fix a bug with importing tests
We continually get the same error when importing tests from an excel sheet. We fixed the author names to the current user, but continue to get the same error after trying to re-import the newly edited and saved file. This happens even when trying to login and import from a different browser and even when attempting it with a different user.
1 vote -
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 -
Grouping of Dashboards
We have made some dashboards for our progress, one that shows all sprints, and one for each sprint. That means that there will be many dashboards, so a possibility to group dashboards would be nice. So that we could have just “All Sprints” as a tab, but a hover on the tab shows a menu for each of the Sprint dashboards.
3 votes -
10 votes
-
Enable sorting on the columns in the pop-up to add test cases to test sets
When adding test cases to test sets, the pop-up you have to select them in has no option to sort the listed test cases - which makes us very dependent on detailed filters or the list becomes hard to work with for us with +10 sub-pages to click between to find the right test case.
We suggest to enable sorting on the columns, so we can sort by name or ID.1 vote
Ido Tandy
responded
-
If step name is blank, add the step number in the history tab
Right now it will just write "Updated step " and you cannot know what step was updated, were if you have step names it will write "Updated step [step name]"
We find it time consuming to always name steps, and step name and step description are often duplicates, so we would like to have the option to not user step names, but still get the history when steps are changed1 vote -
1 vote
-
Integrate steps parameters with FireCracker (and/or API)
BDD automation has a feature call "Scenario Outline", where you can define a table data for the test. This feature is based in step parameters.
PractiTest hosts also a step parameters feature, although the table data is defined at run time, unlike BDD automation, which is defined at test definition time
This can be solved with a custom field hosting the table data, where automation framework can retrieve it using the API, but the problem is when we try to create a run.
I have tried FireCracker with a Scenario Outline test and the report is not accurate because it…4 votes -
Trigger reminders to ensure test coherence between results and issues
Currently, I am using an extraction of issues and test statues to identify in Excel:
- Failed tests linked to closed issues => for testers to update the status of the test
- Failed tests not linked to any issue => for testers to link them to an issue
- Highlight the issues that need to be replied to or retested (e.g. rejected, fixed)This involves:
- Duplicating lines where tests are linked to several issues
- Vlookups between issue statues and test statusesMy idea would be to have triggers in the UI and perhaps also by email to…
1 vote -
zenhub
2 way integration into zenhub.
3 votes -
Calculate a field based on the values of other fields
I am imagining the following to avoid using the green monster.
Issue form with the following fields:
• Reach (value dropdown 20)
• Impact(value dropdown 0.5)
• Confidence (value dropdown 100)
• Estimate (value dropdown 10)
• Score (calculation: 200.5100/10=100 from the above fields)6 votesIdo Tandy
responded
-
4 votes
-
4 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 -
3 votes
-
Don't scroll to the top of the page when clicking the menu icon for a filter
When a filter name is low on the page and you click on the menu icon next to it, it scrolls you to the top, causing you to have to scroll back down the page to the filter.
4 votes -
Make step name not required when importing from spreadsheets
Step names are not required within the tool and it is an extra hassle to have to include them when we import test cases from a spreadsheet. Could you make that a non-required field when importing?
1 vote -
Add tables support
add an option to create, and modify a table in a test's description, expected results and actual results.
and also to paste a table directly to any of these fields.
6 votes
- Don't see your idea?