615 results found
-
Click on Table totals on Dashboard to see those issues
On a dashboard widget where there is a table of issues displayed as status versus priority with the totals at the end of the row. It would be good to click on the total at the end of the row and see the issues.
Same for a pie chart. Click on all that are in status assigned.
If both loaded a filter, that would be good.0 votes -
Add the ability for Xbot tests to pass triggering instance ID to the client
tl;dr: we would love being able to have Xbot tests with a Script Path of e.g.
run_test.py $INSTANCE_ID
, which then executesrun_test.py
on the target client with the actual ID of the instance that triggered the run as a commandline parameter.To elaborate some more on our use case: we use PractiTest together with Xbot and Squish to automate running our BDD GUI tests on cloud VMs. However, we want to have per-step granularity in our logging of test results rather than just the pass/fail outcome determined by Xbot based on the exit code.
Our solution to this is…
3 votes -
Pre-populating Step Parameters values
Pre-populating Step Parameters values based on the Tester or other field.
0 votes -
Display the linked Requirement and Requirement Status in Test Set
Display the linked Requirement and Requirement Status in the test set
0 votes -
Test Set column for number of steps
Display a column with the number of steps of an instance inside a test set
0 votes -
Add the ability to create a not cumulative progress graph
This graph should show the daily progress rather than cumulative progress
0 votes -
Remove auto filter limitation
Support the option to create more than 50 auto filters per module
0 votes -
Test: Preconditions field to be displayed on the Steps tab
Change the location of the test precondition field to be in the steps tab
0 votes -
Export Project history
It would be nice to have an option to export Project History as an excel file, according to the filtered results.
3 votes -
Add Markdown button for code area
Markdown fields currently support one form of code formatting - red text, gray background.
Add support for the additional coding format - black text, gray background0 votes -
Make test run pause button sticky
Test Run "Pause" button is only available at the bottom of the screen, consider making it sticky and available at all times
0 votes -
Better support for tables in Markdown
Improve the appearance of tables embedded into Markdown text boxes
0 votes -
Support for auto filters for more than 2 levels
Allow to create auto filters on more than 2 levels
0 votes -
Using Smartfox on the issues module
Ability to refine the description of Issue, when creating the issue not via fail& issue.
This can be used as spell checker (we already got it) but also as a tool to standardize and refine the text for issues, when non native English speakers are entering the data
0 votes -
Reorder a group of instances in one click
Right now I can drag one instance and move it to another place in the instance list in the test set.
I'd like to be able to check more than one instance, and then be able to move it to another place in a grid altogether2 votes -
Why put a toggle Preview button if it does not match the format after saving
When creating test cases, we usually use nested lists. Considering many limitations on that text area field in terms of format, I rely on the toggle preview to see how it will look like once I ran the test case. However, that is not the case. Can you please fix the formatting on lists there are like a hundred issues on that module alone. Then after that, make sure the Toggle Preview does its job.
3 votes -
When creating a Run dashboard item, allow to select Instances/Testsets/Tests fields vfor axis
Currently when we create dashboard item for Instances, we can select fields from Testsets, and Tests
When we create the same item for Runs, only run fields appear. Can we also enable such thing for the Run dashboard items? Including the instance fields.7 votes -
Allow multiple Gitlab integration per PractiTest project
Because our project is split in multiple Gitlab repositories (Hardware, firmware, software), we have to split the Practitest in multiple project too in order to use the Gitlab issue integration. It would be great to be able to specify several Gitlab repository linked to specific field.
3 votes -
When creating a new test via "Save and New" the steps should be copied from the previous test.
When creating a new test via "Save and New" the steps should be copied from the previous test.
1 vote -
Copy custom fields with values from one project to another
Sometimes, as an account owner, I need to add a new custom field to every project. The behavior of this custom field is the same and so are its values, it doesn't differ between projects. Right now I need to recreate such a custom field manually, no matter how many values it has.
It would be much easier if there would be an option to copy the custom field from another project, with all the values.8 votes
- Don't see your idea?