Custom Fields and Keywords in TestLink

Custom Fields

TestLink provides a feature where User can create his own Custom Field and Keywords and also assign them to his Test cases.

When you create a test case, by default the fields provided are:

• Test case name
• Test case summary
• Test steps
• Expected results

which is quite sufficient to start with your testing. But, apart from managing the test cases, providing good test metrics is equally important. For example, if you are able to record how much time it took for you to run 200 test cases for a particular test project, it is a useful benchmark for planning your regression cycle for the next release or to estimate the time for a similar project which is about to start.

For this reason, TestLink provides 2 default custom fields:

1. Estimated time to run

2. Actual time to run

The field "Estimated time to run" can be configured to be displayed during the test case creation stage, so that the creator enters a value that he feels is required to run the test. The real time, however, may be shorter or slightly higher than the estimate. This can be captured during the test execution phase. The 2nd field "Actual time to run" can be configured to accept values only during execution phase. That's pretty useful.

Important point: (Actual and Estimated Time have their default units in Minutes) but can be customized accordingly in Hours

Similarly other custom Fields can be created and can be assigned to the Test cases as per the requirement.

Keywords

TestLink keywords also play a very important role in planning your test execution and gathering test metrics.

For example, I added keywords "high priority test", "medium priority test", "low priority test", "automated". (PS: we can add more keywords like sanity, regression, etc)

These keywords can be assigned to test cases appropriately. This helps to filter test cases on a specific keyword during execution. i.e., When adding tests to a plan, we can search based on keywords and run tests which are only relevant to that cycle.

Example: To run a quick regression test, we can assign tests marked as "high priority" to ensure basic features are working fine.

Similarly, if you are focused on test automation, you can assign keyword "manual" to your tests, so that you can leave the tests which are taken care of by the automation tool and execute tests only for the manual tests.

We define Priority of our test cases with High, Medium and Low.

Similarly while defining a Milestone we have to define what %age of these individual priorities would be essential to achieve that Milestone:

High: 100%

Medium: 80%

Low: 20%

So all the test cases with Priority high must be executed to achieve 100% milestone

So 80% of the test cases with Priority Medium must be executed to achieve 80% milestone

So 20% of the test cases with Priority low must be executed to achieve 20% milestone