Implementation of TestLink - basic steps from the idea of implementation to your logo in the reports
Having completed the implementation of Test Link in the company where I am currently working, I decided to tell about the steps that I had to perform before I started creating user accounts (that is, giving them access to the system). I wanted testers to see a tool that creates a sense of completeness and reliability.
All steps, except the initial installation, I did myself. And this means that the TestLink setting is not rocket technology and is subject to any manager (and not only).
Below you will learn about the following:
1) What to request from the person who will install TestLink.
2) What is desirable to configure (yourself or someone to ask) after installing TestLink.
3) How to translate the UI elements that are not translated and use it in TestLink.
4) How to transfer tests from XLS to TestLink.
')
In this article, I did not talk about the following things that need to be or should be done when implementing TestLink :
1) integration with bug (issue) tracking systems.
I set up integration with Redmine from TestLink (since the inclusion of plug-ins that we have not tested in corporate Redmine would be very risky and time consuming).
2) creating your own templates for reports (I haven’t done so far).
3) using TestLink within the framework of your company's business processes.
4) training to work with TestLink.
ATTENTION:
Before editing any test link configuration files, do the following:
1) Open the file in edit mode.
2) Change the file encoding mode to UTF-8. This step must be performed after each opening of the file for editing!
3) Now you can edit and save the result.
TestLink took the latest version, 9.1.11. Took assembly from Bitnami, bitnami.com/stack/testlink/installer
The program is free. Software website: testlink.org/
To install, you must ask the administrator to download and install this software. Or install it yourself.
1) Version number for installation
2) Test Link For work, you need a MySQL database and a web server. Often included in the test link distributions.
3) You need to configure the backup database. If you are also backed up with all the TestLink files, great. It is safer to make changes to the settings.
4) It is necessary to make TestLink include in the autoload of the server on which it is installed. This is necessary so that when you restart the server, TestLink will immediately start working.
5) Ask directly in the config.inc.php file (it is located in the /opt/testlink-1.9.11-0/apps/testlink/htdocs directory of the Test Link program) to make the following changes (if you need to support the Russian language normally):
$ tlCfg-> default_language = 'en_US';
$ tlCfg-> charset = 'UTF-8';
When you edit the test link configuration files in any way, make sure that you change it when UTF-8 encoding is enabled.
In addition, it is necessary for the administrator to request the configuration of the TestLink mail system. Those. Set up TestLink to work with your company's mail. It will just configure SMTP in the config file.
These steps have been done for fine tuning, i.e. not a sysadmin, but me, i.e. by the manager.
For settings, you need to go to the TestLink server via the SSH protocol.
If you are running Windows, it’s very convenient to use this program: winscp.net/eng/docs/lang:ru (this is popular Putty with a graphical user-friendly interface).
Configure the following fields in the config.inc.php file (it is located in the /opt/testlink-1.9.11-0/apps/testlink/htdocs directory of the Test Link program):
$ tlCfg-> exec_cfg-> history_on = TRUE;
$ tlCfg-> exec_cfg-> show_history_all_builds = TRUE;
$ tlCfg-> exec_cfg-> show_history_all_platforms = TRUE;
$ tlCfg-> exec_cfg-> steps_exec = true; - since TestLink 1.9.11 this value is by default
$ tlCfg-> exec_cfg-> steps_exec_notes_default = 'latest'; - this change allows you to display notes from the previous (last) test run in the notes of each test step, with a new test run.
part / * [GENERATED DOCUMENTATION] * /:
$ tlCfg-> document_generator-> company_name = 'company name';
$ tlCfg-> document_generator-> company_copyright = date (Y). ' Company name';
$ tlCfg-> document_generator-> tc_version_enabled = TRUE;
When importing tests or groups of tests from XML, if such a name already exists in the system, TestLink will generate a new name based on the existing one. The number of such a test in parentheses will be added to the name. If no changes are made, then the name will be formed as shown in commented lines, i.e. based on date and time.
// $ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> type = 'stringPrefix';
// $ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> text = strftime ("% Y% m% d-% H:% M:% S", time ());
$ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> type = 'counterSuffix';
$ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> text = "(% s)";
TestLink files with graphics are stored here: /opt/testlink-1.9.11-0/apps/testlink/htdocs/gui/themes/default/images.
Paste in the image directory two files with the same parameters as the files tl-logo-transparent-25.png and tl-logo-transparent-12.5.png.
We edit the following fields in the config.inc.php file:
$ tlCfg-> logo_login = 'file with your logo.png'; - file size 231 * 56 pixels, transparent
$ tlCfg-> logo_navbar = 'file with your logo.png'; - file size 116 * 28 pixels, transparent
Now on the login page, in the main menu of the TestLink menu, your company login will appear in the reports.
In the config.inc.php file, you can make a translation for the text used in the description of tests that are automatically created for the requirements.
You need to do a translation for the text provided by these fields:
$ tlCfg-> req_cfg-> testcase_summary_prefix
$ tlCfg-> req_cfg-> testcase_summary_prefix_with_title_and_version
You can edit roles in TestLink itself, i.e. create new and change opportunities provided for each of the roles.
In general, setting up roles is worth a separate article.
But, for example, make sure that the Show Test Cases Assigned to me option is enabled for almost all roles.
The test link includes localization in Russian.
The problem is that approximately 40% of the user interface elements are not translated into Russian there or for which I would like to change the translation.
Therefore, you can do additional translation work. Unfortunately, not all interface elements are programmed so that the translation for them is in one file.
Therefore, even after a full translation of the text from the custom_strings.txt file, there will be elements that are not translated into Russian.
What you need to do to translate the UI part into Russian (and any other) language:
1) Go to the directory /opt/testlink-1.9.11-0/apps/testlink/htdocs/locale/ru_RU (if we use Russian for UI) on the server with Test Link
2) Copy the files custom_strings.txt.example and strings.txt to your PC
3) Copy from strings.txt to custom_strings.txt.example data
4) Make the necessary translation in the custom_strings.txt.example file - ATTENTION !!! BEFORE EDITION BEGINNING, IT IS NECESSARY TO MAKE A VERIFICATION REFERRED AFTER THIS SEQUENCE OF STEPS!
5) Rename custom_strings.txt.example to custom_strings.txt
6) Copy the custom_strings.txt file to the /opt/testlink-1.9.11-0/apps/testlink/htdocs/locale/ru_RU directory on the server with Test Link
Before editing any test link configuration files, do the following:
1) Open the file in edit mode.
2) Change the file encoding mode to UTF-8. This step must be performed after each opening of the file for editing!
3) Now you can edit and save the result.
New versions of Excel do not support (in any way!) The XML format that TestLink understands.
Therefore, for porting is used external software, distributed free of charge.
The program is called EX-converter.
This is free software. Here is his page: sourceforge.net/projects/ex-converter/
The program works under MS Windows.
Go to TestLink. The bottom left will be the Documentation element. Choose the right documents and read (in English). There is, among other things, a user guide and a TestLink setup guide.
testlink.org
bitnami.com/stack/testlink/installer
winscp.net/eng/docs/lang:ru
All steps, except the initial installation, I did myself. And this means that the TestLink setting is not rocket technology and is subject to any manager (and not only).
Below you will learn about the following:
1) What to request from the person who will install TestLink.
2) What is desirable to configure (yourself or someone to ask) after installing TestLink.
3) How to translate the UI elements that are not translated and use it in TestLink.
4) How to transfer tests from XLS to TestLink.
')
In this article, I did not talk about the following things that need to be or should be done when implementing TestLink :
1) integration with bug (issue) tracking systems.
I set up integration with Redmine from TestLink (since the inclusion of plug-ins that we have not tested in corporate Redmine would be very risky and time consuming).
2) creating your own templates for reports (I haven’t done so far).
3) using TestLink within the framework of your company's business processes.
4) training to work with TestLink.
ATTENTION:
Before editing any test link configuration files, do the following:
1) Open the file in edit mode.
2) Change the file encoding mode to UTF-8. This step must be performed after each opening of the file for editing!
3) Now you can edit and save the result.
TestLink installation
TestLink took the latest version, 9.1.11. Took assembly from Bitnami, bitnami.com/stack/testlink/installer
The program is free. Software website: testlink.org/
To install, you must ask the administrator to download and install this software. Or install it yourself.
What you need to specify when prompted to the administrator:
1) Version number for installation
2) Test Link For work, you need a MySQL database and a web server. Often included in the test link distributions.
3) You need to configure the backup database. If you are also backed up with all the TestLink files, great. It is safer to make changes to the settings.
4) It is necessary to make TestLink include in the autoload of the server on which it is installed. This is necessary so that when you restart the server, TestLink will immediately start working.
5) Ask directly in the config.inc.php file (it is located in the /opt/testlink-1.9.11-0/apps/testlink/htdocs directory of the Test Link program) to make the following changes (if you need to support the Russian language normally):
$ tlCfg-> default_language = 'en_US';
$ tlCfg-> charset = 'UTF-8';
When you edit the test link configuration files in any way, make sure that you change it when UTF-8 encoding is enabled.
In addition, it is necessary for the administrator to request the configuration of the TestLink mail system. Those. Set up TestLink to work with your company's mail. It will just configure SMTP in the config file.
Setup Testlink immediately after installation
These steps have been done for fine tuning, i.e. not a sysadmin, but me, i.e. by the manager.
Retreat about the toolkit
For settings, you need to go to the TestLink server via the SSH protocol.
If you are running Windows, it’s very convenient to use this program: winscp.net/eng/docs/lang:ru (this is popular Putty with a graphical user-friendly interface).
basic settings
Configure the following fields in the config.inc.php file (it is located in the /opt/testlink-1.9.11-0/apps/testlink/htdocs directory of the Test Link program):
Show history and test steps during the test run
$ tlCfg-> exec_cfg-> history_on = TRUE;
$ tlCfg-> exec_cfg-> show_history_all_builds = TRUE;
$ tlCfg-> exec_cfg-> show_history_all_platforms = TRUE;
$ tlCfg-> exec_cfg-> steps_exec = true; - since TestLink 1.9.11 this value is by default
$ tlCfg-> exec_cfg-> steps_exec_notes_default = 'latest'; - this change allows you to display notes from the previous (last) test run in the notes of each test step, with a new test run.
Your company data in reports
part / * [GENERATED DOCUMENTATION] * /:
$ tlCfg-> document_generator-> company_name = 'company name';
$ tlCfg-> document_generator-> company_copyright = date (Y). ' Company name';
$ tlCfg-> document_generator-> tc_version_enabled = TRUE;
Setting the automatic correction of the test name (when importing from XML)
When importing tests or groups of tests from XML, if such a name already exists in the system, TestLink will generate a new name based on the existing one. The number of such a test in parentheses will be added to the name. If no changes are made, then the name will be formed as shown in commented lines, i.e. based on date and time.
// $ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> type = 'stringPrefix';
// $ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> text = strftime ("% Y% m% d-% H:% M:% S", time ());
$ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> type = 'counterSuffix';
$ tlCfg-> testcase_cfg-> duplicated_name_algorithm-> text = "(% s)";
Your company logo
TestLink files with graphics are stored here: /opt/testlink-1.9.11-0/apps/testlink/htdocs/gui/themes/default/images.
Paste in the image directory two files with the same parameters as the files tl-logo-transparent-25.png and tl-logo-transparent-12.5.png.
We edit the following fields in the config.inc.php file:
$ tlCfg-> logo_login = 'file with your logo.png'; - file size 231 * 56 pixels, transparent
$ tlCfg-> logo_navbar = 'file with your logo.png'; - file size 116 * 28 pixels, transparent
Now on the login page, in the main menu of the TestLink menu, your company login will appear in the reports.
Translation of some parts of the UI
In the config.inc.php file, you can make a translation for the text used in the description of tests that are automatically created for the requirements.
You need to do a translation for the text provided by these fields:
$ tlCfg-> req_cfg-> testcase_summary_prefix
$ tlCfg-> req_cfg-> testcase_summary_prefix_with_title_and_version
Roles
You can edit roles in TestLink itself, i.e. create new and change opportunities provided for each of the roles.
In general, setting up roles is worth a separate article.
But, for example, make sure that the Show Test Cases Assigned to me option is enabled for almost all roles.
Details about localization in Russian
The test link includes localization in Russian.
The problem is that approximately 40% of the user interface elements are not translated into Russian there or for which I would like to change the translation.
Therefore, you can do additional translation work. Unfortunately, not all interface elements are programmed so that the translation for them is in one file.
Therefore, even after a full translation of the text from the custom_strings.txt file, there will be elements that are not translated into Russian.
What you need to do to translate the UI part into Russian (and any other) language:
1) Go to the directory /opt/testlink-1.9.11-0/apps/testlink/htdocs/locale/ru_RU (if we use Russian for UI) on the server with Test Link
2) Copy the files custom_strings.txt.example and strings.txt to your PC
3) Copy from strings.txt to custom_strings.txt.example data
4) Make the necessary translation in the custom_strings.txt.example file - ATTENTION !!! BEFORE EDITION BEGINNING, IT IS NECESSARY TO MAKE A VERIFICATION REFERRED AFTER THIS SEQUENCE OF STEPS!
5) Rename custom_strings.txt.example to custom_strings.txt
6) Copy the custom_strings.txt file to the /opt/testlink-1.9.11-0/apps/testlink/htdocs/locale/ru_RU directory on the server with Test Link
Before editing any test link configuration files, do the following:
1) Open the file in edit mode.
2) Change the file encoding mode to UTF-8. This step must be performed after each opening of the file for editing!
3) Now you can edit and save the result.
Porting tests from Excel to TestLink
New versions of Excel do not support (in any way!) The XML format that TestLink understands.
Therefore, for porting is used external software, distributed free of charge.
The program is called EX-converter.
This is free software. Here is his page: sourceforge.net/projects/ex-converter/
The program works under MS Windows.
Read the documentation
Go to TestLink. The bottom left will be the Documentation element. Choose the right documents and read (in English). There is, among other things, a user guide and a TestLink setup guide.
Once again, links to useful
testlink.org
bitnami.com/stack/testlink/installer
winscp.net/eng/docs/lang:ru
Source: https://habr.com/ru/post/234633/
All Articles