238 results found
-
More detailed reporting: more types, customized field selection, custom colours,etc
More detailed reporting: more types (currently just bar/pie or table), customized field selection, custom colours (eg: user can select red for failed, green for passed, etc)
3 votes -
mails on issues updates
please enable the possibility to assign a bug to the developer but still the developer will not get an email each time i click the save icon.
1 voteit’s already available
-
In the "Issues" view, save the option selected which controls the number of issues displayed per page
The option selected in the drop down controlling the number of issues displayed per page is not persisted. If you change the option, view an issue, then return to the "Issues" tab, it is reset to 20 issues per page.
11 votes -
Run status should be followed with %Completed
When test or step are blocked or Failed the only way to know test set or test progress is by entering into them.
Good solution suggested by Yaniv is to add "%Completed" for each.5 votes -
Add to the Test set instances table "Test:Last Run" and "Test:Last Version"
Test set instances table contains "Last Run" column from current instance. Same test which is performed in other instance will not appear. by showing to the manger and the tester when was the last test execution and on which version
it will simplify the work. Currently the only way to see the information is to enter each test and then to its instances.1 vote -
Expand the tree view horizontally
To avoid scrolling the view pane
1 vote -
Show test description on run test screen
For teams which are very familiar with the system under test it is not necessary for the test case to include steps. PractiTest does not accomodate for this practice because:
1. It never shows the test description, only the title;
2. It always shows steps, even when there are none.I propose adding the test description to the initial screen (the one with the "Run test" button"
When a test set run is started, PractiTest shows a screen with a "Run test" button. There is a lot of room in this screen that could benefit hugely if the test description…
0 votesNo problem. Updating this idea as completed.
-
auto back up
have scheduled backups for the test in the customers side
1 voteWe provide this function from the API so you can now run a scheduled job to perform this
-
Support different font format and colours
It will be great if different format styles and colours are available for writing Test cases especially when you want to highlight some text in the test cases.
2 votes -
personal tab
tab that will show all the stuff that you need to do (Tests, Issues, Requirements, etc).
13 votesHi,
KIndly note that we’ve recently released a new feature called ‘Task Board’ that allows to see all the entities assigned to you in one place.
Please see more information about that on a page below:https://www.practitest.com/help/general/task-board/
Thanks and have a nice week!
Best regards,
Christine -
Linking external id (Requirement id) to test library and instances
Linking external id (Requirement id) to test library and instances
6 votes -
Missing ability to copy-paste steps, even inside the same test
...It will be very useful and will save time
28 votesHi,
We have reviewed this feature request and added a feature called “Call to Test” that allows to call to steps from other test cases while creating or editing test cases. Find more information here:
https://www.practitest.com/help/tests/call-to-test/ -
Clone test in test editing and search results screen
How do you clone one test? Currently you have to (1) do a search, (2) identify the ID of the test, (3) then go to the test library, (4) navigate to the page where the test can be found and (5) clone the test. Please mind that step 4 may involve trying several pages before you hit the one where the test is listed. This is not very practical. Therefore I propose that a "Clone this test" link or button is added to two places:
1. The search results page and;
2. The General tab of the test editing screen.…
5 votes -
15 votes
-
Test set time estimation (execution)
I need a way to estimate how much time needed for test/test set. one way is to count each test/step running time. another way is to allow me to know how many steps there are in test set and I will estimate them approximately (#minutes per step multiple number of steps).
2 votes -
Generate report of users in each project
If you have a number of projects and users it is difficult keeping track of who has access to each project. I would like to go into Account Settings and generate a report as a table with users (rows) and projects (columns) showing who is assigned to each project. Before adding new users it would be quite easy to see if existing users could be moved off projects. This suggestion is related to the suggestion "Add licence limiter and administration".
4 votes -
Optimize dashboard layout
The current dashboard layout has a huge empty space because (I'm guessing here) of the "Customize dashboard" hiperlink. As a consequence of this, the first line of graphs has only one graph instead of two, and this graph on is a bit offset to the right and therefore not aligned with the left graph on the second line. All these issues can be removed improve by simply transferring the mentioned hiperlink to the blue line which is part of the dashboard tab.
2 votesfixed
-
The Author of Cloned Tests will be the 'cloner' instead of the original creator of the test.
Currently, by cloning a test, the
Author is copied from the original test.
This may cause confusion when users clone tests and modify them.
Setting the cloner as the Cloned Tests' Author will solve this issue.20 votes -
Include tags in batch edit
During initial importing of test cases from another tool or project, batch edits are a very important tool. However, for some reason, tags are not available in batch edits. The tags field should be added.
37 votesHi,
Please note that from now on tags are available in batch edit as well.
Best regards,
Christine -
Rollback an importation
Currently the importing process imports whatever records are correct and provides information regarding the records that couldn't be imported. Although this is fine, the user is then left with two options:
1. Cut and paste the failed records from the original file, correct them and try importing the new fileor
- Delete all imported records, correct the original file and repeat the importing process.
I propose adding a functionality which would allow the user to rollback the last imported records, allowing him to correct the whole original file and retry. This would allow the imported test cases (for instance) to…
0 votesImport process first validates data and doesn’t add partial rows
- Don't see your idea?