Feacker: Feature usage tracker

FEACKER is a Javascript a plug-in to leverage pure::variants on the search of Feature Usage Tracking. FEACKER injects feature-based Google Analytics hits into Software Product Lines developed using pure::variants.

Dependencies

A pure::variants installation is needed to work with FEACKER. Refer to: pure::variants download page

A Google Analytics account with a Universal Property created.

For developers, your system need Node16.13.0

Instalation and Usage

Project downloading and setup

1. Download the last release from releases
2. Store it in a permanent folder.
3. Download GA script and add it to your project source code following GA guides (GA doc)

Configuring FEACKER in pure::variants

For each pure::variants project in which you want to use FEACKER conduct the following steps:

1. Open the transformation dialog and create a new transformation

2. Add a javascript transformation and set FEACKER.js (select it from the UI menu) as the script file. Before doing that, you have to include the FEACKER.js and FeaturesInVariant.js files in your project root inside a folder named "script".

3. In a new transformation add the created transformation and also add the pure:variants File processing transformation using the Reuse transformation option.

4. Change the variant output of the Feacker script path to /your_path/${variant}-FEACKER

5. Change the input variant path of pure::variants fileProcessing transformation to /your_path/${variant}-FEACKER

Running FEACKER

1. At development time:

   • Create the FEACKER.yaml model at the project root. Here you can find an (example of a defined yaml model)
   • Create a GA property counterpart in your GA account. To this aim, you have to login in your account and access the administration panel. Then you will find a "+ Create Property" option:

2. At product configuration time

   • For each variant to be tracked, run the FEACKER transformation previously configured.

3. At the time the product variant is used

   • The log counterpart starts being populated by event triggered throughout

4. At analysis time

   • Access Google Analytics, and display the log counterpart using appropriate dashboards

Running example

If you want to test FEACKER in an already configured project you can download it from: https://github.com/onekin/WACline/tree/featureTracking/WACline