04 - Greenspector Studio - Linux - Android

update 29 aug 2024

Everything is now ready to install Greenspector tools for measures. Two tools are necessary:

  • Greenspector CLI - To run measurement on our testbench

  • Testrunner - To run measurement on local device

  • DashboardCampaign - To generate a result's dashboard

Preparation

Please create two folder for each use:

$HOME

â”” GreenspectorTools

├ Measure

â”” Dashboard

A different location can be chosen. In this case, please remember it for the PATH section of this document.

Download

These tools are available on Greenspector Core Saas, in module section.

To download the right version of these tools, we have to know the Linux OS version. For this purpose, open a terminal as previously explained and use:

uname -m

Two output can be expected:

  • i386 for 32-bit version

  • x86_64 for 64-bit version

Browse in module section and download each required part at the right location:

  • In Measure folder:

    • greenspector-X.XX.X_linux-XXX in Greenspector CLI

    • testrunner-X.X.X_linux-XXX in Test Runner

  • In Dashboard folder:

    • dashboardCampagne-X.X.X_linux-XXX in Dashboard campaign CLI

    • assets.tar in Definition Assets

    • definition.yml in Definition file Template

    • config.yml in Config file Template

Rename executables for easier use:

  • greenspector-X.XX.X_linux-XXX to gspt

  • testrunner-X.X.X_linux-XXX to testrunner

  • dashboardCampagne-X.X.X_linux-XXX to dashboardCampagne

Unzip assets.tar

Path

As usual to be able to launch these tools from every folder, we have to add them to PATH.

Add the following lines in the .bashrc file:

export PATH=$HOME/GreenspectorTools/Measure:$PATH export PATH=$HOME/GreenspectorTools/Dashboard:$PATH

Run the command source ~/.bashrc to apply changes.

Verification

Use the following commands to verify the installation:

gspt -v testrunner -v

These commands should show the current version of Greenspector CLI and Testrunner.

DashboardCampagne doesn't have version check for now.

So enter its command without argument:

You should see log messages.