592 results found
-
expend the search feature when adding a test to a test run
When adding tests to a test run you can either select from the entire list of tests or run a pre made filter. It would be nice if this had a few more options such as:
- Free form search
- Select Tests from an existing run
- Pick a Folder to add tests from
2 votes -
Add to the Report a simple metrics of the overall test progress
To display the percentage of the total number of tests that have been executed (test marked as, Passed, Failed, Not Complete)
i.e. 6 total tests, 2 marked as Not Complete, 1 passed and 3 No Run.
Percentage Test Executed = 50%
Along with metrics to capture the Test completed status (Passed Test Vs Total number of tests) as a percentage.
i.e. 6 total tests, 2 marked as Not Complete, 2 passed and 2 No Run.
Percentage Test Completed: 33%
3 votes -
Implement ways to manage the automation job queue
Currently, there is no way to see what jobs (test runs) have been started or are in the queue to run. Furthermore, there is no way to cancel a job once it has started. Also, only entire test sets can be sent to the job queue, when there are many times when it would be beneficial to submit only a subset of tests in the test set. For example, when you want to re-run a failed test, there is currently no way to do that without executing the entire test set again.
3 votes -
Better test step UI for running and editing test cases
Step result - Rather than just change the colour of the step name/heading, which gets lost in the links and other text above/below it, shade whole the step area/row.
If step N has a result provided (pass, fail, block), and all the steps between step 0 and step N are blank, set steps ) to N all to Pass. This will reduce the number of clicks a tester has to do in order to work through running a test case.
Allow a step to be flagged as "needing review" while the test is being run so it can be completed…
3 votes -
Add / Delete multiple steps with a single click
PractiTest is rather click-heavy.
One way to reduce this would be to allow multiple steps to be added quickly. A data entry field before the Add Step link allowing the user to provide a number of steps to be added would be a simple fix. Default this to 1 and existing behaviour remains. If the user enters 23, then 23 new blank lines are added/inserted. This will facilitate faster/less disrupted test case writing.As the user may then over estimate the number of blank steps required, an option to Delete all blank steps would be a complimentary click reducing feature.
8 votes
Ido Tandy
responded
-
Field data set on 1 screen and showing back on other screens
For example:
I have 1 Custom field browser (list) that have some values in it (Chrome, Firefox Safari etc.)
I set that custom field on the screen:
- Test
- Instance
- IssueWhen I Create new Test and I set the Browser: Firefox when im done with the Test --> Il Create TestSet & Instance = When im in the instance screen I see the Custom field Browser thats already filled in with 'Firefox' that I have selected in the screen Test.
Start the instance and there is a Issue --> Create an Issue, Open the Issue screen and…
3 votesIdo Tandy
responded
-
Change test history so to show previous and updated value
Test history currently only shows me the step name which was updated/added/edited. I need to be able to see specifically what a team member has updated - a 2 column page with time stamp, user name who updated, left hand showing what the value of a field was, and the right hand showing what it was updated to.
3 votes -
Add page nav to bottom of test instances grid
Very simple, quick fix. I like to view the maximum number of test instances at one time (100). But there are no nav controls at the bottom of this grid, so to get to the next page, I have to scroll all the way up to the top of the page to click the "Next page" button. Very annoying.
3 votes -
Not auto-enable bookmark panel in PDF reports....
Since there are no bookmarks created in the PDF versions of PactiTest reports anyway.
1 vote -
Add date-based and "show most recent only" filter options to "Instance" report types.
It would be very helpful to have a report shat shows only the most recently run test instance and exclude the older test instances for the applicable filter.
3 votes -
1 vote
-
When updating an issue some values update instantly disregarding "Back to Issues" while others do not
Open an issue
Insert a title
Save changes
Re-open issue
Editing the title and pressing "Back to Issues" will cause a confirmation box to appear asking you if you are sure that you don't want to save, pressing "No" will make sure that the changes are not saved.
Changing the "Status" to "Rejected", adding attachments or comments will instantly save even if you press "Back to Issues" and choose "No" at the confirmation box.Expected result: Every change made will only save if you choose "Yes" at the confirmation box
Actual results: Results are inconsistent, some values change instantly and…
1 vote -
Filters by users which are no longer part of this project
Filters by users which are no longer part of this project
4 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 -
Add defect search functionality to Add Existing Issue to Test flow
When linking a defect to an executed (failed) test, you do not always remember the defect ID. This is an annoying way to currently link defects.
On the link existing issue step, it would help greatly if we could bring up a list of all defects and be able to sort and search them by date/title/description.8 votes -
Add status for users in user setup
In current version the basis for access and invoicing is users defined in the user setup. In a project when testers are involved now and then, the administrator must manually remove the users to have control of the costs. When the users is supposed to do testing activities later, the admin must then manually add all users. This is very time consuming in big projects. However, it should be possible to set a user inactive by changing a status that will prevent the user from having access to the project and also will exclude this user from the payment.
1 vote -
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 -
Editing option for cloned tests
Once we have cloned a set of tes cases can we have the option of going back to the batch and re naming the certain batch down the line.
1 vote -
Improve functionality of editing and updating tests from runs
I find the current functionality of updating your test while executing it a bit clunky. Now I do understand that it is meant for small changes where big test overhauls should only be done in the test Steps tab but still I think there are some improvements to be made.
1) If a step has been edited during a run, PT should ask the user if he wishes to 'Update Original test' before navigating away from the page. I find that I often update a step but forget to click the button to update the test at the end.
2)…4 votes -
API to the DB, so we can run queries directly to the DB
It can be used to run any report that multiple DB insertions that are not currently supported
6 votes
- Don't see your idea?