Skip to content

Latest commit

 

History

History
81 lines (62 loc) · 1.87 KB

ProjectSpecificCustomizations.md

File metadata and controls

81 lines (62 loc) · 1.87 KB
Raw

Back to main README

Project specific customisations

Configuration

Follow this project structure for your test implementation.

You will need to update the following files from ./src/test:

Update config.properties

Update Test Data file

By default, kendo looks for the test data file here - ./src/test/java/test_data.json. You can override it by providing the path to this file in config.properties with the name - TEST_DATA_FILE_NAME or providing this as an environment variable

Specify the test-data for each environment that you are going to run the test. The structure is:

```
{
  "local": {
    "env": {
      "baseUrl": "https://github.com",
    }
  },
  "prod": {
    "env": {
      "baseUrl": "https://github.com",
    }
  }
}
```

For each environment, you can specify user-specific data as well. Ex:

```
{
  "local": {
    "env": {
      "baseUrl": "https://github.com",
    },
    "anand": {
      "city": "Pune" 
    },
    "naresh": {
      "city": "Mumbai"
    }
  },
  "prod": {
    "env": {
      "baseUrl": "https://github.com",
    }
    "anand": {
      "city": "Mumbai" 
    },
    "naresh": {
      "city": "Pune"
    }
  }
}
```

karate-config.js

The default karate-config.js is provided. This file will automatically load the test-data file. You can add your custom configuration between the sections:

/* Begin update of configuration based on project needs */

...
...
...

/* End update of configuration based on project needs */

Update reportportal.properties

Back to main README