> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/api-test-commons-releases/v1.3.3.md). # v1.3.3 **Release Name**: Api Test Commons Releases **Release Version:** 1.3.3 **Release Date:** 1st July, 2025 **Overview** We are pleased to announce **API Test Commons v1.3.3**, a patch release that hardens the MOSIP Functional Test Framework through watchdog-based execution control, richer reporting, stronger database utilities, automated Slack notifications, and multiple security remediation's. These improvements build on v1.3.2 and earlier 1.3.x releases to deliver faster, safer, and more observable automated test runs across MOSIP modules. **Bug Fixes** | **Bug ID** | **Description** | | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | [**MOSIP-41082**](https://mosip.atlassian.net/browse/MOSIP-41082) | Added missing charset parameter in the **Content-Type** header for URL-encoded requests. | | [**MOSIP-41183**](https://mosip.atlassian.net/browse/MOSIP-41183) | Dynamic prerequisite creation now uses the *current* timestamp, fixing failures in date-sensitive tests. | | [**MOSIP-40930**](https://mosip.atlassian.net/browse/MOSIP-40930) | Corrected SMTP mapping logic to track and verify all e-mail notifications. | | [**MOSIP-28246**](https://mosip.atlassian.net/browse/MOSIP-28246) | Removed unused variables / deprecated utilities to reduce clutter and suppress compiler warnings. | **Major Highlights (New Developments & Enhancements)** | **Area** | **Key JIRA** | **Summary** | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Watchdog Utility** | [MOSIP-40654](https://mosip.atlassian.net/browse/MOSIP-40654) | New watchdog class enforces a configurable (default 1.5 h) hard timeout to auto-terminate hung test runs; wired into **MosipTestRunner**. | | **Slack Notifications** | [MOSIP-41298](https://mosip.atlassian.net/browse/MOSIP-41298) | Post-run push notifications to Slack with environment, rig name, statistics, and MinIO report URL. | | **Inji Web Login Support** | [MOSIP-41343](https://mosip.atlassian.net/browse/MOSIP-41343) | Added helper utilities for Inji Web login flows; includes custom cookie handling. | | **Database Utilities** | [MOSIP-39053](https://mosip.atlassian.net/browse/MOSIP-39053) | Extended **DbManager** with simplified CRUD helpers for faster DB interaction. | | **Caching Improvements** | [MOSIP-31010](https://mosip.atlassian.net/browse/MOSIP-31010) | Translator#getLanguageID() now keeps an in-memory map to avoid repeated CSV loads. | | **Report Accuracy** |

MOSIP-41454
MOSIP-35628

| Rounded sub-second durations for clearer timing; reports now state when suites are skipped due to CAPTCHA enablement. | | **Security Hardening** |

MOSIP-39719
MOSIP-37503
MOSIP-40258

| Log masking for secrets / passwords, complete secret cleanup, and validation of X-XSS-Protection headers. | | **Configuration Update** | [MOSIP-40950](https://mosip.atlassian.net/browse/MOSIP-40950) | Added support for crvs.client.secret needed by CRVS scenarios. | | **Build & Publish** | [MOSIP-41940](https://mosip.atlassian.net/browse/MOSIP-41940) | Migrated to **central-publishing-maven-plugin** for smoother Maven Central releases. | **Repositories Released** | **Repository** | **Version** | | ------------------- | ---------------------------------------------------------------------------- | | **apitest-commons** | [v1.3.3](https://github.com/mosip/mosip-functional-tests/tree/release-1.3.x) | **Pre-requisites** Ensure the following before executing automated tests: * **Java:** 21 * **Maven:** 3.9.6 or higher * **Lombok:** Installed and configured **For Windows** * Git Bash 2.18.0 or higher * settings.xml needs to be present in the .m2 folder. **For Linux** * settings.xml placed in both: * Maven conf folder * /usr/local/maven/conf **Repository & Build** **Access Test Automation Code** 1. **From Browser** 2. Clone or download the repository as a zip file from[ GitHub](https://github.com/mosip/mosip-functional-tests). 3. Unzip the contents. 4. Continue with the steps below from a terminal (Linux) or command prompt (Windows). 5. **From Git Bash** 6. Copy the git link: 7. On your local system, open Git Bash at any location. 8. Run the following command: git clone **Build Test Automation Code** 1. Navigate to the apitest-commons directory: cd ../apitest-commons 2. Build the project: mvn clean install -Dgpg.skip=true -Dmaven.gitcommitid.skip=true Ensure all pre-requisites are met before running the updated tests. Refer to the updated **README** file for detailed setup and execution instructions. For any issues or further assistance, please open an issue on GitHub. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/api-test-commons-releases/v1.3.3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.