Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourRedGreen
titleIn ProgressUP TO DATE

Table of Contents
maxLevel2

Applications

You can check the applications list and their properties. You can either edit an application by clicking on the pen or delete archive it by clicking on the trash bin folder (the pen and the trash bin folder appear when you move your cursor on the application line).

To add a new application which is not yet included in the list, just click on the button "Add an application".

If you click on an application, you can view its detailed analysis, spanned in 5 tabs:

Dashboard

The Dashboard tab gives you a summary of your application’s results. You can select the version of the application by clicking in the box right next to its name.

Eco-score

The global eco-score is an indicator of your level of eco-design ecodesign for the application. It is the average of eco-scores for the following domains : Network, Client resources.

All eco-scores are noted between 0 and 100. To get the highest score, it is important to launch all analyses.

Two metrics are indicated with Just below the eco-score :is indicated the evolution of eco-score since the previous version of the application

;the average of eco-scores of your business

.

Eco-score by domain

  • Network: evaluate the level of eco-design of exchanged requests between client and server. It is calculated by analyzing the requests and their content. To get a score, it is necessary to initiate measures with the TestRunner by launch measurements either with the Power Test Cloud/Bench or with the Test Runner (and activating the http_request option).
  • Client resources: evaluate if your application is client-side resources efficient. It is calculated by the client-side resources consumption (energy, CPU, memory…​). To get a score, it is necessary to initiate measures launch measurements either with the Power Test Cloud/Bench or with the TestRunner Test Runner on a smartphonedevice.

Improvements summary

This is a small bar graph summarizing the number of rules by priority. You can filter the rules in the Improvements table below by clicking on the corresponding priority. To display again all the rules, select "All the rules" in the select box on at the top right of the Improvements table.

Resources impact

This graph summarizes the impact of the your application's usage on the mobile device.

Improvements

This is the list of all the rules that were checked during analysis: rules that are correctly respected appear in green, whereas rules that are violated appear in yellow, orange or red. They are prioritized according to earnings you can get. Each rule is classified according to its domain. The number next to the domain corresponds to its eco-score.

Each rule is associated with a priority, a score and a gain.

  • The Priority priority is an indicator to help you to prioritize your work and is directly correlated with the gain.

  • The Score score is an indicator of how good the rule is verified on the application. Adding up all scores of a specific domain gives this domain’s eco-score.

  • The Gain gain is the difference between the maximum score and the actual score. It is correlated with the priority to help you choosing which rules you should work on at first place.

Consumed resources

Summary A summary of consumed resources for the consumed following metrics of :

Mobile url

: Platform Discharge, Process Data, Process Memory, Process CPU

  • PC url : Platform Energy

  • Mobile apk : Platform Discharge, Process Data, Process Memory, Process CPU

  • .

    The difference between the last two versions of the metric is shown on the left side of the value.

    Meter

    On the left menu, search and sort your test cases by Meter metrics. When you click on a test case you can check its detailed analysis.

    Metrics are sorted by metrics associated to the entire platform and metrics associated to a process or a thread (More more on metrics here).

    You can verify the stability of your measures (See Getting Startedmore details here).

    Test Results

    You will find the result results of your functional tests (pass passed or failfailed).

    Budgets

    Budget can be set for each test and each metrices (See Getting Started for usage)You have the possibility to configure budgets in order to better analyze and monitor the quality of your application: the page Configure the budgets issues in more detail this feature.

    Evolution

    In the evolution tab you can compare on a graphic the average measures result by versions. On the test case list, you can check their detailed analysis between two versions.

    Schedule a Test

    StatuscolourBluetitleComing Soon

    Modules

    StatuscolourBluetitleComing Soon

    Rules

    For each tab (Android, CSS, HTML, Java and PHP) you can use the search tool in order to

    .


    Benchmark

    This tab allows you to launch benchmark tests.

    1. Select your application: the name of an application which is already created in GREENSPECTOR. You can also add an application by clicking on Add an application.
    2. Version: the version of the application version which is already created in GREENSPECTOR. You can also add a version by clicking on Add a version.
    3. Select the environment for the test: choose one of the available devices on the Power Test Cloud (or in your Power Test Bench).
    4. Website or Mobile app: select whether you want to test a website or a mobile Android application.
    5. URL: an URL pointing to the website or the APK you want to test.
    6. Iterations: number of executions of the tests.
    7. Chrome or Firefox : select the browser on which to run the measures in case you are testing a website.

    Tests tracking

    This tab lists all the tests you have launched.

    • Pending: jobs that are in pending state (device not available).
    • Running: jobs in progress.
    • Finished: jobs that are done.

    Once finished, several information on the finished list are available:

    • Ended at: date and time at which the test was finished.
    • Status: failed or finished, in case of a failure, fly over the exclamation mark icon to get more details.
    • Tests Passed: status of the functionnal tests.

    Modules

    Find here all the GREENSPECTOR modules you can download.


    Rules

    Here, more detailed information about software ecodesign good practices. Rules are organised in 3 domains: code, network and client resources. For the code domain, you can also filter the rules by language.

    Each rule has its Energy Gain, Memory Gain, Performance and Difficultyincludes an estimate of potential gains in energy, memory, performance, as well as an indication of the difficulty to apply it.


    Administration

    Test times

    Status
    colourBlue
    titleComing Soon

    License

    Status
    colourBlue
    titleComing Soon

    Users

    This option on the menu on the left lets you left menu bar allows you to manage the current users, add a new one or delete a current one.

    Related articles


    Filter by label (Content by label)
    showLabelsfalse
    max5
    spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@185bfa9a
    showSpacefalse
    sortmodified
    reversetrue
    typepage
    cqllabel = "webinterface" and type = "page" and space = "DOCUMENTATION"
    labelskb-how-to-article