uniform_resource (table) Content
| 01JZ7K652Z9QK16WZC40N9WREK | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-security-testing/test-plan/qf-plan.md | bb59a62f7d220efbafa6c509e38dc65aac49610c | --- id: PLN-006 name: "Security Test Plan" description: "This test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines." created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["security testing"] related_requirements: ["REQ-101", "REQ-102"] --- This test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance. ## Objectives - **Validate Security Controls**: Test APIs against the OWASP API Security Top 10 to ensure secure authentication, authorization, and data protection. - **Identify Vulnerabilities**: Detect and report critical vulnerabilities, including injection flaws, broken access controls, and security misconfigurations. - **Mitigate Risks**: Provide actionable remediation steps to address identified risks. ## Scope of Testing 1. **Authentication & Authorization**: Validate API keys, JWT tokens, role-based access controls, and protection against unauthorized access. 2. **Data Protection**: Ensure encryption in transit (TLS/HTTPS) and assess API responses for sensitive data exposure. 3. **Input Validation**: Test inputs for injection attacks (SQLi, XSS) and ensure strict validation of data formats. 4. **Error Handling**: Verify that error responses do not disclose sensitive internal information (e.g., stack traces). 5. **Cross-Origin Resource Sharing (CORS)**: Assess configurations to allow only trusted domains. ## Approach ### Testing Methodology - **Black-box Testing**: Simulate external attacks without internal system knowledge. - **Gray-box Testing**: Test with partial knowledge of the system to identify hidden vulnerabilities. - **Dynamic Analysis**: Use tools like OWASP ZAP and Burp Suite for runtime vulnerability analysis. ### Tools & Resources - **Tools**: OWASP ZAP, Postman, Burp Suite, Wireshark, custom scripts. - **Standards**: OWASP API Security Top 10, OWASP Cheat Sheets. ## Entry & Exit Criteria ### Entry Criteria - API endpoints are documented and accessible. - Test environment is set up with appropriate user roles and credentials. - Necessary tools and resources are available for testing. ### Exit Criteria - All high and critical vulnerabilities are mitigated or formally accepted as risks. - APIs meet OWASP guidelines and organizational security standards. - Test execution report is delivered, and findings are addressed. ## Deliverables 1. **API Security Testing Report**: Categorized by severity (Critical, High, Medium, Low). 2. **Recommendations**: Actionable steps to remediate identified vulnerabilities. ## References - [OWASP API Security Top 10](https://owasp.org/www-project-api-security/) - [OWASP Cheat Sheet Series](https://cheatsheetseries.owasp.org/) - [Burp Suite Documentation](https://portswigger.net/burp) | md | 3126 | 2024-12-26 17:32:22 UTC | { "frontMatter": "---\nid: PLN-006\nname: \"Security Test Plan\"\ndescription: \"This test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines.\"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"security testing\"]\nrelated_requirements: [\"REQ-101\", \"REQ-102\"]\n---\n", "body": "\nThis test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance.\n\n## Objectives\n\n- **Validate Security Controls**: Test APIs against the OWASP API Security Top 10 to ensure secure authentication, authorization, and data protection.\n- **Identify Vulnerabilities**: Detect and report critical vulnerabilities, including injection flaws, broken access controls, and security misconfigurations.\n- **Mitigate Risks**: Provide actionable remediation steps to address identified risks.\n\n## Scope of Testing\n\n1. **Authentication & Authorization**: \n Validate API keys, JWT tokens, role-based access controls, and protection against unauthorized access.\n2. **Data Protection**: \n Ensure encryption in transit (TLS/HTTPS) and assess API responses for sensitive data exposure.\n3. **Input Validation**: \n Test inputs for injection attacks (SQLi, XSS) and ensure strict validation of data formats.\n4. **Error Handling**: \n Verify that error responses do not disclose sensitive internal information (e.g., stack traces).\n5. **Cross-Origin Resource Sharing (CORS)**: \n Assess configurations to allow only trusted domains.\n\n## Approach\n\n### Testing Methodology\n\n- **Black-box Testing**: Simulate external attacks without internal system knowledge.\n- **Gray-box Testing**: Test with partial knowledge of the system to identify hidden vulnerabilities.\n- **Dynamic Analysis**: Use tools like OWASP ZAP and Burp Suite for runtime vulnerability analysis.\n\n### Tools & Resources\n\n- **Tools**: OWASP ZAP, Postman, Burp Suite, Wireshark, custom scripts.\n- **Standards**: OWASP API Security Top 10, OWASP Cheat Sheets.\n\n## Entry & Exit Criteria\n\n### Entry Criteria\n\n- API endpoints are documented and accessible.\n- Test environment is set up with appropriate user roles and credentials.\n- Necessary tools and resources are available for testing.\n\n### Exit Criteria\n\n- All high and critical vulnerabilities are mitigated or formally accepted as risks.\n- APIs meet OWASP guidelines and organizational security standards.\n- Test execution report is delivered, and findings are addressed.\n\n## Deliverables\n\n1. **API Security Testing Report**: \n Categorized by severity (Critical, High, Medium, Low).\n2. **Recommendations**: \n Actionable steps to remediate identified vulnerabilities.\n\n## References\n\n- [OWASP API Security Top 10](https://owasp.org/www-project-api-security/)\n- [OWASP Cheat Sheet Series](https://cheatsheetseries.owasp.org/)\n- [Burp Suite Documentation](https://portswigger.net/burp)\n", "attrs": { "id": "PLN-006", "name": "Security Test Plan", "description": "This test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "security testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } } | { "id": "PLN-006", "name": "Security Test Plan", "description": "This test plan defines the strategy, scope, and objectives for conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "security testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K652ZJF5SD34KKNA15N9Q | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-security-testing/qf-suite.md | edfad8d5122d0b6142c3a3454d630dac45bc8ab3 | --- id: SUT-006 projectId: PRJ-001 name: "Security Test Suite" description: "This test suite conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance." created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["security testing"] --- ## Objectives - **Validate Security Controls**: Test APIs against the OWASP API Security Top 10 to ensure secure authentication, authorization, and data protection. - **Identify Vulnerabilities**: Detect and report critical vulnerabilities, including injection flaws, broken access controls, and security misconfigurations. - **Mitigate Risks**: Provide actionable remediation steps to address identified risks. ## Scope of Testing 1. **Authentication & Authorization**: Validate API keys, JWT tokens, role-based access controls, and protection against unauthorized access. 2. **Data Protection**: Ensure encryption in transit (TLS/HTTPS) and assess API responses for sensitive data exposure. 3. **Input Validation**: Test inputs for injection attacks (SQLi, XSS) and ensure strict validation of data formats. 4. **Error Handling**: Verify that error responses do not disclose sensitive internal information (e.g., stack traces). 5. **Cross-Origin Resource Sharing (CORS)**: Assess configurations to allow only trusted domains. ## Approach ### Testing Methodology - **Black-box Testing**: Simulate external attacks without internal system knowledge. - **Gray-box Testing**: Test with partial knowledge of the system to identify hidden vulnerabilities. - **Dynamic Analysis**: Use tools like OWASP ZAP and Burp Suite for runtime vulnerability analysis. ### Tools & Resources - **Tools**: OWASP ZAP, Postman, Burp Suite, Wireshark, custom scripts. - **Standards**: OWASP API Security Top 10, OWASP Cheat Sheets. ## Entry & Exit Criteria ### Entry Criteria - API endpoints are documented and accessible. - Test environment is set up with appropriate user roles and credentials. - Necessary tools and resources are available for testing. ### Exit Criteria - All high and critical vulnerabilities are mitigated or formally accepted as risks. - APIs meet OWASP guidelines and organizational security standards. - Test execution report is delivered, and findings are addressed. ## Deliverables 1. **API Security Testing Report**: Categorized by severity (Critical, High, Medium, Low). 2. **Recommendations**: Actionable steps to remediate identified vulnerabilities. ## References - [OWASP API Security Top 10](https://owasp.org/www-project-api-security/) - [OWASP Cheat Sheet Series](https://cheatsheetseries.owasp.org/) - [Burp Suite Documentation](https://portswigger.net/burp) | md | 2884 | 2024-12-26 12:18:46 UTC | { "frontMatter": "---\nid: SUT-006\nprojectId: PRJ-001\nname: \"Security Test Suite\"\ndescription: \"This test suite conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance.\"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"security testing\"]\n---\n", "body": "\n## Objectives\n\n- **Validate Security Controls**: Test APIs against the OWASP API Security Top 10 to ensure secure authentication, authorization, and data protection.\n- **Identify Vulnerabilities**: Detect and report critical vulnerabilities, including injection flaws, broken access controls, and security misconfigurations.\n- **Mitigate Risks**: Provide actionable remediation steps to address identified risks.\n\n## Scope of Testing\n\n1. **Authentication & Authorization**: \n Validate API keys, JWT tokens, role-based access controls, and protection against unauthorized access.\n2. **Data Protection**: \n Ensure encryption in transit (TLS/HTTPS) and assess API responses for sensitive data exposure.\n3. **Input Validation**: \n Test inputs for injection attacks (SQLi, XSS) and ensure strict validation of data formats.\n4. **Error Handling**: \n Verify that error responses do not disclose sensitive internal information (e.g., stack traces).\n5. **Cross-Origin Resource Sharing (CORS)**: \n Assess configurations to allow only trusted domains.\n\n## Approach\n\n### Testing Methodology\n\n- **Black-box Testing**: Simulate external attacks without internal system knowledge.\n- **Gray-box Testing**: Test with partial knowledge of the system to identify hidden vulnerabilities.\n- **Dynamic Analysis**: Use tools like OWASP ZAP and Burp Suite for runtime vulnerability analysis.\n\n### Tools & Resources\n\n- **Tools**: OWASP ZAP, Postman, Burp Suite, Wireshark, custom scripts.\n- **Standards**: OWASP API Security Top 10, OWASP Cheat Sheets.\n\n## Entry & Exit Criteria\n\n### Entry Criteria\n\n- API endpoints are documented and accessible.\n- Test environment is set up with appropriate user roles and credentials.\n- Necessary tools and resources are available for testing.\n\n### Exit Criteria\n\n- All high and critical vulnerabilities are mitigated or formally accepted as risks.\n- APIs meet OWASP guidelines and organizational security standards.\n- Test execution report is delivered, and findings are addressed.\n\n## Deliverables\n\n1. **API Security Testing Report**: \n Categorized by severity (Critical, High, Medium, Low).\n2. **Recommendations**: \n Actionable steps to remediate identified vulnerabilities.\n\n## References\n\n- [OWASP API Security Top 10](https://owasp.org/www-project-api-security/)\n- [OWASP Cheat Sheet Series](https://cheatsheetseries.owasp.org/)\n- [Burp Suite Documentation](https://portswigger.net/burp)\n", "attrs": { "id": "SUT-006", "projectId": "PRJ-001", "name": "Security Test Suite", "description": "This test suite conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "security testing" ] } } | { "id": "SUT-006", "projectId": "PRJ-001", "name": "Security Test Suite", "description": "This test suite conducting security tests on APIs to ensure alignment with the OWASP API Security Top 10 2023 guidelines. The goal is to identify vulnerabilities, mitigate risks, and establish robust security measures for API endpoints, ensuring data protection and regulatory compliance.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "security testing" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6530JK01JDX4GCCXQ77Q | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-security-testing/security-testcase/TC-0026.case.md | 6fed7bfd4be3164aea3eddce10cb1fbfae20cf3f | --- FII: TC-0026 groupId: GRP-008 title: "HTTPS-001 - Ensure the API Requires HTTPS for All Connections." created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Manual" tags: ["security testing"] priority: "High" --- ### Description The API should enforce secure communication by requiring all client-server interactions to use HTTPS. This ensures that data exchanged between the client and server is encrypted, preventing interception or tampering by unauthorized parties. APIs that allow HTTP connections expose sensitive data, such as authentication credentials or personal information, to potential attackers. ### Pre-Conditions: - The API server must be accessible over both HTTP and HTTPS. - Testing tools such as Postman or cURL should be configured to make HTTP and HTTPS requests. - Ensure no network-level redirection is applied. ### Test Steps: 1. **Step 1**: Send an HTTP GET request to the API endpoint. 2. **Step 2**: Verify the server responds with a redirection (HTTP 301 or 308) to the HTTPS endpoint. 3. **Step 3**: Send an HTTPS GET request to the same endpoint. 4. **Step 4**: Verify the server responds with a 200 OK status code and the expected resource. 5. **Step 5**: Check if the response includes the Strict-Transport-Security (HSTS) header. ### Expected Result: - All HTTP requests are redirected to HTTPS with a 301 or 308 status code. - HTTPS requests successfully return the expected resource with a 200 OK status code. - The response includes a valid Strict-Transport-Security (HSTS) header. | md | 1555 | 2024-12-26 12:19:36 UTC | { "frontMatter": "---\nFII: TC-0026\ngroupId: GRP-008\ntitle: \"HTTPS-001 - Ensure the API Requires HTTPS for All Connections.\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Manual\"\ntags: [\"security testing\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThe API should enforce secure communication by requiring all client-server interactions to use HTTPS. This ensures that data exchanged between the client and server is encrypted, preventing interception or tampering by unauthorized parties. APIs that allow HTTP connections expose sensitive data, such as authentication credentials or personal information, to potential attackers.\n\n### Pre-Conditions:\n\n- The API server must be accessible over both HTTP and HTTPS.\n- Testing tools such as Postman or cURL should be configured to make HTTP and HTTPS requests.\n- Ensure no network-level redirection is applied.\n\n### Test Steps:\n\n1. **Step 1**: Send an HTTP GET request to the API endpoint.\n2. **Step 2**: Verify the server responds with a redirection (HTTP 301 or 308) to the HTTPS endpoint.\n3. **Step 3**: Send an HTTPS GET request to the same endpoint.\n4. **Step 4**: Verify the server responds with a 200 OK status code and the expected resource.\n5. **Step 5**: Check if the response includes the Strict-Transport-Security (HSTS) header.\n\n### Expected Result:\n\n- All HTTP requests are redirected to HTTPS with a 301 or 308 status code.\n- HTTPS requests successfully return the expected resource with a 200 OK status code.\n- The response includes a valid Strict-Transport-Security (HSTS) header.\n", "attrs": { "FII": "TC-0026", "groupId": "GRP-008", "title": "HTTPS-001 - Ensure the API Requires HTTPS for All Connections.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "security testing" ], "priority": "High" } } | { "FII": "TC-0026", "groupId": "GRP-008", "title": "HTTPS-001 - Ensure the API Requires HTTPS for All Connections.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "security testing" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6530G35ESWAAS7MDQ6WP | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-security-testing/security-testcase/qf-case-group.md | c86221b1c25992d93399e3341407be3a9f79d07f | --- id: GRP-008 SuiteId: SUT-006 planId: ["PLN-006"] name: "Security Test Cases" description: "API Security Testing Execution Report - OWASP Compliance" created_by: "arun-ramanan@netspective.in" created_at: "2024-11-01" tags: ["Compatability testing"] --- ## Description This documents the results of executing API security test cases based on the API Security Testing Plan, ensuring compliance with the OWASP API Security Top 10. The focus is on verifying secure authentication, authorization, data protection, and adherence to industry standards. ## Test Cases Executed 1. **Management Endpoints & Overall Authentication** 2. **Server Resource Allocation & Rate Limiting Verification** 3. **Error Handling Validation** 4. **Sensitive Data Handling** 5. **HTTP Methods Restriction** 6. **HTTP Return Code Validation** 7. **Access Control Verification** 8. **Input Validation** 9. **HTTPS Enforcement** 10. **Security Headers Validation** 11. **Security Misconfiguration** 12. **CORS Validation** ## Environment - **Test Environment:** test - **API Version:** v1.0 ## Tools Used - **Burp Suite:** Dynamic Application Security Testing & Vulnerability Scanning - **Nessus Professional:** Vulnerability Scanning - **Dirsearch:** Directory/File Bruteforcing ## Objectives - **Verify** the implementation of security controls across all API endpoints. - **Identify** any deviations from expected security behavior. - **Validate** the application of fixes for previously reported vulnerabilities. | md | 1501 | 2024-12-26 12:19:32 UTC | { "frontMatter": "---\nid: GRP-008\nSuiteId: SUT-006\nplanId: [\"PLN-006\"]\nname: \"Security Test Cases\"\ndescription: \"API Security Testing Execution Report - OWASP Compliance\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-11-01\"\ntags: [\"Compatability testing\"]\n---\n", "body": "\n## Description\n\nThis documents the results of executing API security test cases based on the API Security Testing Plan, ensuring compliance with the OWASP API Security Top 10. The focus is on verifying secure authentication, authorization, data protection, and adherence to industry standards.\n\n## Test Cases Executed\n\n1. **Management Endpoints & Overall Authentication**\n2. **Server Resource Allocation & Rate Limiting Verification**\n3. **Error Handling Validation**\n4. **Sensitive Data Handling**\n5. **HTTP Methods Restriction**\n6. **HTTP Return Code Validation**\n7. **Access Control Verification**\n8. **Input Validation**\n9. **HTTPS Enforcement**\n10. **Security Headers Validation**\n11. **Security Misconfiguration**\n12. **CORS Validation**\n\n## Environment\n\n- **Test Environment:** test\n- **API Version:** v1.0\n\n## Tools Used\n\n- **Burp Suite:** Dynamic Application Security Testing & Vulnerability Scanning\n- **Nessus Professional:** Vulnerability Scanning\n- **Dirsearch:** Directory/File Bruteforcing\n\n## Objectives\n\n- **Verify** the implementation of security controls across all API endpoints.\n- **Identify** any deviations from expected security behavior.\n- **Validate** the application of fixes for previously reported vulnerabilities.\n", "attrs": { "id": "GRP-008", "SuiteId": "SUT-006", "planId": [ "PLN-006" ], "name": "Security Test Cases", "description": "API Security Testing Execution Report - OWASP Compliance", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "Compatability testing" ] } } | { "id": "GRP-008", "SuiteId": "SUT-006", "planId": [ "PLN-006" ], "name": "Security Test Cases", "description": "API Security Testing Execution Report - OWASP Compliance", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "Compatability testing" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6530C95FMVK3KRPBAG0Q | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-security-testing/security-testcase/TC-0026.run.md | 3c4030e3c94f538667255ea1d8b41315a8e4d831 | --- FII: "TR-0026" test_case_fii: "TC-0026" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: ToDO - Notes: Not yet executed. | md | 151 | 2024-12-26 12:19:42 UTC | { "frontMatter": "---\nFII: \"TR-0026\"\ntest_case_fii: \"TC-0026\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "\n### Run Summary\n\n- Status: ToDO\n- Notes: Not yet executed.\n", "attrs": { "FII": "TR-0026", "test_case_fii": "TC-0026", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0026", "test_case_fii": "TC-0026", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K653061TE7AM5PZ5N41KX | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/test-plan/login-qf-plan.md | fdefbde86f784991b9c24f6a4f6dd058e2cdd3a0 | --- id: PLN-007 name: "Functional Login Test Plan" description: "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. " created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["compliance testing"] related_requirements: ["REQ-101", "REQ-102"] --- Ensure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ## Scope of Work The testing will cover the following key activities across 10 APIs: ### Functional Testing - Verify the accuracy of each API endpoint against defined test cases and the provided API documentation. - Validate input and response parameters, including headers and status codes. - Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios. - Confirm the correctness and completeness of the data retrieved by APIs. - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data. | md | 1047 | 2024-12-26 17:31:42 UTC | { "frontMatter": "---\nid: PLN-007\nname: \"Functional Login Test Plan\"\ndescription: \"To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. \"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"compliance testing\"]\nrelated_requirements: [\"REQ-101\", \"REQ-102\"]\n---\n", "body": "\nEnsure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.\n\n## Scope of Work\n\nThe testing will cover the following key activities across 10 APIs:\n\n### Functional Testing\n\n- Verify the accuracy of each API endpoint against defined test cases and the provided API documentation.\n- Validate input and response parameters, including headers and status codes.\n- Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios.\n- Confirm the correctness and completeness of the data retrieved by APIs.\n- Ensure APIs effectively handle edge cases like invalid serial numbers or missing data.\n", "attrs": { "id": "PLN-007", "name": "Functional Login Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } } | { "id": "PLN-007", "name": "Functional Login Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65317MSE0SS01Y0DZA70 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/test-plan/search-qf-plan.md | 303e80517b281b5b19d6ad3e2266342ce27e5d04 | --- id: PLN-008 name: "Functional Search Test Plan" description: "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. " created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["compliance testing"] related_requirements: ["REQ-101", "REQ-102"] --- Ensure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ## Scope of Work The testing will cover the following key activities across 10 APIs: ### Functional Testing - Verify the accuracy of each API endpoint against defined test cases and the provided API documentation. - Validate input and response parameters, including headers and status codes. - Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios. - Confirm the correctness and completeness of the data retrieved by APIs. - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data. | md | 1048 | 2024-12-26 12:03:38 UTC | { "frontMatter": "---\nid: PLN-008\nname: \"Functional Search Test Plan\"\ndescription: \"To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. \"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"compliance testing\"]\nrelated_requirements: [\"REQ-101\", \"REQ-102\"]\n---\n", "body": "\nEnsure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.\n\n## Scope of Work\n\nThe testing will cover the following key activities across 10 APIs:\n\n### Functional Testing\n\n- Verify the accuracy of each API endpoint against defined test cases and the provided API documentation.\n- Validate input and response parameters, including headers and status codes.\n- Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios.\n- Confirm the correctness and completeness of the data retrieved by APIs.\n- Ensure APIs effectively handle edge cases like invalid serial numbers or missing data.\n", "attrs": { "id": "PLN-008", "name": "Functional Search Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } } | { "id": "PLN-008", "name": "Functional Search Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6531DCDMAEGKJ5180YJH | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/test-plan/dashboard-qf-plan.md | 41e896e81a2568a8b4e9001966dd00ff1465b0c4 | --- id: PLN-003 name: "Functional Dashboard Test Plan" description: "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. " created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["compliance testing"] related_requirements: ["REQ-101", "REQ-102"] --- Ensure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ## Scope of Work The testing will cover the following key activities across 10 APIs: ### Functional Testing - Verify the accuracy of each API endpoint against defined test cases and the provided API documentation. - Validate input and response parameters, including headers and status codes. - Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios. - Confirm the correctness and completeness of the data retrieved by APIs. - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data. | md | 1051 | 2024-12-26 17:31:34 UTC | { "frontMatter": "---\nid: PLN-003\nname: \"Functional Dashboard Test Plan\"\ndescription: \"To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. \"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"compliance testing\"]\nrelated_requirements: [\"REQ-101\", \"REQ-102\"]\n---\n", "body": "\nEnsure the APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.\n\n## Scope of Work\n\nThe testing will cover the following key activities across 10 APIs:\n\n### Functional Testing\n\n- Verify the accuracy of each API endpoint against defined test cases and the provided API documentation.\n- Validate input and response parameters, including headers and status codes.\n- Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios.\n- Confirm the correctness and completeness of the data retrieved by APIs.\n- Ensure APIs effectively handle edge cases like invalid serial numbers or missing data.\n", "attrs": { "id": "PLN-003", "name": "Functional Dashboard Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } } | { "id": "PLN-003", "name": "Functional Dashboard Test Plan", "description": "To validate APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation. ", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65319HVWWZ2B1N7AXDG2 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0005.run-1.result.json | ca84e8ba90109e54770c3731277a0b1a5abd43f6 | { "test_case_fii": "TC-0005", "title": "Verify that the Daily Cycle Count field is present inside the Response Data.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a GET request to the `/dashboard` API endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Check the response to verify that the `Daily_Cycle_Count_Url` is present in the `extension` section of the returned JSON data.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" }, { "step": 3, "stepname": "Ensure that the corresponding value of `valueInteger` is 3 under the `Daily_Cycle_Count_Url`", "status": "passed", "start_time": "2024-12-15T08:45:13.042Z", "end_time": "2024-12-15T08:45:13.045Z" } ] } | json | 1157 | 2024-12-17 17:44:34 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K65316BB7Q81QVQ74G4GM | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0005.case.md | ef7a5fd23bfebdcb24247a424a03b06d719ebfe0 | --- FII: TC-0005 groupId: GRP-003 title: Verify that the dashboard Count field is present inside the Response Data. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Manual" tags: ["cycle-count"] priority: "High" --- ### Description This test case verifies that the API endpoint `/dashboard` returns the correct response data, specifically ensuring that the `Daily_Cycle_Count` field is present in the JSON response. ### Pre-Conditions: - The API endpoint `/dashboard` is accessible. - The API server is running and available to respond to GET requests. - Proper authentication, if required, is provided for the request. ### Test Steps: 1. **Step 1**: Send a GET request to the `/dashboard` API endpoint. 2. **Step 2**: Check the response to verify that the `Dashboard_Count_Url` is present in the `extension` section of the returned JSON data. 3. **Step 3**: Ensure that the corresponding value of `valueInteger` is 3 under the `Dashboard_Count_Url`. ### Expected Result: - If the cycle count is available, the API should return a `200` status code with the following JSON data: | md | 1117 | 2025-01-01 09:48:50 UTC | { "frontMatter": "---\nFII: TC-0005\ngroupId: GRP-003\ntitle: Verify that the dashboard Count field is present inside the Response Data.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Manual\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case verifies that the API endpoint `/dashboard` returns the correct response data, specifically ensuring that the `Daily_Cycle_Count` field is present in the JSON response.\n\n### Pre-Conditions:\n\n- The API endpoint `/dashboard` is accessible.\n- The API server is running and available to respond to GET requests.\n- Proper authentication, if required, is provided for the request.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to the `/dashboard` API endpoint.\n2. **Step 2**: Check the response to verify that the `Dashboard_Count_Url` is present in the `extension` section of the returned JSON data.\n3. **Step 3**: Ensure that the corresponding value of `valueInteger` is 3 under the `Dashboard_Count_Url`.\n\n### Expected Result:\n\n- If the cycle count is available, the API should return a `200` status code with the following JSON data:\n", "attrs": { "FII": "TC-0005", "groupId": "GRP-003", "title": "Verify that the dashboard Count field is present inside the Response Data.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0005", "groupId": "GRP-003", "title": "Verify that the dashboard Count field is present inside the Response Data.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6531GGHMTCQCBQKKDNZR | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0007.case.md | 79b4ccfb263eb9aa2974b40b00b69f0fc4b5b019 | --- FII: TC-0007 groupId: GRP-003 title: Verify that if the System Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["cycle-count"] priority: "High" --- ### Description This test case is designed to verify the behavior of the API when the "System_count" field in the response is provided with non-integer values, such as special characters, decimals, or leading zeros. The API should throw a 400 Bad Request error when the field contains invalid data. ### Pre-Conditions: - The API endpoint `/dashboard` should be functional. - The API should be accessible and return a valid JSON response. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server that the "valueInteger" field under the "System_count_Url" extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros). ### Expected Result: - The response should contain a 400 Bad Request status code. - An error message should be provided indicating that the "System_count" value is invalid. | md | 1263 | 2024-12-26 12:06:56 UTC | { "frontMatter": "---\nFII: TC-0007\ngroupId: GRP-003\ntitle: Verify that if the System Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case is designed to verify the behavior of the API when the \"System_count\" field in the response is provided with non-integer values, such as special characters, decimals, or leading zeros. The API should throw a 400 Bad Request error when the field contains invalid data.\n\n### Pre-Conditions:\n\n- The API endpoint `/dashboard` should be functional.\n- The API should be accessible and return a valid JSON response.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server that the \"valueInteger\" field under the \"System_count_Url\" extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros).\n\n### Expected Result:\n\n- The response should contain a 400 Bad Request status code.\n- An error message should be provided indicating that the \"System_count\" value is invalid.\n", "attrs": { "FII": "TC-0007", "groupId": "GRP-003", "title": "Verify that if the System Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0007", "groupId": "GRP-003", "title": "Verify that if the System Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6532AGA8RRZ1TE505SPC | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0007.run.md | cfebf75ab8115a11e8893842c39f7cafec41a9cf | --- FII: "TR-0007" test_case_fii: "TC-0007" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Failed - Notes: All steps executed successfully. | md | 168 | 2025-01-01 09:48:22 UTC | { "frontMatter": "---\nFII: \"TR-0007\"\ntest_case_fii: \"TC-0007\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "\n### Run Summary\n\n- Status: Failed\n- Notes: All steps executed successfully.\n", "attrs": { "FII": "TR-0007", "test_case_fii": "TC-0007", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0007", "test_case_fii": "TC-0007", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K653292BM8VK614KEKKDC | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0010.run.md | 1c567aecb77a4954d3cedbd180dd54ecf23bab05 | --- FII: "TR-0010" test_case_fii: "TC-0010" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0010\"\ntest_case_fii: \"TC-0010\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0010", "test_case_fii": "TC-0010", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0010", "test_case_fii": "TC-0010", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6532RBNE9Y41DBHB76CW | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0006.run-1.result.json | b50493741c2880674dc7f2a6c84cdd635289da0b | { "test_case_fii": "TC-0006", "title": "Verify that the Dashboard Count field is present inside the Response Data when sending a GET request to the /dashboard endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Inspect the response to check if the Dashboard Count field is included inside the extension array in the returned JSON data.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 923 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6532VY1MD7Q5TTT5WKJV | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0010.run-1.result.json | 77b50d5d81db788d86e3d46a36eedcba06ae19fb | { "test_case_fii": "TC-0010", "title": "Verify that the Dashboard Count in the response is greater than 0.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server response contains the `extension` field, which should include a `Dashboard_Count_Url` entry and the `valueInteger` should be greater than 0.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 918 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K65327K5W8NZC1HPCWSYT | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0009.run-1.result.json | 1653bdef4d0bb67913658e6d9e0e593bc0ca67bf | { "test_case_fii": "TC-0009", "title": "Verify that the System Count in the response is greater than 0.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server response contains the `extension` field, which should include a `System_Count_Url` entry and the `valueInteger` should be greater than 0.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 912 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6532PM4NZNEY3HMDKDAC | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/qf-case-group.md | 2a0ec055a283bc36ac13e4db6b526472834875c4 | --- id: GRP-003 SuiteId: SUT-003 planId: ["PLN-003"] name: "Dashboard Test Cases" description: "Group of test cases designed to validate the integration capabilities of Dashboard, focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met." created_by: "arun-ramanan@netspective.in" created_at: "2024-11-01" tags: ["integration testing", "data validation", "reporting"] --- ### Overview This test case group is structured to ensure the seamless functionality and reliability of dashboard by validating key integration points and performance metrics: - **Data Ingestion**: Verifying capability to handle multiple data formats (JSON, CSV, XML) without errors or data loss. - **Data Processing Integrity**: Ensuring that all ingested data is accurately processed and retains integrity throughout. - **Reporting Accuracy**: Validating that generated reports reflect the processed data accurately and meet compliance requirements. - **Performance Under Load**: Testing the system's ability to handle concurrent ingestion requests and maintain performance benchmarks. - **Automated Testing**: Facilitating integration into CI/CD pipelines for consistent testing and validation of new releases. | md | 1267 | 2024-12-27 12:43:34 UTC | { "frontMatter": "---\nid: GRP-003\nSuiteId: SUT-003\nplanId: [\"PLN-003\"]\nname: \"Dashboard Test Cases\"\ndescription: \"Group of test cases designed to validate the integration capabilities of Dashboard, focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-11-01\"\ntags: [\"integration testing\", \"data validation\", \"reporting\"]\n---\n", "body": "\n### Overview\n\nThis test case group is structured to ensure the seamless functionality and reliability of dashboard by validating key integration points and performance metrics:\n\n- **Data Ingestion**: Verifying capability to handle multiple data formats (JSON, CSV, XML) without errors or data loss.\n- **Data Processing Integrity**: Ensuring that all ingested data is accurately processed and retains integrity throughout.\n- **Reporting Accuracy**: Validating that generated reports reflect the processed data accurately and meet compliance requirements.\n- **Performance Under Load**: Testing the system's ability to handle concurrent ingestion requests and maintain performance benchmarks.\n- **Automated Testing**: Facilitating integration into CI/CD pipelines for consistent testing and validation of new releases.\n", "attrs": { "id": "GRP-003", "SuiteId": "SUT-003", "planId": [ "PLN-003" ], "name": "Dashboard Test Cases", "description": "Group of test cases designed to validate the integration capabilities of Dashboard, focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "integration testing", "data validation", "reporting" ] } } | { "id": "GRP-003", "SuiteId": "SUT-003", "planId": [ "PLN-003" ], "name": "Dashboard Test Cases", "description": "Group of test cases designed to validate the integration capabilities of Dashboard, focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "integration testing", "data validation", "reporting" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6533KVW9639737MR08RK | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0006.run.md | 0a2834db28c798de31501dc2182e917e71e28c77 | --- FII: "TR-0006" test_case_fii: "TC-0006" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0006\"\ntest_case_fii: \"TC-0006\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0006", "test_case_fii": "TC-0006", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0006", "test_case_fii": "TC-0006", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65335B18EE6W2332P2E7 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0007.run-1.result.json | c5b775c00f6c283e6390b3cfb349aa563b329b87 | { "test_case_fii": "TC-0007", "title": "Verify that if the System Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "status": "failed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server that the `valueInteger` field under the `System_count_Url` extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros).", "status": "failed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 999 | 2025-01-01 09:56:18 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K65334N3KCSQQY89B69KK | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0012.run-1.result.json | afc09e4ac90ba00e6ad2f1cd287d377b2559c699 | { "test_case_fii": "TC-0012", "title": "Verify that the response for System & Dashboard is of integer type.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server response to ensure the fields for System and Dashboard are of integer value.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 855 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6533DKTR41SZCHTDTBQA | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0012.run.md | 3cfaf60686842a5e515630219f55d3e6165d0601 | --- FII: "TR-0012" test_case_fii: "TC-0012" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0012\"\ntest_case_fii: \"TC-0012\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0012", "test_case_fii": "TC-0012", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0012", "test_case_fii": "TC-0012", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6533ZKD5J55MPT3SCR61 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0011.case.md | 3cf54a16b185b5557cb1833c39c1b8aef4fe4a1f | --- FII: TC-0011 groupId: GRP-003 title: Verify that the Dashboard Count is always greater than or equal to the System Count. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["cycle-count"] priority: "High" --- ### Description This test verifies that the Dashboard Count, which represents the total number of cycle counts done up to the current date, is always greater than or equal to the System Count, except for the first time. ### Pre-Conditions: - The `/dashboard` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The API response contains the `extension` field with the expected data structure. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `System_Count_Url` and `Dashboard_Count_Url` value. ### Expected Result: - The response body contains the proper structure: | md | 1069 | 2024-12-26 12:06:52 UTC | { "frontMatter": "---\nFII: TC-0011\ngroupId: GRP-003\ntitle: Verify that the Dashboard Count is always greater than or equal to the System Count.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test verifies that the Dashboard Count, which represents the total number of cycle counts done up to the current date, is always greater than or equal to the System Count, except for the first time.\n\n### Pre-Conditions:\n\n- The `/dashboard` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The API response contains the `extension` field with the expected data structure.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `System_Count_Url` and `Dashboard_Count_Url` value.\n\n### Expected Result:\n\n- The response body contains the proper structure:\n", "attrs": { "FII": "TC-0011", "groupId": "GRP-003", "title": "Verify that the Dashboard Count is always greater than or equal to the System Count.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0011", "groupId": "GRP-003", "title": "Verify that the Dashboard Count is always greater than or equal to the System Count.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65339ZBHBKC27HNP7FEA | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0008.case.md | 2b97864bffc1ad41b6b1525118af9b46f0314a49 | --- FII: TC-0008 groupId: GRP-003 title: Verify that if the Dashboard Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["cycle-count"] priority: "High" --- ### Description This test case is designed to verify the behavior of the API when the "Dashboard Count" field in the response is provided with non-integer values, such as special characters, decimals, or leading zeros. The API should throw a 400 Bad Request error when the field contains invalid data. ### Pre-Conditions: - The API endpoint `/dashboard` should be functional. - The API should be accessible and return a valid JSON response. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server that the "valueInteger" field under the "Dashboard_Count_Url" extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros). ### Expected Result: - The response should contain a 400 Bad Request status code. - An error message should be provided indicating that the "Dashboard Count" value is invalid. | md | 1275 | 2024-12-26 12:06:54 UTC | { "frontMatter": "---\nFII: TC-0008\ngroupId: GRP-003\ntitle: Verify that if the Dashboard Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case is designed to verify the behavior of the API when the \"Dashboard Count\" field in the response is provided with non-integer values, such as special characters, decimals, or leading zeros. The API should throw a 400 Bad Request error when the field contains invalid data.\n\n### Pre-Conditions:\n\n- The API endpoint `/dashboard` should be functional.\n- The API should be accessible and return a valid JSON response.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server that the \"valueInteger\" field under the \"Dashboard_Count_Url\" extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros).\n\n### Expected Result:\n\n- The response should contain a 400 Bad Request status code.\n- An error message should be provided indicating that the \"Dashboard Count\" value is invalid.\n", "attrs": { "FII": "TC-0008", "groupId": "GRP-003", "title": "Verify that if the Dashboard Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0008", "groupId": "GRP-003", "title": "Verify that if the Dashboard Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6534FFC663ACGD61TKGK | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0006.case.md | ff7c2be4cc0952f1b03ded70e2697823d33d7aba | --- FII: TC-0006 groupId: GRP-003 title: Verify that the Dashboard Count field is present inside the Response Data when sending a GET request to the /dashboard endpoint. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["cycle-count"] priority: "High" --- ### Description This test case ensures that the API endpoint /dashboard returns the Dashboard Count field as part of the response data. The field should be present inside the extension array, with a valid value of type integer. ### Pre-Conditions: - Ensure that the API is up and running and accessible. - The **/dashboard** endpoint should return a valid response with relevant data. ### Test Steps: 1. **Step 1**: Send a **GET** request to the `/dashboard` endpoint. 2. **Step 2**: Inspect the response to check if the **Dashboard Count** field is included inside the **extension** array in the returned JSON data. ### Expected Result: 1. If the **Dashboard Count** field is present, the response should have the following format: - Status Code: `200 OK` | md | 1072 | 2024-12-26 12:06:56 UTC | { "frontMatter": "---\nFII: TC-0006\ngroupId: GRP-003\ntitle: Verify that the Dashboard Count field is present inside the Response Data when sending a GET request to the /dashboard endpoint.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case ensures that the API endpoint /dashboard returns the Dashboard Count field as part of the response data. The field should be present inside the extension array, with a valid value of type integer.\n\n### Pre-Conditions:\n\n- Ensure that the API is up and running and accessible.\n- The **/dashboard** endpoint should return a valid response with relevant data.\n\n### Test Steps:\n\n1. **Step 1**: Send a **GET** request to the `/dashboard` endpoint.\n2. **Step 2**: Inspect the response to check if the **Dashboard Count** field is included inside the **extension** array in the returned JSON data.\n\n### Expected Result:\n\n1. If the **Dashboard Count** field is present, the response should have the following format:\n - Status Code: `200 OK`\n", "attrs": { "FII": "TC-0006", "groupId": "GRP-003", "title": "Verify that the Dashboard Count field is present inside the Response Data when sending a GET request to the /dashboard endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0006", "groupId": "GRP-003", "title": "Verify that the Dashboard Count field is present inside the Response Data when sending a GET request to the /dashboard endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6534QH2VGFB9ZXFVZT9B | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0009.run.md | 849b91f7d3bf331abd6296ad34fa56d37da871b0 | --- FII: "TR-0009" test_case_fii: "TC-0009" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0009\"\ntest_case_fii: \"TC-0009\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0009", "test_case_fii": "TC-0009", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0009", "test_case_fii": "TC-0009", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65342D5YPRJJN7ZHS3YT | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0008.run.md | a7eebddb1e66b2a032e10eafffffec673b41cd7b | --- FII: "TR-0008" test_case_fii: "TC-0008" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0008\"\ntest_case_fii: \"TC-0008\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0008", "test_case_fii": "TC-0008", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0008", "test_case_fii": "TC-0008", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6534N8EBZJ7WBRNQGPQX | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0011.run.md | 3519c683a2721ab3e0cbb1c84f00f407cd8eafaa | --- FII: "TR-0011" test_case_fii: "TC-0011" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0011\"\ntest_case_fii: \"TC-0011\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0011", "test_case_fii": "TC-0011", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0011", "test_case_fii": "TC-0011", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65359EHAD8YBZ3NCKNJE | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0005.run.md | b5e87c0c5019c999f2103597ed1b3f3aa9fd9b7e | --- FII: "TR-0005" test_case_fii: "TC-0005" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0005\"\ntest_case_fii: \"TC-0005\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0005", "test_case_fii": "TC-0005", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0005", "test_case_fii": "TC-0005", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6535PDGV5J17W1TFH7XB | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0008.run-1.result.json | d29b6e0135d42e5cb8d0ea252e2a7860f5b4d540 | { "test_case_fii": "TC-0008", "title": "Verify that if the Dashboard Count field in the response is not an integer and contains special characters, decimals, or leading zeros, it should throw an error.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server that the valueInteger field under the Dashboard_Count_Url extension contains a value that is not an integer (e.g., contains special characters, decimals, or leading zeros).", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 1045 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6535R4GPSCY52WVG5DYJ | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0012.case.md | 64b638d1c32e2e9d6ea4c73a375a12fc8721785f | --- FII: TC-0012 groupId: GRP-003 title: Verify that the response for System & Dashboard is of integer type. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Manual" tags: ["cycle-count"] priority: "High" --- ### Description This test case checks the API response to ensure that the values for "System" and "Dashboard" are returned as integer values. The API should return the expected response structure, with "valueInteger" containing integer values. ### Pre-Conditions: - The `/dashboard` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The API response contains the `extension` field with the expected data structure. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server response to ensure the fields for System and Dashboard are of integer value. ### Expected Result: - The response body contains the proper value. | md | 1029 | 2025-01-01 09:56:38 UTC | { "frontMatter": "---\nFII: TC-0012\ngroupId: GRP-003\ntitle: Verify that the response for System & Dashboard is of integer type.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Manual\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case checks the API response to ensure that the values for \"System\" and \"Dashboard\" are returned as integer values. The API should return the expected response structure, with \"valueInteger\" containing integer values.\n\n### Pre-Conditions:\n\n- The `/dashboard` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The API response contains the `extension` field with the expected data structure.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server response to ensure the fields for System and Dashboard are of integer value.\n\n### Expected Result:\n\n- The response body contains the proper value.\n", "attrs": { "FII": "TC-0012", "groupId": "GRP-003", "title": "Verify that the response for System & Dashboard is of integer type.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0012", "groupId": "GRP-003", "title": "Verify that the response for System & Dashboard is of integer type.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65357AYWXM34AEEDP94P | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0010.case.md | 09d7a6f7941260155b8ff4fa6baa990c1c0e5b37 | --- FII: TC-0010 groupId: GRP-003 title: Verify that the Dashboard Count in the response is greater than 0. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Manual" tags: ["cycle-count"] priority: "High" --- ### Description This test case ensures that the API response for the `/dashboard` endpoint includes a valid `Dashboard_Count` value that is greater than 0. The test will confirm that the value in the response is correctly populated. ### Pre-Conditions: - The `/dashboard` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The API response contains the `extension` field with the expected data structure. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `Lifetime_Cycle_Count_Url` entry and the `valueInteger` should be greater than 0. ### Expected Result: - The value of `valueInteger` should be greater than 0 (in this example, `2`). | md | 1118 | 2025-01-01 09:49:00 UTC | { "frontMatter": "---\nFII: TC-0010\ngroupId: GRP-003\ntitle: Verify that the Dashboard Count in the response is greater than 0.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Manual\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case ensures that the API response for the `/dashboard` endpoint includes a valid `Dashboard_Count` value that is greater than 0. The test will confirm that the value in the response is correctly populated.\n\n### Pre-Conditions:\n\n- The `/dashboard` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The API response contains the `extension` field with the expected data structure.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `Lifetime_Cycle_Count_Url` entry and the `valueInteger` should be greater than 0.\n\n### Expected Result:\n\n- The value of `valueInteger` should be greater than 0 (in this example, `2`).\n", "attrs": { "FII": "TC-0010", "groupId": "GRP-003", "title": "Verify that the Dashboard Count in the response is greater than 0.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0010", "groupId": "GRP-003", "title": "Verify that the Dashboard Count in the response is greater than 0.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6535YN1148RFDDE49C59 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0011.run-1.result.json | 2205aa115c6ae5244f4ed67a494b805de048781d | { "test_case_fii": "TC-0011", "title": "Verify that the Dashboard Count is always greater than or equal to the System Count.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/dashboard` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server response contains the `extension` field, which should include a `Dashboard_Count_Url` and `system_Count_Url` value.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 911 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6535MFP681PGV35NSM3A | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/dashboard-count/TC-0009.case.md | 74c8cbe25dda2a7be37dca56a04d3beef29c3ee0 | --- FII: TC-0009 groupId: GRP-003 title: Verify that the System Count in the response is greater than 0. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["cycle-count"] priority: "High" --- ### Description This test case ensures that the API response for the `/dashboard` endpoint includes a valid `System_Count` value that is greater than 0. The test will confirm that the value in the response is correctly populated. ### Pre-Conditions: - The `/dashboard` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The API response contains the `extension` field with the expected data structure. ### Test Steps: 1. **Step 1**: Send a GET request to `/dashboard` API endpoint. 2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `Daily_Cycle_Count_Url` entry and the `valueInteger` should be greater than 0. ### Expected Result: - The value of `valueInteger` should be greater than 0 (in this example, `2`). | md | 1113 | 2024-12-26 12:06:54 UTC | { "frontMatter": "---\nFII: TC-0009\ngroupId: GRP-003\ntitle: Verify that the System Count in the response is greater than 0.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"cycle-count\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case ensures that the API response for the `/dashboard` endpoint includes a valid `System_Count` value that is greater than 0. The test will confirm that the value in the response is correctly populated.\n\n### Pre-Conditions:\n\n- The `/dashboard` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The API response contains the `extension` field with the expected data structure.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/dashboard` API endpoint.\n2. **Step 2**: Review the JSON response from the server response contains the `extension` field, which should include a `Daily_Cycle_Count_Url` entry and the `valueInteger` should be greater than 0.\n\n### Expected Result:\n\n- The value of `valueInteger` should be greater than 0 (in this example, `2`).\n", "attrs": { "FII": "TC-0009", "groupId": "GRP-003", "title": "Verify that the System Count in the response is greater than 0.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } } | { "FII": "TC-0009", "groupId": "GRP-003", "title": "Verify that the System Count in the response is greater than 0.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "cycle-count" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6536DFAX8P58FZDAX5X2 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0001.run.md | af2bec0e687ab9819e4d250e93f47250d4d9863c | --- FII: "TR-0001" test_case_fii: "TC-0001" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0001\"\ntest_case_fii: \"TC-0001\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0001", "test_case_fii": "TC-0001", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0001", "test_case_fii": "TC-0001", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65362915FGEA4Y9S0XND | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/qf-case-group.md | 631f13a60df8b3a2b38139f0736a5da6d4099a2e | --- id: GRP-004 SuiteId: SUT-003 planId: ["PLN-007"] name: "Login Test Cases" description: "Group of test cases designed to validate the integration capabilities of focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met." created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["integration testing", "data validation", "reporting"] --- ### Overview This test case group is structured to ensure the seamless functionality and reliability of data by validating key integration points and performance metrics: - **Data Ingestion**: Verifying API's capability to handle multiple data formats (JSON, CSV, XML) without errors or data loss. - **Data Processing Integrity**: Ensuring that all ingested data is accurately processed and retains integrity throughout. - **Reporting Accuracy**: Validating that generated reports reflect the processed data accurately and meet compliance requirements. - **Performance Under Load**: Testing the system's ability to handle concurrent ingestion requests and maintain performance benchmarks. - **Automated Testing**: Facilitating integration into CI/CD pipelines for consistent testing and validation of new releases. | md | 1245 | 2024-12-26 17:34:42 UTC | { "frontMatter": "---\nid: GRP-004\nSuiteId: SUT-003\nplanId: [\"PLN-007\"]\nname: \"Login Test Cases\"\ndescription: \"Group of test cases designed to validate the integration capabilities of focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.\"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"integration testing\", \"data validation\", \"reporting\"]\n---\n", "body": "\n### Overview\n\nThis test case group is structured to ensure the seamless functionality and reliability of data by validating key integration points and performance metrics:\n\n- **Data Ingestion**: Verifying API's capability to handle multiple data formats (JSON, CSV, XML) without errors or data loss.\n- **Data Processing Integrity**: Ensuring that all ingested data is accurately processed and retains integrity throughout.\n- **Reporting Accuracy**: Validating that generated reports reflect the processed data accurately and meet compliance requirements.\n- **Performance Under Load**: Testing the system's ability to handle concurrent ingestion requests and maintain performance benchmarks.\n- **Automated Testing**: Facilitating integration into CI/CD pipelines for consistent testing and validation of new releases.\n", "attrs": { "id": "GRP-004", "SuiteId": "SUT-003", "planId": [ "PLN-007" ], "name": "Login Test Cases", "description": "Group of test cases designed to validate the integration capabilities of focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "integration testing", "data validation", "reporting" ] } } | { "id": "GRP-004", "SuiteId": "SUT-003", "planId": [ "PLN-007" ], "name": "Login Test Cases", "description": "Group of test cases designed to validate the integration capabilities of focusing on data ingestion, processing integrity, and reporting functionalities to ensure compliance and performance standards are met.", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "integration testing", "data validation", "reporting" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65360N7JPJZ9BP9XYVER | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0001.case.md | 1db2bd01aae3c174a83484efc569a418e7fadc97 | --- FII: TC-0001 groupId: GRP-004 title: Verify Successful Login to the API created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["login"] priority: "High" --- ### Description To verify that a user can successfully log in to the API using valid credentials. ### Pre-Conditions: - The API is up and running. - The user has valid login credentials (username and password). - API authentication endpoint is accessible. ### Test Steps: 1. **Step 1**: Send a POST request to the login API endpoint with valid credentials (username and password). - **Endpoint**: `POST /api/login` - **Request Body**: ```json { "username": "validUser", "password": "validPassword123" } ``` 2. **Step 2**: Verify that the request returns a 200 HTTP status code indicating success. 3. **Step 3**: Verify that the response contains a valid authentication token in the response body. - The token should be a non-empty string. ### Expected Result: - **HTTP Status Code**: 200 OK - **Response Body**: - The response should contain a success message or an authentication token. - The authentication token should be in the correct format (e.g., JWT). - Example response: { "message": "Login successful", "token": "<token>" } | md | 1311 | 2024-12-26 12:09:20 UTC | { "frontMatter": "---\nFII: TC-0001\ngroupId: GRP-004\ntitle: Verify Successful Login to the API\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"login\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nTo verify that a user can successfully log in to the API using valid credentials.\n\n### Pre-Conditions:\n\n- The API is up and running.\n- The user has valid login credentials (username and password).\n- API authentication endpoint is accessible.\n\n### Test Steps:\n\n1. **Step 1**: Send a POST request to the login API endpoint with valid credentials (username and password).\n - **Endpoint**: `POST /api/login`\n - **Request Body**:\n ```json\n {\n \"username\": \"validUser\",\n \"password\": \"validPassword123\"\n }\n ```\n2. **Step 2**: Verify that the request returns a 200 HTTP status code indicating success.\n3. **Step 3**: Verify that the response contains a valid authentication token in the response body.\n - The token should be a non-empty string.\n\n### Expected Result:\n\n- **HTTP Status Code**: 200 OK\n- **Response Body**:\n - The response should contain a success message or an authentication token.\n - The authentication token should be in the correct format (e.g., JWT).\n - Example response:\n {\n \"message\": \"Login successful\",\n \"token\": \"<token>\"\n }\n", "attrs": { "FII": "TC-0001", "groupId": "GRP-004", "title": "Verify Successful Login to the API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } } | { "FII": "TC-0001", "groupId": "GRP-004", "title": "Verify Successful Login to the API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6536CQ906VV929QS8TQY | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0004.run.md | fcc7407fd9c379ebb178610fe89c6f4ca5a3c02a | --- FII: "TR-0004" test_case_fii: "TC-0004" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Failed - Notes: All steps executed successfully. | md | 168 | 2025-01-01 09:47:52 UTC | { "frontMatter": "---\nFII: \"TR-0004\"\ntest_case_fii: \"TC-0004\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "\n### Run Summary\n\n- Status: Failed\n- Notes: All steps executed successfully.\n", "attrs": { "FII": "TR-0004", "test_case_fii": "TC-0004", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0004", "test_case_fii": "TC-0004", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6537V24ME7HCCE9KEFV6 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0004.case.md | f2783fcccaab0afca9809c69284597e92971e28b | --- FII: TC-0004 groupId: GRP-004 title: Verify Empty Payload Block Login to API created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["login"] priority: "High" --- ### Description This test case validates that the API rejects a login attempt with an empty payload. ### Pre-conditions: - The API is running and accessible. - User is not logged in. ### Test Steps 1. **Step 1**: Send a POST request to the API's login endpoint with an empty payload (`{}`). - **Request**: - URL: `https://localhost/api/login` - Method: POST - Payload: `{}` 2. **Step 2**: Verify the status code of the response. 3. **Step 3**: Check the response message for appropriate error handling (e.g., "Invalid input" or "Payload cannot be empty"). ### Expected Result - The response status code should be `400 Bad Request`. - The response body should contain an error message indicating that the payload is empty, such as `"error": "Payload cannot be empty"`. ### Actual Result | md | 1023 | 2024-12-26 12:09:42 UTC | { "frontMatter": "---\nFII: TC-0004\ngroupId: GRP-004\ntitle: Verify Empty Payload Block Login to API\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"login\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case validates that the API rejects a login attempt with an empty payload.\n\n### Pre-conditions:\n\n- The API is running and accessible.\n- User is not logged in.\n\n### Test Steps\n\n1. **Step 1**: Send a POST request to the API's login endpoint with an empty payload (`{}`).\n - **Request**:\n - URL: `https://localhost/api/login`\n - Method: POST\n - Payload: `{}`\n2. **Step 2**: Verify the status code of the response.\n\n3. **Step 3**: Check the response message for appropriate error handling (e.g., \"Invalid input\" or \"Payload cannot be empty\").\n\n### Expected Result\n\n- The response status code should be `400 Bad Request`.\n- The response body should contain an error message indicating that the payload is empty, such as `\"error\": \"Payload cannot be empty\"`.\n\n### Actual Result\n", "attrs": { "FII": "TC-0004", "groupId": "GRP-004", "title": "Verify Empty Payload Block Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } } | { "FII": "TC-0004", "groupId": "GRP-004", "title": "Verify Empty Payload Block Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6537D7KX9YJJM8FCFF4B | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0003.case.md | 932897147239933b47ea2f3bdec27989ccc66995 | --- FII: TC-0003 groupId: GRP-004 title: Verify if Missing "Password" Details Block Login to API created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["login"] priority: "High" --- ### Description This test case verifies that if the "password" detail is missing from the request, the API should block the login attempt. ### Pre-conditions: - The API is up and running. - The API endpoint for login is known and accessible. - Valid user credentials (username) are available. ### Test Steps: 1. **Step 1**: Send a login request to the API with the "username" field populated but the "password" field missing. - **Request**: - Method: POST - Endpoint: `/api/v1/login` - Body: `{ "username": "testuser", "password": "" }` 2. **Step 2**: Check if the login attempt is blocked, and an appropriate error message is returned (e.g., "Password is required"). ### Expected Result: - The API should reject the login attempt with an error response, indicating that the "password" field is required. - **Response**: - HTTP Status Code: `400 Bad Request` - Response Body: `{ "error": "Password is required" }` | md | 1171 | 2024-12-26 12:09:34 UTC | { "frontMatter": "---\nFII: TC-0003\ngroupId: GRP-004\ntitle: Verify if Missing \"Password\" Details Block Login to API\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"login\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case verifies that if the \"password\" detail is missing from the request, the API should block the login attempt.\n\n### Pre-conditions:\n\n- The API is up and running.\n- The API endpoint for login is known and accessible.\n- Valid user credentials (username) are available.\n\n### Test Steps:\n\n1. **Step 1**: Send a login request to the API with the \"username\" field populated but the \"password\" field missing.\n\n - **Request**:\n - Method: POST\n - Endpoint: `/api/v1/login`\n - Body: `{ \"username\": \"testuser\", \"password\": \"\" }`\n\n2. **Step 2**: Check if the login attempt is blocked, and an appropriate error message is returned (e.g., \"Password is required\").\n\n### Expected Result:\n\n- The API should reject the login attempt with an error response, indicating that the \"password\" field is required.\n- **Response**:\n - HTTP Status Code: `400 Bad Request`\n - Response Body: `{ \"error\": \"Password is required\" }`\n", "attrs": { "FII": "TC-0003", "groupId": "GRP-004", "title": "Verify if Missing \"Password\" Details Block Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } } | { "FII": "TC-0003", "groupId": "GRP-004", "title": "Verify if Missing \"Password\" Details Block Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6537Q491PJSEB0TEC675 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0003.run-1.result.json | f0e01728fa020c14c2e8017cbf38866ed5596e26 | { "test_case_fii": "TC-0003", "title": "Verify if Missing Password Details Block Login to API", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a login request to the API with the username field populated but the password field missing.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Check if the login attempt is blocked, and an appropriate error message is returned (e.g., Password is required)", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 881 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6537MSWB6DY0J1A99F72 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0002.case.md | b41dfbb5897d08644a7ceacd96b0358738198e02 | --- FII: TC-0002 groupId: GRP-004 title: Verify Missing "Username and Password" Blocks Login to API created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["login"] priority: "High" --- ### Description This test case verifies that the API does not allow login when "username" and "password" fields are missing in the request payload. ### Pre-Conditions: - The API is accessible. - The testing environment is set up. - The API endpoint for login is known. ### Test Steps: 1. **Step 1**: Send a POST request to the API login endpoint without including the "username" and "password" fields in the request body. - Example Request Body: ```json { "username": "", "password": "" } ``` 2. **Step 2**: Observe the response from the API after submitting the request. ### Expected Result: - The API should respond with a **400 Bad Request** or **401 Unauthorized** error, indicating that both "username" and "password" are required. - The response should contain a meaningful error message, such as: "Error: Missing 'username' and 'password' fields. Please provide valid credentials." | md | 1166 | 2024-12-26 12:09:28 UTC | { "frontMatter": "---\nFII: TC-0002\ngroupId: GRP-004\ntitle: Verify Missing \"Username and Password\" Blocks Login to API\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"login\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case verifies that the API does not allow login when \"username\" and \"password\" fields are missing in the request payload.\n\n### Pre-Conditions:\n\n- The API is accessible.\n- The testing environment is set up.\n- The API endpoint for login is known.\n\n### Test Steps:\n\n1. **Step 1**: Send a POST request to the API login endpoint without including the \"username\" and \"password\" fields in the request body.\n - Example Request Body:\n ```json\n {\n \"username\": \"\",\n \"password\": \"\"\n }\n ```\n2. **Step 2**: Observe the response from the API after submitting the request.\n\n### Expected Result:\n\n- The API should respond with a **400 Bad Request** or **401 Unauthorized** error, indicating that both \"username\" and \"password\" are required.\n- The response should contain a meaningful error message, such as: \n \"Error: Missing 'username' and 'password' fields. Please provide valid credentials.\"\n", "attrs": { "FII": "TC-0002", "groupId": "GRP-004", "title": "Verify Missing \"Username and Password\" Blocks Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } } | { "FII": "TC-0002", "groupId": "GRP-004", "title": "Verify Missing \"Username and Password\" Blocks Login to API", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "login" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65379VNDA30JHSP7WQVH | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0003.run.md | b3d97761dcb8da93c1a1d2eb7fbf61282a1a7e80 | --- FII: "TR-0003" test_case_fii: "TC-0003" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 165 | 2024-12-17 08:47:00 UTC | { "frontMatter": "---\nFII: \"TR-0003\"\ntest_case_fii: \"TC-0003\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0003", "test_case_fii": "TC-0003", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0003", "test_case_fii": "TC-0003", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65387JWSDBBDC5MSZV2D | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0001.run-1.result.json | 85b6cdb2632fdbd099c85d377ca04b157c440e3c | { "test_case_fii": "TC-0001", "title": "Verify Successful Login to the API", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a POST request to the login API endpoint with valid credentials (username and password)", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Verify that the request returns a 200 HTTP status code indicating success.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" }, { "step": 3, "stepname": "Verify that the response contains a valid authentication token in the response body", "status": "passed", "start_time": "2024-12-15T08:45:13.042Z", "end_time": "2024-12-15T08:45:13.045Z" } ] } | json | 1094 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6538YX515APWAA96J9C2 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0002.run-1.result.json | 5c4d39a3c4ee31b7e18f6e2674e92a39238e2bc5 | { "test_case_fii": "TC-0002", "title": "Verify Missing credentials Blocks Login to API", "status": "failed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a POST request to the API login endpoint without including the credentials in fields of the request body.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Observe the response from the API after submitting the request.", "status": "failed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 794 | 2025-01-01 09:46:38 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K653838KBGV74XZ279Y7V | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0002.run.md | a305b966198cd1aa320aa158af4930128aa6aad3 | --- FII: "TR-0002" test_case_fii: "TC-0002" run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: failed - Notes: All steps executed successfully. | md | 168 | 2025-01-01 09:47:18 UTC | { "frontMatter": "---\nFII: \"TR-0002\"\ntest_case_fii: \"TC-0002\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "\n### Run Summary\n\n- Status: failed\n- Notes: All steps executed successfully.\n", "attrs": { "FII": "TR-0002", "test_case_fii": "TC-0002", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0002", "test_case_fii": "TC-0002", "run_date": "2024-12-15", "environment": "Test" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K6538B9DFSKZC57Q39C94 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/login/TC-0004.run-1.result.json | c26064ce814245e270e7dbfdd4c556f70aed706c | { "test_case_fii": "TC-0004", "title": "Verify Empty Payload Block Login to API", "status": "failed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a POST request to the API's login endpoint with an empty payload (`{}`).", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Verify the status code of the response is 400", "status": "failed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" }, { "step": 3, "stepname": "Check the response message for appropriate error handling (e.g., Invalid input or Payload cannot be empty)", "status": "failed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 1020 | 2025-01-01 09:46:28 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K65383CA06Q33YES8D943 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/qf-suite.md | 4f3050914553b5ea050444f49bf73ceb56de2727 | --- id: SUT-003 projectId: PRJ-001 name: "Functional Test Suite" description: "To validate the functionality, reliability, and accuracy of the 10 APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation." created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" tags: ["functional testing"] --- ## Scope of Work The testing will cover the following key activities across 10 APIs: ### Functional Testing - Verify the accuracy of each API endpoint against defined test cases and the provided API documentation. - Validate input and response parameters, including headers and status codes. - Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios. - Confirm the correctness and completeness of the data retrieved by APIs. - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data. | md | 954 | 2024-12-26 12:01:22 UTC | { "frontMatter": "---\nid: SUT-003\nprojectId: PRJ-001\nname: \"Functional Test Suite\"\ndescription: \"To validate the functionality, reliability, and accuracy of the 10 APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntags: [\"functional testing\"]\n---\n", "body": "\n## Scope of Work\n\nThe testing will cover the following key activities across 10 APIs:\n\n### Functional Testing\n\n- Verify the accuracy of each API endpoint against defined test cases and the provided API documentation.\n- Validate input and response parameters, including headers and status codes.\n- Conduct boundary value analysis and test edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios.\n- Confirm the correctness and completeness of the data retrieved by APIs.\n- Ensure APIs effectively handle edge cases like invalid serial numbers or missing data.\n", "attrs": { "id": "SUT-003", "projectId": "PRJ-001", "name": "Functional Test Suite", "description": "To validate the functionality, reliability, and accuracy of the 10 APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "tags": [ "functional testing" ] } } | { "id": "SUT-003", "projectId": "PRJ-001", "name": "Functional Test Suite", "description": "To validate the functionality, reliability, and accuracy of the 10 APIs by executing functional test cases and ensuring alignment with defined requirements and API documentation.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "tags": [ "functional testing" ] } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65384CB2GWS1J1RYP1G4 | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0013.case.md | 1808862e899172433bae31d8161a070f443bdd72 | --- FII: TC-0013 groupId: GRP-005 title: "Ensure that the information retrieved for the search listing." created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Manual" tags: ["wild-cycle"] priority: "High" --- ### Description This test case verifies the accuracy and completeness of the information retrieved from the `/search`. The objective is to ensure that the data returned for the last procedure cycle is consistent, up-to-date, and complete, including all relevant details about the procedures performed, device information, and the status of each procedure. ### Pre-Conditions: - The `/search` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The device has completed the search API procedure, and relevant data is available in the system. ### Test Steps: 1. **Step 1**: Send a GET request to `/search` API endpoint. 2. **Step 2**: Review the JSON response from the server response should include a JSON object with a "resourceType" of "Bundle," containing an array of entries with relevant details about each procedure performed. The procedures should have accurate "performedDateTime," "outcome," "status," and associated references. ### Expected Result: - The response should contain a "Bundle" resource with "Procedure" entries showing the completed procedures, accurate "performedDateTime" and "outcome" data. - No missing or incorrect data for any procedure performed. | md | 1502 | 2025-01-01 09:49:10 UTC | { "frontMatter": "---\nFII: TC-0013\ngroupId: GRP-005\ntitle: \"Ensure that the information retrieved for the search listing.\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Manual\"\ntags: [\"wild-cycle\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nThis test case verifies the accuracy and completeness of the information retrieved from the `/search`. The objective is to ensure that the data returned for the last procedure cycle is consistent, up-to-date, and complete, including all relevant details about the procedures performed, device information, and the status of each procedure.\n\n### Pre-Conditions:\n\n- The `/search` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The device has completed the search API procedure, and relevant data is available in the system.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/search` API endpoint.\n2. **Step 2**: Review the JSON response from the server response should include a JSON object with a \"resourceType\" of \"Bundle,\" containing an array of entries with relevant details about each procedure performed. The procedures should have accurate \"performedDateTime,\" \"outcome,\" \"status,\" and associated references.\n\n### Expected Result:\n\n- The response should contain a \"Bundle\" resource with \"Procedure\" entries showing the completed procedures, accurate \"performedDateTime\" and \"outcome\" data.\n- No missing or incorrect data for any procedure performed.\n", "attrs": { "FII": "TC-0013", "groupId": "GRP-005", "title": "Ensure that the information retrieved for the search listing.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "wild-cycle" ], "priority": "High" } } | { "FII": "TC-0013", "groupId": "GRP-005", "title": "Ensure that the information retrieved for the search listing.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Manual", "tags": [ "wild-cycle" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN | |||||||
| 01JZ7K65388XBAF1QP640E8FJR | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0013.run-1.result.json | b78652a225ff82324bad55a079a68772faca7883 | { "test_case_fii": "TC-0013", "title": "Ensure that the information retrieved for the search listing.", "status": "passed", "start_time": "2024-12-15T08:45:11.753Z", "end_time": "2024-12-15T08:45:13.250Z", "total_duration": "1.50 seconds", "steps": [ { "step": 1, "stepname": "Send a **GET** request to the `/search` endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Review the JSON response from the server response should include a JSON object with a resourceType of Bundle, containing an array of entries with relevant details about each procedure performed. The procedures should have accurate performedDateTime, outcome, status, and associated references.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 1022 | 2024-12-17 08:47:00 UTC | 2025-07-03 07:32:00 | UNKNOWN | |||||||||
| 01JZ7K6539V9XCXMN5KCH2JMSS | 01JZ7K652VKW2F4Q5VYA14Z8FD | 01JZ7K652WTPPJQSKRHZ9E7AF2 | 01JZ7K652XDSD9PVJZK1TMXRMP | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0014.case.md | 926aaa15bf97456732831b69907a8ecec6164664 | --- FII: TC-0014 groupId: GRP-005 title: Ensure that the "Performed Date & Time" of the procedure is present in the response data. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["wild-cycle"] priority: "High" --- ### Description Verify that the API response contains the correct "Performed Date & Time" field when sending a GET request to the `/search` endpoint. ### Pre-Conditions: - The `/search` API endpoint is operational and accessible. - Authentication (if required) is provided, and the request can be successfully executed. - The device has completed the wild cycle procedure, and relevant data is available in the system. ### Test Steps: 1. **Step 1**: Send a GET request to `/search` API endpoint. 2. **Step 2**: Review the JSON response from the server response should include the "PerformedDateTime" field with the correct date and time. ### Expected Result: - The API response should include the "PerformedDateTime" field with the correct date and time in the following format: "PerformedDateTime" : "2015-02-07T13:28:17-05:00" | md | 1103 | 2024-12-26 12:10:26 UTC | { "frontMatter": "---\nFII: TC-0014\ngroupId: GRP-005\ntitle: Ensure that the \"Performed Date & Time\" of the procedure is present in the response data.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"wild-cycle\"]\npriority: \"High\"\n---\n", "body": "\n### Description\n\nVerify that the API response contains the correct \"Performed Date & Time\" field when sending a GET request to the `/search` endpoint.\n\n### Pre-Conditions:\n\n- The `/search` API endpoint is operational and accessible.\n- Authentication (if required) is provided, and the request can be successfully executed.\n- The device has completed the wild cycle procedure, and relevant data is available in the system.\n\n### Test Steps:\n\n1. **Step 1**: Send a GET request to `/search` API endpoint.\n2. **Step 2**: Review the JSON response from the server response should include the \"PerformedDateTime\" field with the correct date and time.\n\n### Expected Result:\n\n- The API response should include the \"PerformedDateTime\" field with the correct date and time in the following format:\n \"PerformedDateTime\" : \"2015-02-07T13:28:17-05:00\"\n", "attrs": { "FII": "TC-0014", "groupId": "GRP-005", "title": "Ensure that the \"Performed Date & Time\" of the procedure is present in the response data.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } } | { "FII": "TC-0014", "groupId": "GRP-005", "title": "Ensure that the \"Performed Date & Time\" of the procedure is present in the response data.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } | 2025-07-03 07:32:00 | UNKNOWN |
Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.
Error in query number 6:
Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:
SELECT 'text' AS component,
(SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
⬆️
'(Page ' || $current_page || ' of ' || $total_pages || ') ' ||
Backtrace
sql parser error: Expected: ), found: $current_page at Line: 42, Column: 35"console/content/table/uniform_resource.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.