TestLink is a web-based test management system that facilitates software quality assurance. It is developed and maintained by Teamtest. The platform offers support for test cases, test suites, test plans, test projects and user management, as well as various reports and statistics.

https://testlink.org/

$ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-testlink/master/docker-compose.yml
$ docker-compose up

WARNING: This is a beta configuration, currently unsupported.

Get the raw URL pointing to the kubernetes.yml manifest and use kubectl to create the resources on your Kubernetes cluster like so:

$ kubectl create -f https://raw.githubusercontent.com/bitnami/bitnami-docker-testlink/master/kubernetes.yml

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.

To run this application you need Docker Engine 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

Running TestLink with a database server is the recommended way. You can either use docker-compose or run the containers manually.

This is the recommended way to run TestLink. You can use the following docker compose template:

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - 'mariadb_data:/bitnami/mariadb'
  testlink:
    image: 'bitnami/testlink:latest'
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - 'testlink_data:/bitnami/testlink'
      - 'apache_data:/bitnami/apache'
      - 'php_data':/bitnami-php'
    depends_on:
      - mariadb
    environment:
      TESTLINK_USERNAME: admin
      TESTLINK_PASSWORD: verysecretadminpassword
      TESTLINK_EMAIL: [email protected]

volumes:
  mariadb_data:
    driver: local
  testlink_data:
    driver: local
  apache_data:
    driver: local
  php_data:
    driver: local

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

1. Create a new network for the application and the database:

$ docker network create testlink-tier

2. Start a MariaDB database in the network generated:

$ docker run -d --name mariadb -e ALLOW_EMPTY_PASSWORD=yes --net=testlink-tier bitnami/mariadb

Note: You need to give the container a name in order for TestLink to resolve the host

3. Run the TestLink container:

$ docker run -d -p 80:80 --name testlink --net=testlink-tier bitnami/testlink

Then you can access your application at http://your-ip/

If you remove every container and volume all your data will be lost, and the next time you run the image the application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence of the Testlink deployment, the above examples define docker volumes namely mariadb_data, php_data apache_data and testlink_data. The TestLink application state will persist as long as these volumes are not removed.

Note! If you have already started using your application, follow the steps on backing up to pull the data from your running container down to your host.

This requires a minor change to the docker-compose.yml template previously shown:

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - '/path/to/mariadb-persistence:/bitnami/mariadb'
  testlink:
    image: 'bitnami/testlink:latest'
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - '/path/to/testlink-persistence:/bitnami/testlink'
      - '/path/to/apache-persistence:/bitnami/apache'
     -  '/path/to/php-persistence:/bitnami/php'
    depends_on:
      - mariadb

In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:

1. Create a network (if it does not exists):

$ docker network create testlink-tier

2. Create a MariaDB container with host volume:

$ docker run -d --name mariadb -e ALLOW_EMPTY_PASSWORD=yes \
  --net testlink-tier \
  --volume /path/to/mariadb-persistence:/bitnami/mariadb \
  bitnami/mariadb:latest

Note: You need to give the container a name in order for TestLink to resolve the host

3. Run the TestLink container:

$ docker run -d -p 80:80 -p 443:443 --name testlink \
  --net testlink-tier \
  --volume /path/to/testlink-persistence:/bitnami/testlink \
  --volume /path/to/apache-persistence:/bitnami/apache \
  --volume /path/to/php-persistence:/bitnami/php \
  bitnami/testlink:latest

Bitnami provides up-to-date versions of MariaDB and TestLink, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the TestLink container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

1. Get the updated images:

$ docker pull bitnami/testlink:latest

2. Stop your container

• For docker-compose: $ docker-compose stop testlink
• For manual execution: $ docker stop testlink

3. (For non-compose execution only) Create a backup if you have not mounted the testlink folder in the host.

4. Remove the currently running container

• For docker-compose: $ docker-compose rm -v testlink
• For manual execution: $ docker rm -v testlink

5. Run the new image

• For docker-compose: $ docker-compose start testlink
• For manual execution (mount the directories if needed): docker run --name testlink bitnami/testlink:latest

When you start the testlink image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:

• For docker-compose add the variable name and value under the application section:

testlink:
  image: bitnami/testlink:latest
  ports:
    - '80:80'
    - '443:443'
  environment:
    - TESTLINK_PASSWORD=my_password

• For manual execution add a -e option with each variable and value:

$ docker run -d -p 80:80 -p 443:443 --name testlink
  -e TESTLINK_PASSWORD=my_password \
  --net testlink-tier \
  --volume /path/to/testlink-persistence:/bitnami/testlink \
  --volume /path/to/apache-persistence:/bitnami/apache \
  --volume /path/to/php-persistence:/bitnami/php \
  bitnami/testlink:latest

Available variables:

• TESTLINK_USERNAME: TestLink admin username. Default: user
• TESTLINK_PASSWORD: TestLink admin password. Default: bitnami
• TESTLINK_EMAIL: TestLink admin email. Default: [email protected]
• TESTLINK_LANGUAGE: TestLink default language. Default: en_US
• MARIADB_USER: Root user for the MariaDB database. Default: root
• MARIADB_PASSWORD: Root password for the MariaDB.
• MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
• MARIADB_PORT: Port used by MariaDB server. Default: 3306

To configure TestLink to send email using SMTP you can set the following environment variables:

• SMTP_ENABLE: Enable SMTP mail delivery.
• SMTP_HOST: SMTP host.
• SMTP_PORT: SMTP port.
• SMTP_USER: SMTP account user.
• SMTP_PASSWORD: SMTP account password.
• SMTP_CONNECTION_MODE: SMTP connection mode, ssl or tls.

This would be an example of SMTP configuration using a GMail account:

• docker-compose:

testlink:
  image: bitnami/testlink:latest
  ports:
    - '80:80'
    - '443:443'
  environment:
    - SMTP_ENABLE=true
    - SMTP_HOST=smtp.gmail.com
    - SMTP_PORT=587
    - [email protected]
    - SMTP_PASSWORD=your_password
    - SMTP_CONNECTION_MODE=tls

• For manual execution:

$ docker run -d -p 80:80 -p 443:443 --name testlink \
  -e SMTP_ENABLE=true \
  -e SMTP_HOST=smtp.gmail.com -e SMTP_PORT=587 \
  -e [email protected] \
  -e SMTP_PASSWORD=your_password \
  -e SMTP_CONNECTION_MODE=tls \
  --net testlink-tier \
  --volume /path/to/testlink-persistence:/bitnami/testlink \
  --volume /path/to/apache-persistence:/bitnami/apache \
  --volume /path/to/php-persistence:/bitnami/php \
  bitnami/testlink:latest

To backup your application data follow these steps:

1. Stop the running container:

• For docker-compose: $ docker-compose stop testlink
• For manual execution: $ docker stop testlink

2. Copy the TestLink data folder in the host:

$ docker cp /path/to/testlink-persistence:/bitnami/testlink

To restore your application using backed up data simply mount the folder with TestLink data in the container. See persisting your application section for more info.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version ($ docker version)
• Output of $ docker info
• Version of this container ($ echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Most real time communication happens in the #containers channel at bitnami-oss.slack.com; you can sign up at slack.oss.bitnami.com.

Discussions are archived at bitnami-oss.slackarchive.io.

Copyright 2016 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.