DIGIT Test Automation Framework Setup guide

Read me - https://github.com/egovernments/test-automation/tree/master/api-automation

Steps to make changes in the script

1. Clone the Repo

2. git clone https://github.com/egovernments/test-automation.git

3. Collect all the APIs that are new/updated added as part of the sprint.

4. Create a local branch to make changes in the script

5. Check if the endpoints are already available then reuse them, if not add the endpoints in - common.yaml file.

6. Check if the URL is already defined then reuse, if not add/define the URL in the - karate-config.js file.

7. Check which services the API belongs to (municipal/core/business services), if already similar tests are available then try adding in the existing file.

8. If it is a new API then create the below files under the specified folders

9. pretest - to run the API, validating the response codes and storing the response

   • ex: @autoEscalate - /core-services/pretest/escalate protest.feature

   • tests - to create individual tests based on the pretest and validate the results based on test scenarios.

   • ex: @autoEscalate_PGR_01 - /core-services/tests/escalate.feature

   • requestPayload - to create the payload (JSON payload) for the pretests

   • ex: escalate.json - /core-services/escalate/escalate.json

   • constants - to create constant data like success, error messages, and other data that can be called in the tests.

   • ex: escalate.yaml - /core-services/constants/escalate.yaml

   • testData - to create test data (like pdf or other files) for the tests.

   • ex: dummyTestdata.rtf -/core-services/testData/dummyTestdata.rtf

10. Create/update the necessary files as mentioned above. for pretest and tests add relevant @tags

11. Run the @newtags. Refer to the readme.file for detailed setup, steps to run the individual @tags