603 results found
-
Add an instance counter that gives visibilty to the number of Pass/Fail/Total runs.
A test is added to the Test Library that contains parameter values. That test is added to a Test Set multiple times with a variation in the parameter value. Each parameter test is run multiple times, some pass, some may fail. The overall pass of the test set instance can be determined by the admin user with pass fail criteria (percentage based) with a specification on the required number of runs per test instance. Eg. If there is only 1 pass and 99 fails the overall parameter instance should not be pass when there is a 100% pass run requirement.…
1 vote
Ido Tandy
responded
-
Reviewing Test Cases Support
Is there a way of making reviewing test cases easier?
We can mark the tests ready for review, but would be easy if we have some GUI support to add the review comments to the steps or description.
We don't have to rely on other tools to send review comments etc if it is supported in PT itself.
17 votes -
Enable add a screenshot embedded in the text instead of as an attachment
this will be useful when we would like to show what is the expected results for example or if there is an issue just take a screenshot and show it to our development team
instead of having to save the screenshot and adding it to the issue ...this will be useful also for showing screenshots of the tests and expected results
Thanks.
5 votesIdo Tandy
responded
-
Add a 'Part Passed' status to test runs
As a tester when I would like to be able to set tests to 'Part passed' (i.e passed with minor issues). This would be useful for so that minor issues, that do not block the release can be reported against a test and do not get lost, and reports can also be run showing a 'passed' status. The test does not completely pass, but you do not want it to show as a big red fail in a report - the issues that remain do not block the release
2 votesIdo Tandy
responded
-
Add the 'linked bug' flag to the filter selection criteria on tests
As a tester, I would like to be able to use the 'linked bug' flag in a filter selection criteria on tests
This would enable me to find tests that may have been marked as 'passed' as they meet the release criteria, but still may have minor issues outstanding against them. i.e. create a filter of tests that have a linked bugs regardless of the test 'run status'.3 votesIdo Tandy
responded
-
Huge memory usage on Firefox 56 @Windows 7
I spotted Practitest is the reason of huge memory usage in FF browser with Windows 7. Usage is gradually increasing, especially when I open it in few tabs. It is laggy as well, but only within tabs where I have Practitest.
After closing tabs with Practitest memory is not released.
1 voteIdo Tandy
responded
-
4 votesIdo Tandy
responded
-
Clicking on link to attachement opens a file instead of give choice open or download
In Firefox browser I spotted following situation - when I click on link to attachment, PractiTest opens a file instead of call browser's dialog with option to choice - open or download a file.
1 voteIdo Tandy
responded
-
Add Status to Steps
It would be useful to add Status on steps so that a single test can be divided in different steps which should be evaluated singularly
3 votes
Christine
responded
Hi Fabrizio,
Thanks for your feature request.
Could you please clarify it?
Thanks in advance.
Best regards,
Christine -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
9 votesIdo Tandy
responded
-
Link an Issue automatically as a failed Status of a Requirement.
Edith said to me: With regards to the Requirement, the status will be Failed, but the Issue will not be linked automatically. You can link it manually. I agree with you that the Issue should be linked automatically and will happy if you can add it as a feature request here.
1 voteIdo Tandy
responded
-
search
I would like to search in a broader context, not just in a specific project, but search through all the projects
2 votesIdo Tandy
responded
-
Requirement adding/modification must be shown in the history tab of it
I think title explains it :)
1 voteIdo Tandy
responded
-
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 votesIdo Tandy
responded
-
Add the ability to edit the default JIRA ticket text
After clicking 'Fail & Issue', a JIRA ticket is created with the 'Summary' field populated automatically with "Bug reported from test: " followed by the test name. This can make the name unnecessarily long or potentially not follow existing naming conventions for a particular JIRA project. It would be nice to set a custom value for this pre-populated text, instead of editing it manually each time. For example, I use "PT Report: " as an abbreviated version. A company might want an even shorter code.
It might also be a handy feature to choose to put this text at the…
5 votesIdo Tandy
responded
-
Dependencies on params
Can we have feature of having different expected results depending on chosen params? It would be very useful in cases where you have similar steps (driven by param) but different exepected results.
1 voteIdo Tandy
responded
-
1 voteIdo Tandy
responded
-
3 votesIdo Tandy
responded
-
Allow the account admin the ability to create reports/dashboards across projects.
Dashboards and reports should be able to be created to report on multiple projects. If an organization is able to report on all the activity within Practitest, it will allow Executive Leadership the ability to see the entire workload of what is being processed via Practitest.
It really will show the immense activity accomplished during testing as a whole.
10 votesIdo Tandy
responded
-
Import Jira requirement ticket with all it's sub-tickets
In order to provide better coverage of the specifications I do propose to implement:
- Tree-like import that means importing parent and subtickets;
- Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
- Add system field "Traceability" for requirements that will reflect clickable test IDs;
If the solution will be implemented it will simplify test covering process and test covering tracking process;
28 votesIdo Tandy
responded
- Don't see your idea?