585 results found
-
Ability to sync the comments from requirements and bugs from ADO to PractiTest and vice versa
Currently when the requirements and bugs are synced from ADO, the comments are not synced.
For requirements the comments have valuable information reflecting the changes and doubts which are important for a tester to know while creating test cases so it is very critical to include the comments as well.Also if a tester has certain doubts on a requirements if there is a 2 way sync he can just post the comments on the PractiTest and they should flow to the linked requirement card in the ADO.
For bugs, since the developers won't always have access to PractiTest, the will…
28 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 -
customizable test progression graph in the dashboard
The test execution progress graph is a real good tool, giving clear info on a project progress status.
For now the time period of this graph is fixed to 28 days.
Being able to customize this X-axe would be very useful to study the reasons of slowliness in a project afterwards, for instance.8 votes -
Give users the ability to add custom fields at Test Step Level.
You should give the users to add fields at test step level.
They should be allowed to Add things like Test Data for a particular step like Large Queries it it. For us the Test Precondition or Test Description or Test Name cannot be used for that purpose.
13 votes -
Remove blank columns & rows from detailed report (Excel)
When Practitest generates a 'detail' report of tests, in Excel format, there are two blank columns on the left (A & B) and a lot of blank rows padding the report. These blanks waste space on the screen/ sheet when printing. I have to manually remove these every time, which wastes time. Please could you take them out of the default report ?
8 votes -
Add ability to get the steps based on filter-id.
I want to get the steps of test cases which are in Automation status (Automation filter).
3 votes -
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 -
Clone Test Set with current test status
There should be an option to allow the user to clone either as anew Test Set or with existing Test Status.
It will help us to run the same test set with multiple versions of our product.
Currently cloning reset all the test statuses.
3 votes -
Improvements to Exploratory testing
When using Exploratory testing can we have an option to:
(1) Take screen shot and add comments via the tool itself
(2) record all the screen actions as a recording.
(3) Convert all the actions automatically as steps if you want to make the test a scripted one for later use26 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 -
Show Requirement Description field
Requirement description is very important for users to overview all requirement list or check duplication after importing from excel file but now user only can see requirement description by view each requirement detail.
3 votes -
Give option to only run tests on instances that have 'ready' status within test set
At the moment, when I've created a new test I will leave it as 'draft' status until the feature comes available for me to test. However, I like to have my test sets organised and ready to go. It would be useful to have an option to only test the instances within a test set that have 'ready' status. This would save accidentally initiating tests for the instances that are not yet ready and are still in draft.
2 votes -
Add the possibility to compare two/several testsets contents
it is very often usefull to compare testets contents to extract information like:
- tests removed from one testset to another
- tests added from on testset to another
- tests seen as passed in one testset execution and failed in another testset execution (regression or test fixed)seems to be possible to do this through filters and excel (macro, formulas) would be useful to have it natively supported in PractiTest
3 votes -
Add Task board / Kaban keep last set filter
Each time the Task board (Kaban) screen opens the default filter is set.
Request to keep the last set filter.1 vote -
test execution
This is a pity that we can't see the test description + the attachments during execution.
+ the additon of a button to end the test execution . This is a strange feeling to validate the test by coming back to its description or in instances list.3 votes
AdminYaniv
(Product Manager, PractiTest)
responded
Hi Benoit,
Thanks for your feedback.
Kindly note that you can hover over ‘Test in Test Library’ and see the test description.
As for the button to end the test execution, our main goal was always to save tester time hence we initially did not plan to add any additional buttons to that screen.
Having said that, would recommend to use the keyboard shortcuts, see more information here: https://www.practitest.com/help/settings/keyboard-shortcuts/
Thanks,
Yaniv -
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 -
In Test Library provide the ability to add attachments to a filter or folder
Provide the ability to add attachments and/or links at the filter and folder level in Test Library. This way attachments that apply to all tests in that filter or folder can be stored once and not in each test. Similiar reason for URLs. It would be a place to store test instructions, data paths etc.
3 votes -
Drop images or docuemnts in description
Hello,
Attachements are quite painful to add: this is click-click-click ... We should be able to add images or documents in the description. Images would appear in the description, so we wouldn't have to re-click to see it real sized.Additionnaly we don't understand why we can't see the description of the test while executing test cases . Is it intentionnal ? Thanks !
7 votesThe option to drag & drop files into the description will be supported in the new forms UI we are working on these days. The test set / Issues form already have this option - soon all items will have it as well
-
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.
4 votes
Ido Tandy
responded
-
Provide a link to tests after they've been imported
When batch importing test cases via spreadsheet, Practitest does not take you to the tests you just imported, it just states whether the operation succeeded or not.
If would be nice if the imported tests were linked to on the result page so we can immediately start work on them. At the moment I have no idea where my imported tests end up so often have to search for them manually which takes time.
3 votes
- Don't see your idea?