Please enable JavaScript.
Coggle requires JavaScript to display documents.
RMV API Automation (Why REST Assured? (Redable, Maintainable, Open source,…
RMV API Automation
Why REST Assured?
Redable
Maintainable
Open source
Easy integration with Java
No additional code to setup HTML connection
RMV Automation stack
Maven
TestNG
Multiple SetUp/tearDown levels
TestNG XML's configuration
Tests parameterization
Reporting capability
Java
REST Assured
Structure of the API test
GET/PUT/POST/DELETE call to receive API response
SSO call
Parsing JSON and asserting Data
SSO Call using REST Assured
asserting 200 + getting CusID
POST call to env specific URL
passing API key in header and XML in body
GET/PUT/POST/DELETE API call
asserting 200
returning response as JSON object
API call to specific URL
Parsing JSON and asserting Data
Asserting Data
Excel data
Hardcoded data
XML passed data
Longing output
Creating JSON Object of specific nested API
CI/CD pipeline
Jenkins job
https://jenkins.morningstar.com/job/MIM/view/Automation/job/RM5%20Automation%20Smoke%20Test%20API/
Runs as downstream job of MIM.RM.API build
Java/Maven project easy to integrate
Rerporting
Customized Listener for providing reports
HTML reports are constructed and distributed to the list of recepients
Using TestNG reporting capability
Standarts
coding standarts
Pull requests
project structure