testlink是给编程人员完成的软件，可以很方便的就能进行软件测试，测试的效率高

# TestLink 1.9.19 Metonic cycle - Read me ## Contents 1. [Introduction](#1-introduction) 2. [Release notes / Critical Configuration Notes](2-release-notes--critical-configuration-notes) 3. [System Requirements](#3-system-requirements---server) 4. [Installation & SECURITY](#4-installation--security) 5. [Upgrade and Migration](#5-upgrade-and-migration) 6. [TestLink Team](#6-testlink-team) 7. [Bug Reports and Feedback](#7-bug-reports-and-feedback) 8. [Supporting our work](#8-supporting-our-work) 9. [Regarding forum usage](#9-regarding-forum-usage-wwwtestlinkorg) www.testlink.org 10. [Changes](#10-changes) 11. [Testlink & FreeTest](#11-testlink--freetest) 12. [Security](#12-security) 13. [JIRA DB interface changes](#13-jira-db-interface-changes) 14. [People/Companies supporting TestLink](#14-peoplecompanies-supporting-testlink) 15. [Use forum.testlink.org](#15-use-forumtestlinkorg) 16. [User cries: I WANT HELP !!!](#16-user-cries-i-want-help-) 17. [Use Mantis documentation](#17-use-mantis-documentation) 18. [Link to GITORIOUS COMMITS](#18-link-to-gitorious-commits) ## 1. Introduction TestLink is a web based test management and test execution system. It enables quality assurance teams to create and manage their test cases as well as to organize them into test plans. These test plans allow team members to execute test cases and track test results dynamically. TestLink is a GPL licensed open source project. All of the source code behind TestLink is freely available for download via [SourceForge][sou] or [GitHub][hub]. If you are interested in contributing to the TestLink effort feel free to contact us. There is no hidden fee - 100% free for using! In an ideal world, testing would be a pretty straightforward process. A test team takes the product requirements, writes a test specification document, reviews the tests, and then runs them all for each version of the product. The team is composed of full-time staff, and everyone knows exactly what is expected of them. In practice, few organisations have that luxury. There is not time to run all the tests on every product version - especially on fix-releases that need to be rolled out quickly. Requirements are constantly changing, and the tests have to be changed in step. Test staff come and go. There are misunderstandings over who was supposed to run which tests, so some get missed. Management suddenly wants a status update at seven in the evening. In these situations you need the support of a test management tool, such as TestLink. The purpose of TestLink is to answer questions such as: - For which requirements do we still need to write or update test cases? - Which tests do you want me to run for this version? - How much progress have we made on testing this release? - Which test cases are currently failing, and what are the errors? - On which version was this group of test cases last run, and is it time we ran them again? - And ultimately: is this version of the product fit for release? TestLink helps you to keep the test process under control. It forms a repository for requirements and test cases, and relates these to builds, platforms and staff. You allocate tests to staff who carry them out and record the results. A wide variety of reports provide information on what has been done and what still needs to be done. ## 2. Release notes / CRITICAL Configuration Notes This release contains bugfixes and enhancement for 1.9.18 See CHANGELOG file for detailed list of issues fixed. Give a look also to: https://github.com/TestLinkOpenSourceTRMS/testlink-code/wiki https://github.com/TestLinkOpenSourceTRMS/testlink-documentation/wiki ### CRITICAL PHP.INI Settings #### max_input_vars **Available since PHP 5.3.9. Default value: 1000** If you are going to have test plans with more than 100 test cases, it will be CRITICAL to increase this value in order to avoid issues such as CRASH or MALFUNCTION when adding test cases to test plan. See [this forum post on max_input_vars][frm] or [this mantis issue][bug] for details. #### memory_limit **Default value: 128MB** If you are going to re-import an XML file to update its test case data, the system might run out of memory. [The original issue][mem] was resolved with a `memory_limit` value of 256MB. ### Oauth configuration Since 1.9.17 there is new authorization method - using OAuth providers. Authentication against multiple oauth providers is supported. Currently it configured to work with Google OAuth and Github, but you can add any OAuth server that support protocol 2.0 and 2-step authentication. #### There are some restrictions in using OAuth: 1. OAuth should not be specified as Default Authentication method 2. If user does not exist in DB and you try to login through oauth - userID will be saved to db with special auth type. And for secure reasons you can't logon via regular email/password into Testlink. 3. If user already exists in DB then you can logon via password or via OAuth #### To configure OAuth you should set in config provided by OAuth provider oauth_client_id - id of OAuth program oauth_client_secret - secret code oauth_grant_type - authorization_code is default value oauth_url - url of OAuth server token_url - url for getting token oauth_profile - url of OAuth profile page oauth_grant_type, oauth_scope - specific parameters for several OAuth providers. They are not necessary ### Changes on LDAP CONFIGURATION Since 1.9.16 authentication against [Multiple LDAP Servers][ldap] is supported. To implement this feature configuration parameters have been changed, as explained here: #### TestLink Version < 1.9.16 $tlCfg->authentication['method'] = 'LDAP'; $tlCfg->authentication['ldap_server'] = 'ldap.xyz.com'; $tlCfg->authentication['ldap_port'] = '389'; $tlCfg->authentication['ldap_version'] = '3'; $tlCfg->authentication['ldap_root_dn'] = 'dc=xyz,dc=com'; $tlCfg->authentication['ldap_bind_dn'] = 'uid=tl,ou=staff,dc=xyz,dc=com'; $tlCfg->authentication['ldap_bind_passwd'] = 'XYZw'; $tlCfg->authentication['ldap_tls'] = false; // true -> use tls #### TestLink Version >= 1.9.16 $tlCfg->authentication['method'] = 'LDAP'; $tlCfg->authentication['ldap'][1]['ldap_server'] = 'ldap.xyz.com'; $tlCfg->authentication['ldap'][1]['ldap_port'] = '389'; $tlCfg->authentication['ldap'][1]['ldap_version'] = '3'; $tlCfg->authentication['ldap'][1]['ldap_root_dn'] = 'dc=xyz,dc=com'; $tlCfg->authentication['ldap'][1]['ldap_bind_dn'] = 'uid=tl,ou=staff,dc=xyz,dc=com'; $tlCfg->authentication['ldap'][1]['ldap_bind_passwd'] = 'XYZw'; $tlCfg->authentication['ldap'][1]['ldap_tls'] = false; ## 3. System Requirements - server Server environment should consist of: - web-server: Apache 2.x - PHP > 5.5 It will be better if you use PHP 7.2.x - DBMS: MySQL 5.7.x / MariaDB 10.1.x, Postgres 9.x, MS-SQL 201x Supported client web-browsers: - Firefox - Internet Explorer 9.x or greater - Chrome ATTENTION: we have not enough resources to test on all kind of browsers. Right now development is done using Chrome & Firefox. ## 4. Installation & SECURITY The following details the basic steps for installation on any system. Instructions may seem unix-centric but should work on Windows systems. Barring complications, it should take you about 10-20 minutes to install, configure, and start using TestLink. Short summary: 1. Transfer files 2. Uncompress files 3. Launch web based installer 1. First, transfer the file to your web-server using whatever method you like best (ftp, scp, etc). You will need to telnet/ssh into the server machine for the next steps. 2. Next, untar/gunzip it to the directory that you want. The usual command is (1 step): tar zxvf <filename.tar.gz> OR (2 steps): gunzip <filename.tar.gz> tar xvf <filename.tar> Total Commander, Winzip, and other programs should also be able to handle decompression of the archive. At this point you may want to rename