...
Configuration
The only rule is that on start-up Karate expects a file called karate-config.js to exist on the
classpath and contain a JavaScript function. The function is expected to return a JSON object
and all keys and values in that JSON object will be made available as script variables. And
that's all there is to Karate configuration! You can easily get the value of the current
'environment' or 'profile', and then set up 'global' variables using some simple JavaScript.Global Variables:
Non-JSON values such as Java object references or JS functions are supported only if they are
at the "root" of the JSON returned from karate-config.js.Switching the Mutiple Environment:
Karate is flexible, you can easily overwrite config variables within each individual test-script -
which is very convenient when in dev-mode or rapid-prototyping and also environment
specific Config will be taken care here. external config file having host name, credentials, stateCode, cityCode, etc.Test Properties:
Contains all properties related to Tests cases like Feature file, Http requests, responses, test
data etc.Framework Properties:
Contains All properties related to Karate framework like pom.xml, YAML files, .md files etc.Reports:
We can generate default BDD cucumber reports and we can integrate reporting plugins.Tests:
Contains test scenarios feature files with execution tags, Assertions etc.MDMS call:
Fetching the test data from MDMS and using in tests.
...