uniform_resource (table) Content
- Start Row: 0
- Rows per Page: 50
- Total Rows: 96
- Current Page: 1
- Total Pages: 2
| 01JTT0KWP1ZK8JJNA3Y2Q8HRKQ | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/qf-project.md | f155f37b8f8396e6c4500279f9792b3680b61f2f | --- id: "PRJ-001" name: "Sample Project" description: "The Sample Project API enables efficient management by providing real-time data tracking, status updates, and maintenance logs. It supports secure integration with external systems using RESTful endpoints and JSON data formats." created_by: "admin@opsfolio.com" created_at: "2024-11-01" last_updated_at: "2024-11-18" status: "Active" tags: ["integration testing", "system validation", "performance testing"] --- ### Project Overview This defines the framework for testing sample project APIs. It specifies the testing scope, required resources, timelines, roles, and associated risks. It ensures the APIs deliver accurate operational and maintenance data. ### Scope The testing effort will encompass the following key activities in 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 for edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios. - Confirm the correctness and completeness of the data retrieved by the APIs. - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data. • Integration Testing - Validate seamless integration of the APIs with the system and the API tracking system. - Confirm proper functionality of database connectivity and API tracking mechanisms, particularly for authentication retrievals. - Security Testing - Verify token-based authentication and user roles, including checks for unauthorized access attempts. - Test for vulnerabilities such as SQL injection and Cross-Site Scripting (XSS) through input validation. - Ensure secure data transmission via HTTPS and encryption for sensitive information. - Validate API usage limits (rate limiting) and confirm that abusive patterns are effectively restricted. - Regression Testing - Ensure that bug fixes do not impact the functionality or responses of existing API endpoints by re-executing test cases after fixes are applied. - Analyze related components and workflows connected to updated APIs to confirm stability and compatibility post-execution. - Compatibility Testing - Focus on widely used browsers (e.g., Chromium, Safari, Firefox) and OS platforms (Windows, macOS, Linux). - Usability Testing - Rationale: API simplicity justifies the exclusion of usability testing. - Compensatory Measure: Developer documentation will be reviewed for clarity, completeness, and accuracy as part of the deliverables. - Performance, Load, and Scalability Testing - Exclusion Justification: Single-user interactions are anticipated per device. - Recommendation: Include performance benchmarks (e.g., response time, throughput, error rate, endurance testing, and resource utilization). - Compliance Testing - Ensure the provided tracking APIs comply with ISO 14971 for secure communication (SSL/TLS), authentication, and data integrity. Testing for adherence to FHIR standards. | md | 3165 | 2024-12-20 09:14:54 UTC | { "frontMatter": "---\nid: \"PRJ-001\"\nname: \"Sample Project\"\ndescription: \"The Sample Project API enables efficient management by providing real-time data tracking, status updates, and maintenance logs. It supports secure integration with external systems using RESTful endpoints and JSON data formats.\"\ncreated_by: \"admin@opsfolio.com\"\ncreated_at: \"2024-11-01\"\nlast_updated_at: \"2024-11-18\"\nstatus: \"Active\"\ntags: [\"integration testing\", \"system validation\", \"performance testing\"]\n---\n", "body": "\n### Project Overview\nThis defines the framework for testing sample project APIs. It specifies the testing scope, required resources, timelines, roles, and associated risks. It ensures the APIs deliver accurate operational and maintenance data.\n\n### Scope\nThe testing effort will encompass the following key activities in 10 APIs:\n\n - Functional Testing\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 for edge cases, such as handling empty requests, invalid inputs, and other unexpected scenarios.\n - Confirm the correctness and completeness of the data retrieved by the APIs.\n - Ensure APIs effectively handle edge cases like invalid serial numbers or missing data.\n•\tIntegration Testing\n - Validate seamless integration of the APIs with the system and the API tracking system.\n - Confirm proper functionality of database connectivity and API tracking mechanisms, particularly for authentication retrievals.\n - Security Testing\n - Verify token-based authentication and user roles, including checks for unauthorized access attempts.\n - Test for vulnerabilities such as SQL injection and Cross-Site Scripting (XSS) through input validation.\n - Ensure secure data transmission via HTTPS and encryption for sensitive information.\n - Validate API usage limits (rate limiting) and confirm that abusive patterns are effectively restricted.\n - Regression Testing\n - Ensure that bug fixes do not impact the functionality or responses of existing API endpoints by re-executing test cases after fixes are applied.\n - Analyze related components and workflows connected to updated APIs to confirm stability and compatibility post-execution.\n - Compatibility Testing\n - Focus on widely used browsers (e.g., Chromium, Safari, Firefox) and OS platforms (Windows, macOS, Linux).\n - Usability Testing\n - Rationale: API simplicity justifies the exclusion of usability testing.\n - Compensatory Measure: Developer documentation will be reviewed for clarity, completeness, and accuracy as part of the deliverables.\n - Performance, Load, and Scalability Testing\n - Exclusion Justification: Single-user interactions are anticipated per device.\n - Recommendation: Include performance benchmarks (e.g., response time, throughput, error rate, endurance testing, and resource utilization).\n - Compliance Testing\n - Ensure the provided tracking APIs comply with ISO 14971 for secure communication (SSL/TLS), authentication, and data integrity. Testing for adherence to FHIR standards.", "attrs": { "id": "PRJ-001", "name": "Sample Project", "description": "The Sample Project API enables efficient management by providing real-time data tracking, status updates, and maintenance logs. It supports secure integration with external systems using RESTful endpoints and JSON data formats.", "created_by": "admin@opsfolio.com", "created_at": "2024-11-01", "last_updated_at": "2024-11-18", "status": "Active", "tags": [ "integration testing", "system validation", "performance testing" ] } } | { "id": "PRJ-001", "name": "Sample Project", "description": "The Sample Project API enables efficient management by providing real-time data tracking, status updates, and maintenance logs. It supports secure integration with external systems using RESTful endpoints and JSON data formats.", "created_by": "admin@opsfolio.com", "created_at": "2024-11-01", "last_updated_at": "2024-11-18", "status": "Active", "tags": [ "integration testing", "system validation", "performance testing" ] } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP2KEGZ6HTXRS2MQRH8 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/qf-suite.md | 400970aa7c748a5eeea6f845c90a14a06f24e85b | --- id: SUT-002 projectId: PRJ-001 name: "Compliance Test Suite" description: "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG)." created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["compliance testing"] --- ## Test Execution Steps ### Analyze FHIR Implementation Guide (IG) Requirements - Review the IG to identify key compliance requirements, including resource profiles, extensions, and terminology bindings. ### Validate FHIR Resource Profiles - Verify that all FHIR resources conform to the structure and constraints specified in the IG. - Test for compliance with required, must-support, and optional elements. ### Verify Extensions and Modifications - Validate custom extensions and modifications to ensure they are defined and implemented according to the IG. ### Terminology Binding Validation - Confirm that codable concepts and value sets adhere to the terminology bindings specified in the IG. ### Check Conformance Statements - Validate system compliance with declared FHIR capabilities (e.g., search parameters, read, write, or operation support). ### Validate Interactions and APIs - Test API interactions (read, create, update, delete) to ensure they align with IG requirements. ### Test for Cardinality Rules - Verify adherence to cardinality rules (minimum and maximum occurrence constraints) specified in the IG. ### HTTP Status Code Validation - Validate API responses to ensure appropriate HTTP status codes are returned based on FHIR operations. ### Data Validation Against IG Examples - Compare FHIR resource instances against examples provided in the IG for accuracy and adherence. ## Decision Point - **If validation fails**: Proceed to "Defect Logging." - **If validation passes**: Proceed to "Documentation of Compliance." ## Defect Log in Jira & Xray - Log identified defects in Jira and link them to corresponding Xray test cases for traceability. ## Issue Fixes - Address non-compliance issues to ensure the API meets FHIR IG standards. ## Retesting & Regression Testing - Retest resolved issues to confirm compliance. - Conduct regression testing to verify no new issues were introduced. ## Test Report Generation - Generate a consolidated test report summarizing validation outcomes, including test success rates, defects, logs, and screenshots. ## Deliverables 1. **Test Report**: Summary of test execution, success rates, defects, and screenshots. 2. **Defect Management Records**: Complete traceability of logged defects from identification to resolution. | md | 2673 | 2024-12-30 15:35:08 UTC | { "frontMatter": "---\nid: SUT-002\nprojectId: PRJ-001\nname: \"Compliance Test Suite\"\ndescription: \"To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).\"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"compliance testing\"]\n---\n", "body": "\n## Test Execution Steps\n\n### Analyze FHIR Implementation Guide (IG) Requirements\n\n- Review the IG to identify key compliance requirements, including resource profiles, extensions, and terminology bindings.\n\n### Validate FHIR Resource Profiles\n\n- Verify that all FHIR resources conform to the structure and constraints specified in the IG.\n- Test for compliance with required, must-support, and optional elements.\n\n### Verify Extensions and Modifications\n\n- Validate custom extensions and modifications to ensure they are defined and implemented according to the IG.\n\n### Terminology Binding Validation\n\n- Confirm that codable concepts and value sets adhere to the terminology bindings specified in the IG.\n\n### Check Conformance Statements\n\n- Validate system compliance with declared FHIR capabilities (e.g., search parameters, read, write, or operation support).\n\n### Validate Interactions and APIs\n\n- Test API interactions (read, create, update, delete) to ensure they align with IG requirements.\n\n### Test for Cardinality Rules\n\n- Verify adherence to cardinality rules (minimum and maximum occurrence constraints) specified in the IG.\n\n### HTTP Status Code Validation\n\n- Validate API responses to ensure appropriate HTTP status codes are returned based on FHIR operations.\n\n### Data Validation Against IG Examples\n\n- Compare FHIR resource instances against examples provided in the IG for accuracy and adherence.\n\n## Decision Point\n\n- **If validation fails**: Proceed to \"Defect Logging.\"\n- **If validation passes**: Proceed to \"Documentation of Compliance.\"\n\n## Defect Log in Jira & Xray\n\n- Log identified defects in Jira and link them to corresponding Xray test cases for traceability.\n\n## Issue Fixes\n\n- Address non-compliance issues to ensure the API meets FHIR IG standards.\n\n## Retesting & Regression Testing\n\n- Retest resolved issues to confirm compliance.\n- Conduct regression testing to verify no new issues were introduced.\n\n## Test Report Generation\n\n- Generate a consolidated test report summarizing validation outcomes, including test success rates, defects, logs, and screenshots.\n\n## Deliverables\n\n1. **Test Report**: Summary of test execution, success rates, defects, and screenshots.\n2. **Defect Management Records**: Complete traceability of logged defects from identification to resolution.\n", "attrs": { "id": "SUT-002", "projectId": "PRJ-001", "name": "Compliance Test Suite", "description": "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ] } } | { "id": "SUT-002", "projectId": "PRJ-001", "name": "Compliance Test Suite", "description": "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ] } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP216K9M9T7NZ9SAFKF | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/test-plan/qf-plan.md | 4586f5cfa0fc76ac0681e36cd41097c6fde16acc | --- id: PLN-002 name: "compliance Test Plan" description: "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG)." created_by: "qa-lead@example.com" created_at: "2024-11-01" tags: ["compliance testing"] related_requirements: ["REQ-101", "REQ-102"] --- Ensure that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG). ## Test Execution Steps ### Analyze FHIR Implementation Guide (IG) Requirements - Review the IG to identify key compliance requirements, including resource profiles, extensions, and terminology bindings. ### Validate FHIR Resource Profiles - Verify that all FHIR resources conform to the structure and constraints specified in the IG. - Test for compliance with required, must-support, and optional elements. ### Verify Extensions and Modifications - Validate custom extensions and modifications to ensure they are defined and implemented according to the IG. ### Terminology Binding Validation - Confirm that codable concepts and value sets adhere to the terminology bindings specified in the IG. ### Check Conformance Statements - Validate system compliance with declared FHIR capabilities (e.g., search parameters, read, write, or operation support). ### Validate Interactions and APIs - Test API interactions (read, create, update, delete) to ensure they align with IG requirements. ### Test for Cardinality Rules - Verify adherence to cardinality rules (minimum and maximum occurrence constraints) specified in the IG. ### HTTP Status Code Validation - Validate API responses to ensure appropriate HTTP status codes are returned based on FHIR operations. ### Data Validation Against IG Examples - Compare FHIR resource instances against examples provided in the IG for accuracy and adherence. ## Decision Point - **If validation fails**: Proceed to "Defect Logging." - **If validation passes**: Proceed to "Documentation of Compliance." ## Defect Log in Jira & Xray - Log identified defects in Jira and link them to corresponding Xray test cases for traceability. ## Issue Fixes - Address non-compliance issues to ensure the API meets FHIR IG standards. ## Retesting & Regression Testing - Retest resolved issues to confirm compliance. - Conduct regression testing to verify no new issues were introduced. ## Test Report Generation - Generate a consolidated test report summarizing validation outcomes, including test success rates, defects, logs, and screenshots. ## Deliverables 1. **Test Report**: Summary of test execution, success rates, defects, and screenshots. 2. **Defect Management Records**: Complete traceability of logged defects from identification to resolution. | md | 2881 | 2024-12-30 15:39:08 UTC | { "frontMatter": "---\nid: PLN-002\nname: \"compliance Test Plan\"\ndescription: \"To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).\"\ncreated_by: \"qa-lead@example.com\"\ncreated_at: \"2024-11-01\"\ntags: [\"compliance testing\"]\nrelated_requirements: [\"REQ-101\", \"REQ-102\"]\n---\n", "body": "\nEnsure that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).\n\n## Test Execution Steps\n\n### Analyze FHIR Implementation Guide (IG) Requirements\n\n- Review the IG to identify key compliance requirements, including resource profiles, extensions, and terminology bindings.\n\n### Validate FHIR Resource Profiles\n\n- Verify that all FHIR resources conform to the structure and constraints specified in the IG.\n- Test for compliance with required, must-support, and optional elements.\n\n### Verify Extensions and Modifications\n\n- Validate custom extensions and modifications to ensure they are defined and implemented according to the IG.\n\n### Terminology Binding Validation\n\n- Confirm that codable concepts and value sets adhere to the terminology bindings specified in the IG.\n\n### Check Conformance Statements\n\n- Validate system compliance with declared FHIR capabilities (e.g., search parameters, read, write, or operation support).\n\n### Validate Interactions and APIs\n\n- Test API interactions (read, create, update, delete) to ensure they align with IG requirements.\n\n### Test for Cardinality Rules\n\n- Verify adherence to cardinality rules (minimum and maximum occurrence constraints) specified in the IG.\n\n### HTTP Status Code Validation\n\n- Validate API responses to ensure appropriate HTTP status codes are returned based on FHIR operations.\n\n### Data Validation Against IG Examples\n\n- Compare FHIR resource instances against examples provided in the IG for accuracy and adherence.\n\n## Decision Point\n\n- **If validation fails**: Proceed to \"Defect Logging.\"\n- **If validation passes**: Proceed to \"Documentation of Compliance.\"\n\n## Defect Log in Jira & Xray\n\n- Log identified defects in Jira and link them to corresponding Xray test cases for traceability.\n\n## Issue Fixes\n\n- Address non-compliance issues to ensure the API meets FHIR IG standards.\n\n## Retesting & Regression Testing\n\n- Retest resolved issues to confirm compliance.\n- Conduct regression testing to verify no new issues were introduced.\n\n## Test Report Generation\n\n- Generate a consolidated test report summarizing validation outcomes, including test success rates, defects, logs, and screenshots.\n\n## Deliverables\n\n1. **Test Report**: Summary of test execution, success rates, defects, and screenshots.\n2. **Defect Management Records**: Complete traceability of logged defects from identification to resolution.\n", "attrs": { "id": "PLN-002", "name": "compliance Test Plan", "description": "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } } | { "id": "PLN-002", "name": "compliance Test Plan", "description": "To validate that the system complies with the FHIR standards by testing its API endpoints and data exchange processes against the specifications defined in the Implementation Guide (IG).", "created_by": "qa-lead@example.com", "created_at": "2024-11-01", "tags": [ "compliance testing" ], "related_requirements": [ "REQ-101", "REQ-102" ] } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP2W4QS9WR4WG0GW7AF | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/compliance-testcase/qf-case-group.md | e1324f2216c16e9b3e82825e4c0235a3826b7912 | --- id: GRP-002 SuiteId: SUT-002 planId: ["PLN-002"] name: "Compliance Test Cases" description: "Comprehensive FHIR Conformance Validation and Testing" created_by: "arun-ramanan@netspective.in" created_at: "2024-11-01" tags: ["Compatability testing"] --- ## Description To ensure adherence to FHIR (Fast Healthcare Interoperability Resources) standards based on the Implementation Guide (IG). The test aims to validate conformance to FHIR profiles, security standards, and operational best practices across all relevant endpoints and resources. ## Test Cases to Execute ### 1. Resource-Level Validation - Verify adherence to mandatory and optional FHIR elements for specific resources. - Ensure support for required extensions and custom profiles per the IG. - Validate use of terminology bindings to specified Value Sets. ### 2. Capability Statement Validation - Verify the API's Capability Statement includes all mandatory elements defined in the IG. - Confirm supported operations, interactions, and resource types. ### 4. Terminology Services Testing - Verify the use of correct Value Sets, Code Systems, and terminology bindings. - Test `$validate-code` and `$expand` operations for terminology validation. ### 10. Audit Logging - Validate that all operations are logged as per FHIR security standards. - Confirm compliance with audit event structures defined in FHIR. ## Environment - **Test Environment:** Test server with FHIR-compliant configuration. - **FHIR Version:** As specified in the IG (e.g., R4, R5). - **Scope Host URL/IP:** Defined API endpoint or test instance. ## Tools Utilized - **FHIR Validator:** Validate resource conformance to FHIR profiles. ## Objectives - Validate compliance with FHIR Implementation Guide requirements. - Identify deviations from FHIR standards and IG conformance. ## Execution Strategy ### Pre-Test Preparation: - Review the FHIR IG and confirm test prerequisites. - Load test data based on IG-compliant resource examples. ### Test Execution: - Run automated tests for conformance using the FHIR Validator. ### Post-Test Reporting: - Document test results and any deviations from expected behavior. - Provide actionable recommendations for resolving identified issues. | md | 2243 | 2024-12-26 11:56:54 UTC | { "frontMatter": "---\nid: GRP-002\nSuiteId: SUT-002\nplanId: [\"PLN-002\"]\nname: \"Compliance Test Cases\"\ndescription: \"Comprehensive FHIR Conformance Validation and Testing\"\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-11-01\"\ntags: [\"Compatability testing\"]\n---\n", "body": "\n## Description\n\nTo ensure adherence to FHIR (Fast Healthcare Interoperability Resources) standards based on the Implementation Guide (IG). The test aims to validate conformance to FHIR profiles, security standards, and operational best practices across all relevant endpoints and resources.\n\n## Test Cases to Execute\n\n### 1. Resource-Level Validation\n\n- Verify adherence to mandatory and optional FHIR elements for specific resources.\n- Ensure support for required extensions and custom profiles per the IG.\n- Validate use of terminology bindings to specified Value Sets.\n\n### 2. Capability Statement Validation\n\n- Verify the API's Capability Statement includes all mandatory elements defined in the IG.\n- Confirm supported operations, interactions, and resource types.\n\n### 4. Terminology Services Testing\n\n- Verify the use of correct Value Sets, Code Systems, and terminology bindings.\n- Test `$validate-code` and `$expand` operations for terminology validation.\n\n### 10. Audit Logging\n\n- Validate that all operations are logged as per FHIR security standards.\n- Confirm compliance with audit event structures defined in FHIR.\n\n## Environment\n\n- **Test Environment:** Test server with FHIR-compliant configuration.\n- **FHIR Version:** As specified in the IG (e.g., R4, R5).\n- **Scope Host URL/IP:** Defined API endpoint or test instance.\n\n## Tools Utilized\n\n- **FHIR Validator:** Validate resource conformance to FHIR profiles.\n\n## Objectives\n\n- Validate compliance with FHIR Implementation Guide requirements.\n- Identify deviations from FHIR standards and IG conformance.\n\n## Execution Strategy\n\n### Pre-Test Preparation:\n\n- Review the FHIR IG and confirm test prerequisites.\n- Load test data based on IG-compliant resource examples.\n\n### Test Execution:\n\n- Run automated tests for conformance using the FHIR Validator.\n\n### Post-Test Reporting:\n\n- Document test results and any deviations from expected behavior.\n- Provide actionable recommendations for resolving identified issues.\n", "attrs": { "id": "GRP-002", "SuiteId": "SUT-002", "planId": [ "PLN-002" ], "name": "Compliance Test Cases", "description": "Comprehensive FHIR Conformance Validation and Testing", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "Compatability testing" ] } } | { "id": "GRP-002", "SuiteId": "SUT-002", "planId": [ "PLN-002" ], "name": "Compliance Test Cases", "description": "Comprehensive FHIR Conformance Validation and Testing", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-11-01", "tags": [ "Compatability testing" ] } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP2GNK3A1F35M5QEME1 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/compliance-testcase/TC-0023.run-1.result.json | f2503ac359e04171a0c1c7e0b9f6791838718ec5 | { "test_case_fii": "TC-0023", "title": "Ensure that the response body adheres to the schema defined in the Implementation Guide (IG) for the API 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 request (GET/POST/PUT depending on the API) to the target endpoint.", "status": "passed", "start_time": "2024-12-15T08:45:11.762Z", "end_time": "2024-12-15T08:45:13.003Z" }, { "step": 2, "stepname": "Capture the JSON response from the API.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" }, { "step": 3, "stepname": "Compare the response body against the schema defined in the IG using a schema validation tool.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" }, { "step": 4, "stepname": "Verify that all required fields are present and adhere to the expected data types and formats.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 1418 | 2024-12-17 08:47:00 UTC | 2025-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP336HDX5S8J7T468XX | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/compliance-testcase/TC-0023.case.md | 0521888e2e21e9da9c82e4c1b83501d7f58b7841 | --- FII: TC-0023 groupId: GRP-002 projectId: PRJ-001 test_execution: EXE-002 planId: PLN-002 title: Ensure that the response body adheres to the schema defined in the Implementation Guide (IG) for the API endpoint. created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["compliance testing"] priority: "High" --- ### Description This test verifies that the JSON response from the API matches the schema requirements outlined in the IG. Any deviations from the schema should be identified and flagged as errors. ### Pre-Conditions: - API endpoint is accessible and operational. - The expected response schema is defined in the IG. - A tool or script for schema validation (e.g., Postman, JSON Schema Validator) is available. ### Test Steps: 1. **Step 1**: Send a request (GET/POST/PUT depending on the API) to the target endpoint. 2. **Step 2**: Capture the JSON response from the API. 3. **Step 3**: Compare the response body against the schema defined in the IG using a schema validation tool. 4. **Step 4**: Verify that all required fields are present and adhere to the expected data types and formats. ### Expected Result: - The response body conforms to the schema specified in the IG, including: - Required fields are present. - Data types and formats match schema definitions. - No additional or unexpected fields are included unless allowed by the schema. | md | 1422 | 2024-12-19 16:50:28 UTC | { "frontMatter": "---\nFII: TC-0023\ngroupId: GRP-002\nprojectId: PRJ-001\ntest_execution: EXE-002\nplanId: PLN-002\ntitle: Ensure that the response body adheres to the schema defined in the Implementation Guide (IG) for the API endpoint.\ncreated_by: \"arun-ramanan@netspective.in\"\ncreated_at: \"2024-12-15\"\ntest_type: \"Automation\"\ntags: [\"compliance testing\"]\npriority: \"High\"\n---\n", "body": "\n### Description\nThis test verifies that the JSON response from the API matches the schema requirements outlined in the IG. Any deviations from the schema should be identified and flagged as errors.\n\n### Pre-Conditions:\n- API endpoint is accessible and operational.\n- The expected response schema is defined in the IG.\n- A tool or script for schema validation (e.g., Postman, JSON Schema Validator) is available.\n\n### Test Steps:\n\n1. **Step 1**: Send a request (GET/POST/PUT depending on the API) to the target endpoint. \n2. **Step 2**: Capture the JSON response from the API. \n3. **Step 3**: Compare the response body against the schema defined in the IG using a schema validation tool. \n4. **Step 4**: Verify that all required fields are present and adhere to the expected data types and formats.\n\n### Expected Result:\n- The response body conforms to the schema specified in the IG, including:\n - Required fields are present.\n - Data types and formats match schema definitions.\n - No additional or unexpected fields are included unless allowed by the schema.", "attrs": { "FII": "TC-0023", "groupId": "GRP-002", "projectId": "PRJ-001", "test_execution": "EXE-002", "planId": "PLN-002", "title": "Ensure that the response body adheres to the schema defined in the Implementation Guide (IG) for the API endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "compliance testing" ], "priority": "High" } } | { "FII": "TC-0023", "groupId": "GRP-002", "projectId": "PRJ-001", "test_execution": "EXE-002", "planId": "PLN-002", "title": "Ensure that the response body adheres to the schema defined in the Implementation Guide (IG) for the API endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "compliance testing" ], "priority": "High" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP3V1HTPM9EX9JN5D7G | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-compliance-testing/compliance-testcase/TC-0023.run.md | 03bcb637cfe78689717c2f4c46ff4d8f463f1c3c | --- FII: "TR-0023" test_case_fii: "TC-0023" projectId: PRJ-001 test_execution: EXE-002 planId: PLN-002 run_date: "2024-12-15" environment: "Test" --- ### Run Summary - Status: Passed - Notes: All steps executed successfully. | md | 224 | 2024-12-19 16:49:06 UTC | { "frontMatter": "---\nFII: \"TR-0023\"\ntest_case_fii: \"TC-0023\"\nprojectId: PRJ-001\ntest_execution: EXE-002\nplanId: PLN-002\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0023", "test_case_fii": "TC-0023", "projectId": "PRJ-001", "test_execution": "EXE-002", "planId": "PLN-002", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0023", "test_case_fii": "TC-0023", "projectId": "PRJ-001", "test_execution": "EXE-002", "planId": "PLN-002", "run_date": "2024-12-15", "environment": "Test" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP3WS2N583E7VW7X7AF | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP3V4TJS1BP2G127ED2 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0016.case.md | 8ce6ba624c2c3ef8d2df35c286603fb8714c68ea | --- FII: TC-0016 groupId: GRP-005 title: "Ensure that the 'Result' field exists within the response data when a GET request is sent to the `/search` endpoint." created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["wild-cycle"] priority: "High" --- ### Description This test verifies that the 'Result' is included in the response data returned by the `/search` endpoint. The test ensures the correct structure and expected values are returned, demonstrating successful execution and compliance with the API requirements. ### 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 data contains the 'Result' field exists within the response data. ### Expected Result: - The response data includes the proper structure. | md | 1122 | 2024-12-26 12:10:38 UTC | { "frontMatter": "---\nFII: TC-0016\ngroupId: GRP-005\ntitle: \"Ensure that the 'Result' field exists within the response data when a GET request is sent to the `/search` endpoint.\"\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\nThis test verifies that the 'Result' is included in the response data returned by the `/search` endpoint. The test ensures the correct structure and expected values are returned, demonstrating successful execution and compliance with the API requirements.\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 data contains the 'Result' field exists within the response data.\n\n### Expected Result:\n\n- The response data includes the proper structure.\n", "attrs": { "FII": "TC-0016", "groupId": "GRP-005", "title": "Ensure that the 'Result' field exists within the response data when a GET request is sent to the `/search` endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } } | { "FII": "TC-0016", "groupId": "GRP-005", "title": "Ensure that the 'Result' field exists within the response data when a GET request is sent to the `/search` endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP4FZRFFKJ49TZ1NYBA | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/qf-case-group.md | 65c0142c440f61917c69a0fda1392e6cb53ef096 | --- id: GRP-005 SuiteId: SUT-003 planId: ["PLN-008"] name: "Search API Test Cases" description: "Group of test cases designed to validate the integration capabilities of Search API, 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 Search API by validating key integration points and performance metrics: - **Data Ingestion**: Verifying Search 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 | 1275 | 2024-12-26 17:34:48 UTC | { "frontMatter": "---\nid: GRP-005\nSuiteId: SUT-003\nplanId: [\"PLN-008\"]\nname: \"Search API Test Cases\"\ndescription: \"Group of test cases designed to validate the integration capabilities of Search API, 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 Search API by validating key integration points and performance metrics:\n\n- **Data Ingestion**: Verifying Search 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-005", "SuiteId": "SUT-003", "planId": [ "PLN-008" ], "name": "Search API Test Cases", "description": "Group of test cases designed to validate the integration capabilities of Search API, 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-005", "SuiteId": "SUT-003", "planId": [ "PLN-008" ], "name": "Search API Test Cases", "description": "Group of test cases designed to validate the integration capabilities of Search API, 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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP4FKBVW8HKFXKGY8Z8 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0014.run.md | 5796f1228ec7ed6c34799f2ddcc57ae9f82692c4 | --- FII: "TR-0014" test_case_fii: "TC-0014" 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-0014\"\ntest_case_fii: \"TC-0014\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0014", "test_case_fii": "TC-0014", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0014", "test_case_fii": "TC-0014", "run_date": "2024-12-15", "environment": "Test" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP4YAPMK6JRJQS8AKVY | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0015.run-1.result.json | 901a010a11f006ca8d9af8841e9f0f4892aa855e | { "test_case_fii": "TC-0015", "title": "Ensure that the `MRC result` field exists within the response data when a GET request is sent to the `/search` 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 `/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 data contains the `MRC result` object with the expected attributes.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 905 | 2024-12-17 08:47:00 UTC | 2025-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP40XV2STB2K6W3EFT8 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0016.run.md | 36ed98fce8233f83d2ed079c0af8d944f46815b0 | --- FII: "TR-0016" test_case_fii: "TC-0016" 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-0016\"\ntest_case_fii: \"TC-0016\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0016", "test_case_fii": "TC-0016", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0016", "test_case_fii": "TC-0016", "run_date": "2024-12-15", "environment": "Test" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP4JN0JZKVG5KFF26ED | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP5RXVBAXS61RK3RXH3 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0014.run-1.result.json | 118fb1646e71c2ea50aa7ddc85ffccbdf570b239 | { "test_case_fii": "TC-0014", "title": "Ensure that the `Performed Date & Time` of the procedure is present in 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 `/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 the `PerformedDateTime` field with the correct date and time.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 883 | 2024-12-17 08:47:00 UTC | 2025-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP5DC5E62Y5Q920CGR8 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0013.run.md | 9fb0d905fc34e2a3ec91533ea311dfc44c44782e | --- FII: "TR-0013" test_case_fii: "TC-0013" 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-0013\"\ntest_case_fii: \"TC-0013\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0013", "test_case_fii": "TC-0013", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0013", "test_case_fii": "TC-0013", "run_date": "2024-12-15", "environment": "Test" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP5SBVNQ19MX1Y8PW49 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP5M6QFCXZY54400W1A | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP5MD0R04B4CG4N1GT7 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0016.run-1.result.json | bdc7c83b7e720c1f427836809fc433f19d54a302 | { "test_case_fii": "TC-0016", "title": "Ensure that the `Result` field exists within the response data when a GET request is sent to the `/search` 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 `/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 data contains the 'Result'field exists within the response data.", "status": "passed", "start_time": "2024-12-15T08:45:13.014Z", "end_time": "2024-12-15T08:45:13.041Z" } ] } | json | 898 | 2024-12-17 08:47:00 UTC | 2025-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP56YWX81HYRS943468 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0015.run.md | f5f5f61582bbd9f695dce91a7e28e405f8d6dffc | --- FII: "TR-0015" test_case_fii: "TC-0015" 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-0015\"\ntest_case_fii: \"TC-0015\"\nrun_date: \"2024-12-15\"\nenvironment: \"Test\"\n---\n", "body": "### Run Summary\n- Status: Passed\n- Notes: All steps executed successfully.", "attrs": { "FII": "TR-0015", "test_case_fii": "TC-0015", "run_date": "2024-12-15", "environment": "Test" } } | { "FII": "TR-0015", "test_case_fii": "TC-0015", "run_date": "2024-12-15", "environment": "Test" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP6V5MJCPN1GZKYMJ6F | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /app/www.surveilr.com/lib/service/qualityfolio/rssd/synthetic-asset-tracking/api-functional-testing/search/TC-0015.case.md | d98eb787cd256f14da27b859b78f00b43cef713c | --- FII: TC-0015 groupId: GRP-005 title: "Ensure that the `MRC result` field exists within the response data when a GET request is sent to the `/search` endpoint." created_by: "arun-ramanan@netspective.in" created_at: "2024-12-15" test_type: "Automation" tags: ["wild-cycle"] priority: "High" --- ### Description This test verifies that the `MRC result` is included in the response data returned by the `/search` endpoint. The test ensures the correct structure and expected values are returned, demonstrating successful execution and compliance with the API requirements. ### 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 data contains the `MRC result` object with the expected attributes. ### Expected Result: - The response data includes the proper structure. | md | 1132 | 2024-12-26 12:10:34 UTC | { "frontMatter": "---\nFII: TC-0015\ngroupId: GRP-005\ntitle: \"Ensure that the `MRC result` field exists within the response data when a GET request is sent to the `/search` endpoint.\"\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\nThis test verifies that the `MRC result` is included in the response data returned by the `/search` endpoint. The test ensures the correct structure and expected values are returned, demonstrating successful execution and compliance with the API requirements.\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 data contains the `MRC result` object with the expected attributes.\n\n### Expected Result:\n\n- The response data includes the proper structure.\n", "attrs": { "FII": "TC-0015", "groupId": "GRP-005", "title": "Ensure that the `MRC result` field exists within the response data when a GET request is sent to the `/search` endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } } | { "FII": "TC-0015", "groupId": "GRP-005", "title": "Ensure that the `MRC result` field exists within the response data when a GET request is sent to the `/search` endpoint.", "created_by": "arun-ramanan@netspective.in", "created_at": "2024-12-15", "test_type": "Automation", "tags": [ "wild-cycle" ], "priority": "High" } | 2025-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP6JYM60X21D3BAZHDE | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP67S5N0F06HZ81PSJB | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP6BXCY1YGRZBTECX70 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP6FHQMCF2RBE0KZ40A | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP7HXQB7B2MH4N23J6S | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP7SP04DMSFWV515Q53 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP7AW60WEK1R0A23E6V | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP7GXRJNK15VNF9Q32E | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP747801PAXX22G36G1 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP8XZ2GSDAZ8CGZEF8Y | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP82GMB8SXXXJSBKMAN | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP822H93HX5Z3R3F5VT | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP85RBYKCGNKK3BSFR9 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP8FGCGAM89YW0KQNXK | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP8GWHWA7FRT8J77D97 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP81VGCG0EJB9MAVX13 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP8PZ0CGA91XVFXDZGT | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||||
| 01JTT0KWP96DKJEVKX01MHK3VD | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP90MW06JCS1B51DKFX | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP99M62B5NAJKERK047 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWP946RE122M5WQRW414 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPA0W23NMFJFNQRNGJ5 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPAVYCCCA7XS7WQ5GPH | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPAQ3YK5AMRKTE468XB | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPA2CQAQAS00CJXMR4G | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPB0FQKAJT2ZVDT51XB | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPB4XJYXXJEAFDH6QKR | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPBMWBWR491VD554FMG | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN | |||||||
| 01JTT0KWPBZDPJAN00BW326T59 | 01JTT0KWNXQEEMM59Z0EPSCSKX | 01JTT0KWNYFYKN55TY3EPQ066G | 01JTT0KWNZB8TQA4JMWF9Q8M6F | /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-05-09 07:54:33 | UNKNOWN |
(Page 1 of 2) Next