feat: initial release

.gitignore

+/target/
+!.mvn/wrapper/maven-wrapper.jar
+
+### STS ###
+.apt_generated
+.classpath
+.factorypath
+.project
+.settings
+.springBeans
+.sts4-cache
+
+### IntelliJ IDEA ###
+.idea
+*.iws
+*.iml
+*.ipr
+
+### NetBeans ###
+/nbproject/private/
+/build/
+/nbbuild/
+/dist/
+/nbdist/
+/.nb-gradle/

.gitlab-ci.yml

+include:
+  - project: 'Orange-OpenSource/tbc/tools/gitlab-ci'
+    ref: 'master'
+    file: '/templates/validation.yml'
+  - project: 'Orange-OpenSource/tbc/kicker'
+    ref: 'master'
+    file: '/templates/validation.yml'
+  - project: 'Orange-OpenSource/tbc/bash'
+    ref: '1.0.0'
+    file: 'templates/gitlab-ci-bash.yml'
+
+stages:
+  - build
+  - publish
+
+variables:
+  GITLAB_CI_FILES: "templates/gitlab-ci-puppeteer.yml"
+  BASH_SHELLCHECK_FILES: "*.sh"
+
+extract-script:
+  stage: .pre
+  script:
+    - echo "#!/bin/bash" > script.sh
+    - sed -n '/BEGSCRIPT/,/ENDSCRIPT/p' "$GITLAB_CI_FILES" | sed 's/^  //' >> script.sh
+    - export LC_ALL=C.UTF-8
+  artifacts:
+    when: always
+    name: extracted template script
+    expire_in: 1h
+    paths:
+      - script.sh
+
+release:
+  image: node:12
+  stage: publish
+  before_script:
+    - npm install -g semantic-release @semantic-release/gitlab @semantic-release/exec @semantic-release/git
+  script:
+    - semantic-release
+  only:
+    refs:
+      - master
+    variables:
+      - $TMPL_RELEASE_ENABLED

.gitlab/issue_templates/bug_report.md

+## Describe the bug
+
+(Describe the problem clearly and concisely.)
+
+
+## Expected behavior
+
+(Describe the expected behavior clearly and concisely.)
+
+
+## Actual behavior
+
+(Describe the actual behavior clearly and concisely.)
+
+
+## Logs and/or screenshots
+
+(Join any relevant logs and/or screenshot. Please use code blocks (```) to format console output, logs, and code.)
+
+
+## Context & Configuration
+
+Link to a project, pipeline or job facing the bug: (please provide one if possible)
+
+The issue was reproduced using:
+
+* Version of the template: (type in the version)
+* GitLab server(s): (Was it gitlab.com? A self-managed server? Which version? CE / EE? Which license?)
+* GitLab runner(s): (type in any relevant information about the GitLab runner(s) you used)
+
+
+Here is the `.gitlab-ci.yml` file:
+
+```yaml
+# Add your .gitlab-ci.yml here, if applicable and useful.
+
+```
+
+(If useful, list configured GitLab CI project and/or group variables.)
+
+Configured GitLab CI project or group variables:
+
+* `VARIABLE_1`
+* `VARIABLE_2`
+* ...
+
+
+(Finally add any possible additional useful context info here.)
+
+
+
+
+/label ~"kind/bug" ~"status/needs-investigation"

.gitlab/issue_templates/feature_request.md

+## Description
+
+(Describe the feature clearly and concisely.)
+
+## Implementation ideas
+
+(If you have any implementation ideas, they can go here.)
+(Any design change proposal could be also discussed on the _to be continuous_ Google Group: https://groups.google.com/g/tbc-dev.)
+
+
+/label ~"kind/enhancement" ~"status/needs-investigation"

.gitlab/merge_request_templates/bug_fix.md

+## Presentation
+
+(Necessarily link to an issue. If it doesn't exist, please create one.)
+
+Fixes #999
+
+## Checklist
+
+* Documented:
+    * [ ] `README.md` reflects any job, variable or whichever visible change
+    * [ ] `kicker.json` reflects any job, variable or whichever visible change
+* Tested & examplified:
+    * [ ] (url to a project sample successfully proving the merge request fixes the issue)
+
+/label ~"kind/fix"

.gitlab/merge_request_templates/new_feature.md

+## Presentation
+
+(Necessarily link to an issue. If it doesn't exist, please create one.)
+
+Closes #999
+
+
+## Checklist
+
+* General:
+    * [ ] use [rules](https://docs.gitlab.com/ee/ci/yaml/#rules) instead of [only/except](https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-advanced)
+    * [ ] optimized [cache](https://docs.gitlab.com/ee/ci/caching/) configuration (wherever applicable)
+* Publicly usable:
+    * [ ] untagged runners
+    * [ ] no proxy configuration but support `http_proxy`/`https_proxy`/`no_proxy`
+    * [ ] no custom CA certificate(s) but supports `$CUSTOM_CA_CERTS` or `$DEFAULT_CA_CERTS` to declare custom CA certificate(s)
+    * [ ] internet hostnames/urls only
+* Used Docker images:
+    * [ ] **public** images
+    * [ ] **official** images (when possible)
+    * [ ] `latest` tag (when possible)
+* Documented:
+    * [ ] `README.md` documents the new feature
+    * [ ] `kicker.json` describes the new feature
+* Tested & examplified:
+    * [ ] (url to a project sample successfully using the new feature)
+
+
+/label ~"kind/enhancement"

.releaserc.yml

+plugins: [
+  "@semantic-release/commit-analyzer",
+  "@semantic-release/release-notes-generator",
+  "@semantic-release/gitlab",
+  [
+    "@semantic-release/exec",
+    {
+      "prepareCmd": "./bumpversion.sh \"${lastRelease.version}\" \"${nextRelease.version}\" \"${nextRelease.type}\""
+    }
+  ],
+  [
+    "@semantic-release/git",
+    {
+      "assets": ["*.md", "templates/*.yml"]
+    }
+  ]
+]
+branches:
+  - "master"
+tagFormat: "${version}"
\ No newline at end of file

CONTRIBUTE.md

+# Contributors guide
+
+**Want to contribute? Great!**
+We try to make it easy, and all contributions, even the smaller ones, are more than welcome.
+This includes bug reports, fixes, documentation, examples...
+But first, read this page (including the small print at the end).
+
+## Legal
+
+All original contributions to _to be continuous_ are licensed under the
+[GNU Lesser General Public License](https://www.gnu.org/licenses/lgpl-3.0.html),
+version 3.0 or later.
+
+All contributions are subject to the [Developer Certificate of Origin](https://developercertificate.org/) (DCO).
+The DCO is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project.
+The DCO text is also included verbatim in the [DCO.txt](DCO.txt) file in the root directory of the repository.
+
+Contributors **must** _sign-off_ that they adhere to these requirements by adding a `Signed-off-by` line to commit messages, as shown below:
+
+```text
+This is the commit message
+
+Signed-off-by: John Dev <john.dev@developer.example.org>
+```
+
+Git has a handy [`-s` command line option](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) to append this automatically to your commit message:
+
+```bash
+$ git commit -s -m 'This is the commit message'
+```
+
+## Reporting an issue
+
+This project uses GitLab issues to manage the issues.
+
+Before creating an issue:
+
+1. upgrade your project to the latest released template version, and check whether your bug is still present,
+2. have a look in the opened issues if your problem is already known/tracked, and possibly contribute to the thread with your own information.
+
+If none of the above was met, open an issue directly in GitLab, select the appropriate issue template and fill-in each section when applicable.
+
+## Submitting a code change
+
+### Git Setup
+
+Before contributing, make sure you have set up your Git authorship correctly:
+
+```bash
+git config --global user.name "Your Full Name"
+git config --global user.email your.email@example.com
+```
+
+### Workflow
+
+All submissions, including submissions by project members, need to be reviewed before being merged.
+
+To contribute:
+
+1. Create an issue describing the bug or enhancement you want to propose (select the right issue template).
+2. Make sure the issue has been reviewed and agreed.
+3. Create a Merge Request, from your **own** fork (see [forking workflow](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) documentation).
+   Don't hesitate to mark your MR as `Draft` as long as you think it's not ready to be reviewed.
+
+### Git Commit Conventions
+
+In addition to being signed-off according the [Developer Certificate of Origin](https://developercertificate.org/) (see above),
+Git commits in _to be continuous_ shall be:
+
+1. **atomic** (1 commit `=` 1 and only 1 _thing_),
+2. **semantic** (using [semantic-release commit message syntax](https://semantic-release.gitbook.io/semantic-release/#commit-message-format)).
+
+You'll find extensive information about Git commit conventions on the [reference documentation website](https://orange-opensource.gitlab.io/tbc/doc/dev/workflow/#git-commit-guidelines).
+
+### Coding Guidelines
+
+The extensive _to be continuous_ coding guidelines can be found on the [reference documentation website](https://orange-opensource.gitlab.io/tbc/doc/dev/guidelines/).

DCO.txt

+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
\ No newline at end of file

LICENSE.txt

+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
\ No newline at end of file

README.md

+# GitLab CI template for Puppeteer
+
+This project implements a generic GitLab CI template for running [Puppeteer](https://pptr.dev/) functional tests. Puppeteer is a browser automation API. You can integrate it with any Javascript testing framework (such as [Jest](https://jestjs.io/), [Mocha](https://mochajs.org/), etc) and run your Puppeteer scripts with a headless Chromium
+
+## Usage
+
+In order to include this template in your project, add the following to your `gitlab-ci.yml`:
+
+```yaml
+include:
+  - project: 'Orange-OpenSource/tbc/puppeteer'
+    ref: '1.0.0'
+    file: '/templates/gitlab-ci-puppeteer.yml'
+
+# Pipeline steps
+stages:
+  - acceptance # required by Puppeteer template
+  # TODO: add all other required stages
+```
+
+## `puppeteer` job
+
+This job starts [Puppeteer](https://pptr.dev/) (functional) tests.
+
+It uses the following variable:
+
+| Name                  | description                              | default value     |
+| --------------------- | ---------------------------------------- | ----------------- |
+| `PUPPETEER_IMAGE`     | The Docker image used to run [Puppeteer](https://hub.docker.com/r/buildkite/puppeteer) | `buildkite/puppeteer:latest` |
+| `PUPPETEER_PROJECT_DIR` | The Puppeteer project directory (containing `package.json`) | `.` |
+| `PUPPETEER_TEST_EXTRA_ARGS`  | Testing framework extra options based on [Jest](https://jestjs.io/docs/en/cli) | _none_ |
+| `REVIEW_ENABLED`      | Set to enable Puppeteer tests on review environments (dynamic environments instantiated on development branches) | _none_ (disabled) |
+
+### Unit tests report integration
+
+ Puppeteer test reports are [integrated to Gitlab by generating JUnit reports](https://docs.gitlab.com/ee/ci/junit_test_reports.html).
+
+### Jest
+
+Here we use [Jest](https://jestjs.io/) as testing framework and obviously choose [jest-junit](https://www.npmjs.com/package/jest-junit) to generate Junit test reports
+
+Add the package as a development dependency:
+
+```bash
+npm install --save-dev jest jest-junit
+```
+
+and update `package.json` to add scripts section to invoke jest command as below:
+
+```js
+"scripts": {
+  "puppeteer": "jest"
+}
+```
+
+:warning: In your puppeteer scripts, take all screenshots under `puppeteer/screenshots`.
+
+By default, reports are generated with file name `TEST-REPORT.xml` under `puppeteer/reports` directory. You can override these values by using variables `JEST_JUNIT_OUTPUT_DIR` and `JEST_JUNIT_OUTPUT_NAME` accordingly.
+
+### Puppeteer `baseUrl` auto evaluation
+
+By default, the Puppeteer template auto-evaluates a [baseUrl setting with Jest](https://jestjs.io/docs/en/configuration#globals-object)
+(i.e. the variable pointing at server under test) by looking either for a `$environment_url` variable or for an
+`environment_url.txt` file.
+
+Therefore if an upstream job in the pipeline deployed your code to a server and propagated the deployed server url,
+either through a [dotenv](https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#artifactsreportsdotenv) variable `$environment_url`
+or through a basic `environment_url.txt` file, then the Puppeteer test will automatically be run on this server.
+
+:warning: all our deployment templates implement this design. Therefore even purely dynamic environments (such as review
+environments) will automatically be propagated to your Puppeteer tests.
+
+If you're not using a smart deployment job, you may still explicitly declare the `PUPPETEER_BASE_URL` variable (but that
+will be unfortunately hardcoded to a single server).

bumpversion.sh

+#!/usr/bin/env bash
+
+function log_info() {
+  >&2 echo -e "[\\e[1;94mINFO\\e[0m] $*"
+}
+
+function log_warn() {
+  >&2 echo -e "[\\e[1;93mWARN\\e[0m] $*"
+}
+
+function log_error() {
+  >&2 echo -e "[\\e[1;91mERROR\\e[0m] $*"
+}
+
+# check number of arguments
+if [[ "$#" -le 2 ]]; then
+  log_error "Missing arguments"
+  log_error "Usage: $0 <current version> <next version>"
+  exit 1
+fi
+
+curVer=$1
+nextVer=$2
+relType=$3
+
+if [[ "$curVer" ]]; then
+  log_info "Bump version from \\e[33;1m${curVer}\\e[0m to \\e[33;1m${nextVer}\\e[0m (release type: $relType)..."
+
+  # replace in README
+  sed -e "s/ref: '$curVer'/ref: '$nextVer'/" README.md > README.md.next
+  mv -f README.md.next README.md
+
+  # replace in template and variants
+  for tmpl in templates/*.yml
+  do
+    sed -e "s/\"$curVer\"/\"$nextVer\"/" "$tmpl" > "$tmpl.next"
+    mv -f "$tmpl.next" "$tmpl"
+  done
+else
+  log_info "Bump version to \\e[33;1m${nextVer}\\e[0m (release type: $relType): this is the first release (skip)..."
+fi

kicker.json

+{
+  "name": "Puppeteer",
+  "description": "GitLab CI template for running [Puppeteer](https://pptr.dev/) functional tests",
+  "template_path": "templates/gitlab-ci-puppeteer.yml",
+  "kind": "acceptance",
+  "variables": [
+    {
+      "name": "PUPPETEER_IMAGE",
+      "description": "The Docker image used to run [Puppeteer](https://hub.docker.com/r/buildkite/puppeteer)",
+      "default": "buildkite/puppeteer:latest"
+    },
+    {
+      "name": "PUPPETEER_PROJECT_DIR",
+      "description": "The Puppeteer project directory (containing `package.json`)",
+      "default": "."
+    },
+    {
+      "name": "PUPPETEER_TEST_EXTRA_ARGS",
+      "description": "Testing framework extra options based on [Jest](https://jestjs.io/docs/en/cli)",
+      "advanced": true
+    },
+    {
+      "name": "REVIEW_ENABLED",
+      "description": "Set to enable Puppeteer tests on review environments (dynamic environments instantiated on development branches)",
+      "type": "boolean"
+    }
+  ]
+}

templates/gitlab-ci-puppeteer.yml

+# =========================================================================================
+# Copyright (C) 2021 Orange
+#
+# This program is free software; you can redistribute it and/or modify it under the terms 
+# of the GNU Lesser General Public License as published by the Free Software Foundation; 
+# either version 3 of the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
+# without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See the GNU Lesser General Public License for more details.
+#
+# You should have received a copy of the GNU Lesser General Public License along with this 
+# program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth 
+# Floor, Boston, MA  02110-1301, USA.
+# =========================================================================================
+variables:
+  # Default Docker image (can be overriden)
+  PUPPETEER_IMAGE: "buildkite/puppeteer:latest"
+  PUPPETEER_PROJECT_DIR: "."
+  # default production ref name (pattern)
+  PROD_REF: '/^master$/'
+  # default integration ref name (pattern)
+  INTEG_REF: '/^develop$/'
+
+# allowed stages depend on your template type (see: orange-opensource.gitlab.io/tbc/doc/dev-guidelines/#stages)
+stages:
+  - acceptance
+
+.puppeteer-scripts: &puppeteer-scripts |
+  # BEGSCRIPT
+  set -e
+
+  function log_info() {
+      echo -e "[\\e[1;94mINFO\\e[0m] $*"
+  }
+
+  function log_warn() {
+      echo -e "[\\e[1;93mWARN\\e[0m] $*"
+  }
+
+  function log_error() {
+      echo -e "[\\e[1;91mERROR\\e[0m] $*"
+  }
+
+  function assert_defined() {
+    if [[ -z "$1" ]]
+    then
+      log_error "$2"
+      exit 1
+    fi
+  }
+
+  function install_ca_certs() {
+    certs=$1
+    if [[ -z "$certs" ]]
+    then
+      return
+    fi
+
+    # import in system
+    if echo "$certs" >> /etc/ssl/certs/ca-certificates.crt
+    then
+      log_info "CA certificates imported in \\e[33;1m/etc/ssl/certs/ca-certificates.crt\\e[0m"
+    fi
+    if echo "$certs" >> /etc/ssl/cert.pem
+    then
+      log_info "CA certificates imported in \\e[33;1m/etc/ssl/cert.pem\\e[0m"
+    fi
+  }
+
+  # maybe install NPM dependencies if package.json file found
+  function maybe_install_deps() {
+    if [[ -f "package-lock.json" ]]
+    then
+      log_info "\\e[33;1mpackage-lock.json\\e[0m file found: install dependencies..."
+      npm ci --cache .npm --prefer-offline
+    elif [[ -f "package.json" ]]
+    then
+      log_warn "\\e[33;1mpackage.json\\e[0m file found but no \\e[33;1mpackage-lock.json\\e[0m: use Puppeteer with default dependencies"
+      log_warn "If your tests require additional dependencies, please create \\e[33;1mpackage-lock.json\\e[0m with 'npm install' and commit it"
+    else
+      log_warn "No \\e[33;1mpackage.json\\e[0m file found: choose testing framework Jest or Mocha to use with Puppeteer"
+    fi
+  }
+
+  function eval_base_url() {
+    # shellcheck disable=SC2154
+    if [[ -n "$environment_url" ]]
+    then
+      PUPPETEER_BASE_URL="$environment_url"
+      export PUPPETEER_BASE_URL
+      log_info "Upstream \$environment_url variable set: use baseUrl \\e[33;1m$PUPPETEER_BASE_URL\\e[0m"
+    elif [[ -f environment_url.txt ]]
+    then
+      PUPPETEER_BASE_URL=$(cat environment_url.txt)
+      export PUPPETEER_BASE_URL
+      log_info "Upstream environment_url.txt file found: use baseUrl \\e[33;1m$PUPPETEER_BASE_URL\\e[0m"
+    else
+      log_info "No upstream environment url found: leave default"
+    fi
+  }
+
+  function get_latest_template_version() {
+    tag_json=$(wget -T 5 -q -O - "$CI_API_V4_URL/projects/Orange-OpenSource%2Ftbc%2F$1/repository/tags?per_page=1" || echo "")
+    echo "$tag_json" | sed -rn 's/^.*"name":"([^"]*)".*$/\1/p'
+  }
+
+  function check_for_update() {
+    template="$1"
+    actual="$2"
+    latest=$(get_latest_template_version "$template")
+    if [[ -n "$latest" ]] && [[ "$latest" != "$actual" ]]
+    then
+      log_warn "\\e[1;93m=======================================================================================================\\e[0m"
+      log_warn "\\e[93mThe template \\e[32m$template\\e[93m:\\e[33m$actual\\e[93m you're using is not up-to-date: consider upgrading to version \\e[32m$latest\\e[0m"
+      log_warn "\\e[93m(set \$TEMPLATE_CHECK_UPDATE_DISABLED to disable this message)\\e[0m"
+      log_warn "\\e[1;93m=======================================================================================================\\e[0m"
+    fi
+  }
+
+  if [[ -z "$TEMPLATE_CHECK_UPDATE_DISABLED" ]]; then check_for_update puppeteer "1.0.0"; fi
+
+  # ENDSCRIPT
+
+puppeteer:
+  image:
+    name: "$PUPPETEER_IMAGE"
+    entrypoint: [""]
+  cache:
+    key: ${CI_COMMIT_REF_SLUG}
+    paths:
+      - $PUPPETEER_PROJECT_DIR/.npm/
+  services:
+    - name: "$CI_REGISTRY/orange-opensource/tbc/tools/tracking:master"
+      command: ["--service", "puppeteer", "1.0.0"]
+  stage: acceptance
+  before_script:
+    - *puppeteer-scripts
+    - install_ca_certs "${CUSTOM_CA_CERTS:-$DEFAULT_CA_CERTS}"
+    # retrieve server url to test from 'environment_url.txt' file
+    - eval_base_url
+    - cd "$PUPPETEER_PROJECT_DIR"
+    - maybe_install_deps
+    # create directories
+    - mkdir -p puppeteer/screenshots
+    - mkdir -p puppeteer/reports
+    # set junit report dir and fileName
+    - export JEST_JUNIT_OUTPUT_DIR="puppeteer/reports"
+    - export JEST_JUNIT_OUTPUT_NAME="TEST_REPORT.xml"
+  script:
+    # maybe activate DEBUG traces
+    - 'if [[ "$TRACE" ]]; then export DEBUG=puppeteer:*; fi'
+    # run puppeteer tests
+    - npm run puppeteer -- --config '{"globals":{"URL":"$PUPPETEER_BASE_URL"}}' --reporters=default --reporters=jest-junit $PUPPETEER_TEST_EXTRA_ARGS
+  artifacts:
+    name: "$CI_JOB_NAME artifacts from $CI_PROJECT_NAME on $CI_COMMIT_REF_SLUG"
+    when: always
+    paths:
+      - $PUPPETEER_PROJECT_DIR/puppeteer/reports/
+      - $PUPPETEER_PROJECT_DIR/puppeteer/screenshots/
+    reports:
+      junit:
+        - $PUPPETEER_PROJECT_DIR/puppeteer/reports/TEST_REPORT.xml
+    expire_in: 1 day
+  rules:
+    # exclude merge requests
+    - if: $CI_MERGE_REQUEST_ID
+      when: never
+    # exclude tags
+    - if: $CI_COMMIT_TAG
+      when: never
+    # on production and integration branch(es): auto (on_success)
+    - if: '$CI_COMMIT_REF_NAME =~ $PROD_REF || $CI_COMMIT_REF_NAME =~ $INTEG_REF'
+    # on other branch(es): manual & non-blocking if $REVIEW_ENABLED set
+    - if: $REVIEW_ENABLED
+      when: manual
+      allow_failure: true