Skip to content

Config json explained

Jump to bottom
msporna edited this page Jan 7, 2019 · 7 revisions

Config.json is a file that instrument_client needs in order to insert probes into code of application from which coverage is being obtained.

  • "config_ver":3, read only
  • "last_revision":1.2019, read only
  • "instrument_server_url": "http://localhost:5000", url to server where instrument_server is running, localhost:5000 is a default
  • "source_root_absolute_path": "", angular=src folder | unity=Scripts folder | other: root
  • "web_routes_available": [], applies to angular and javascript apps - routes that can be visited within app
  • "source_to_exclude":[], list of all sources that should not be considered when gathering coverage. Wildcards are not supported currently, only list of specific files. Only names,not paths.
  • "android_lava_helper_namespace": , namespace pointing to Lava Helper's 'lava' folder within your project - used to import LavaHelper into other classes
  • "INJECT_MODE": "" string containing 1 of these: android,web,unity

Table of Contents

  1. How it works
  2. Initial setup
  3. Setup for Unity game
  4. Setup for Android app
  5. Setup for javascript
  6. Setup for Angular app
  7. GETTING THE COVERAGE
  8. Getting coverage for build (multiple coverage sessions consolidated
  9. Setup modules
  10. Managing tags
  11. Managing users
  12. Create and End test session automatically (CI)
  13. Instrumenting code on every iteration
  14. Coverage report explained
  15. Accessing latest report
  16. How to interpret covered lines report
  17. Config explained
  18. Settings
  19. Send custom values along with line statistics
  20. Examples
  21. Extended-CI-use-case
  22. Troubleshooting
Clone this wiki locally