0% found this document useful (0 votes)
27 views

Testing Workflow: Objective: Test If All Services Are Working (For A Given Request, Endpoints Return

The document outlines a testing workflow to ensure all services are working individually in a given environment. It involves specifying an environment, building code repositories for that environment, running unit tests to create reports for each component, deploying to boxes for the environment, waiting for services to start up, and running API tests to check responses from different requests and create reports. It does not provide details on how to test PUT, POST, and DELETE endpoints through API tests.

Uploaded by

Prakhar Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
27 views

Testing Workflow: Objective: Test If All Services Are Working (For A Given Request, Endpoints Return

The document outlines a testing workflow to ensure all services are working individually in a given environment. It involves specifying an environment, building code repositories for that environment, running unit tests to create reports for each component, deploying to boxes for the environment, waiting for services to start up, and running API tests to check responses from different requests and create reports. It does not provide details on how to test PUT, POST, and DELETE endpoints through API tests.

Uploaded by

Prakhar Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Testing Workflow

Objective: Test if all services are working (For a given request, endpoints return
response as expected) individually in an environment
1. Specify {env}
2. Build all git repos from {env} branch [config: list of git urls] Assumptions:
All git branches have a branch named {env} {env} branch has env specific
properties
3. Run junits*, Create report for each component If succesfull, upload to
nexus ??
4. deploy to boxes of {env} [config: map(full component name, sys_path(if
jar)/ tomcat_manger_api_string )] Assumptions: runtime requirements
are satisfied on target boxes
5. Poll/Wait until all services are up (check by hitting endpoint / parse logs
??)
6. Run job of Api tests [check responses from different request], create reports.

Queries:

How to Test PUT/POST/DELETE endpoints ?

You might also like