As a new user of testlink (for evaluation) I suffer while experimenting through the process:
TestLink is lacking something in the interface to materialize the process of creation of Tests.
I think that better than to mask unavailable steps, it should be preferable to disable it.
For example in order to execute tests, one must do the following steps in order:
1- write test specifications
2- create test plan
3- define test suite
4- create a build
5- assign test plans to users
Alex___
Need for more didactic interface
-
alex_dacosta
- TestLink user
- Posts: 8
- Joined: Mon Nov 14, 2005 9:03 am
I think interface can be improved, but IMHO the problem when using
a new product, exists always.
The best approach:
read the user manuals (that may be can be improved)
then experiment
I\'ve evaluated Salome, Test Master, TestDirector, QuickTest, dotproject, mantis, and always faced the same initial difficulty, understand how
to move in the user interface.
a new product, exists always.
The best approach:
read the user manuals (that may be can be improved)
then experiment
I\'ve evaluated Salome, Test Master, TestDirector, QuickTest, dotproject, mantis, and always faced the same initial difficulty, understand how
to move in the user interface.
Make TestLink more intuitive
I need to add my comments to this topic, as I have been poking at TestLink for several weeks to see how I might use it. I have read the documentation several times, and I believe I now understand how things work, but I still find myself trying to figure out how to get to the right page in order to view something or create something.
The key problem seems to be that if something hasn\'t been defined, that item or the options related to it are hidden. For example, if a Test Plan hasn\'t been defined, none of the options for adding test cases or builds are shown. It would be better to display these options unactivated, with just the options that are permissible active. This allows you to figure out the workflow.
A second example is the permissions/rights concept. It is very flexible, but is also confusing. It\'s not clear what will be hidden when a user has been given a certain Permission level, or when they are assigned Ownership of a test suite. Again, if their Permission level does not allow modification of something, better to dim it out than to hide it. It would help if there was a pop-up text when you click on the Permission field next to your user ID at the top of the page that explains what you can/can\'t do given your permissions.
In general, I am impressed by the power and flexibility of TestLink, but additional attention needs to be given to the user experience.
The key problem seems to be that if something hasn\'t been defined, that item or the options related to it are hidden. For example, if a Test Plan hasn\'t been defined, none of the options for adding test cases or builds are shown. It would be better to display these options unactivated, with just the options that are permissible active. This allows you to figure out the workflow.
A second example is the permissions/rights concept. It is very flexible, but is also confusing. It\'s not clear what will be hidden when a user has been given a certain Permission level, or when they are assigned Ownership of a test suite. Again, if their Permission level does not allow modification of something, better to dim it out than to hide it. It would help if there was a pop-up text when you click on the Permission field next to your user ID at the top of the page that explains what you can/can\'t do given your permissions.
In general, I am impressed by the power and flexibility of TestLink, but additional attention needs to be given to the user experience.
I definitely agree that there is gap in usability of TestLink.
I identify these points:
I identify these points:
- * Extend information about features availability in User manual
* Add page that shows overview of un/available features for the current user
* Create some instruction video for newbies