556 results found
-
Add support for SCIM
For example, users using AzureAD would like to have automatic sync between PractiTest and AzureAD users.
1 vote -
make requirements links visible when executing a test
When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.
39 votes -
Select multiple values in setting filter from Multi-list field
When you prepare data in Multilist, there should be easier option to select them in filter preparation.
Actual:
Set up multi-list field (eg. task number for functions) and prepare TCs with these numbers.
Prepare filter with multiple values - you have separately prepare filter or you have to click "Or", "open dropdown", "select value" repeatly.Expected:
Use shift/ctrl to select multiple values from multilist.
There should be displayed filed with selected list.
Clicking on field opens dropdown with selected values for editation of multiselection.
"X" will be over whole multiselection and delete whole selection1 vote -
Ability to link a requirement to another requirement
Ability to link a BR to the FRs that supports the BR.
1 vote -
Include comments in the PractiTest API
Include comments in the PractiTest API.
17 votes -
Enable automatic download of reports
Currently get an automated email with a link to click to download the report. I would like the report downloaded automatically.
E.g. If I could anticipate the link to download the report (as currently added to the email) I could generate it automatically and hence download the report. You might also provide an api style interface such that the report is available in chrome as a page which can be extracted from chrome as JSON.
P.s. Not a good solution for me, but still a solution, have you thought about a google drive interface for the reports (and exports) to…
3 votes -
1 vote
-
Test case templates
Allow creation and selection of test case templates. These could have standardized titles, step names, etc. Example:
Title: "My App: <component>: <test>"
Step 1: "SETUP"
Step 5: "CLEANUP"20 votes -
Add project name column to Slack integration
As a company with many related projects that are reported to the same channel, we have a need for distinguishing between the tests belonging to different projects
1 vote -
Add status 'SKIP' for skipped test case while run an instance
Hi Admin,
while running of an instance, it had better provide a status 'SKIP‘ so that we can know how many test cases 'SKIP' in regression testing.
1 vote -
Adding a Header on External Dashboard
Similar to JIRA headers.
Ex: A dynamic todays date added to current release.1 vote -
Support to create / modify dashboard via API
Hi, While we integrated API into our testing pipeline, noticed that it could not create / modify dashboard via API.
Suggest to support this feature.
1 vote -
Ability to create a burn up report.
If we know of a particular release date and we want to track test execution to that date, then a burn up report can help us track and highlight risks at a very early stage.
This should take into account the testers available for the execution so that it can work out the velocity accordingly1 vote -
Ability to customize time for scheduling reports in practitest.
Currently practitest tools schedules all report (daily / weekly or monthly) at 6.00 AM but it would be great if tool allows to customize time for scheduling the reports to be delivered.
7 votes
Ido Tandy
responded
-
Goto Test field should find tests by name
NARRATIVE: The "Goto Tests…" field currently only works for test IDs. It would be nice to be able to go to tests by test name as well.
STEPS TO DUPE:
1. Go to the Test Library module.
2. Type an existing test name into the "Goto Tests…" field
3. Push return.RESULT: All tests for the currently selected filter are displayed.
EXPECTED: To go to the test with the matching name.
3 votes -
Add a Check Box for Tests that are just Steps that are reoccuring but not needed in the TestSet
There are many cases where "Login as.." for instance is just called by other tests so that is not repeated in every Test, These "Login as" Tests are necessary but not necessary in the TestSets. Could a small check box, "Do not include in TestSet" be added so when we create a TestSet the Unnecessary tests are not visible or Color Coded to let the Tester know that Test is not needed in the TestSet? We are currently using xx as a prefix in the Test Name to distinguish these types of tests. Love your product!
3 votes -
Implement a way to avoid duplicate tests in test sets
I know the use case for adding a test more than once to a test set (for using parameters)
However what I often do is
Filter: V1.9
Add 50 test cases
Add some to a test set (not necessarily all)
Add 10 more test cases
Go to the test set to add some of these cases -- I'd like a checkbox to show ONLY tests that are NOT already in the test setOtherwise its really easy to create duplicate test instances in the test set when I just wanted to add the new ones in
7 votes -
Add a way to trigger run machine to start a test set
Our automation test execution (ATE) machine can receive a remotely command and put into queue, commands from queue will be pulled out and processed, such as 'Build', 'Program', 'Run', 'Report'... but I can't find any way to trigger our ATE from Practitest server now.
3 votes -
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.
I general we should add the option to filter according to certain fields
15 votes -
Add parctitest "test id" from Jira (directly)when I created new ticket
Add parctitest "test id" from Jira (directly)when I created new ticket
4 votes
- Don't see your idea?