Integration of test scripts developed into the Framework

What Integration Means

Once individual test scripts exist (e.g., API tests written with Rest Assured), they need to be plugged into the framework's shared structure — using its base classes, utilities, and configuration rather than duplicating logic.

Typical Steps

• Move common setup/teardown logic into a shared base test class that other test classes extend.
• Replace hardcoded values (like URLs or credentials) with calls to the framework's configuration reader.
• Register new tests in the appropriate TestNG group or suite file.

Why This Step Matters

Proper integration ensures every new test automatically benefits from the framework's reporting, logging, and reusable components, rather than existing as an isolated script.