Divya Ramamurthy

Test Case - Connector Integration Testing.xlsx NO TEST SCENARIO 1 Authentication NEW Connector Scenarios TEST DATA TEST CASES DESCRIPTION Authentication types and their test Try connecting with VALID values connection parameters as per requirements Data Load Verify that the connector can successfully authenticate with the Source system using valid credentials. From Connector, trigger a connection request to the Source System Connector should Fail when incorrect credentials are provided. Ensure Connector is active and data load is functioning Verify that the connector is performing operation as fetching data from the Source system. Ensure Connector is active and data load is functioning Verify error handling is functioning and ensure that appropriate error messages are returned. Authentication is successful and Sample test Try loading data with VALID values data is available in Source system Try loading data with INVALID values Ensure data load is successful and transformation workflow is triggered Confirm that the workflow executes successfully when all necessary parameters are provided and the required conditions are met. Verify error handling is functioning and ensure that appropriate error messages are returned. Authentication is successful and Sample test data is available in Source system Validate Data Accuracy Ensure that data is transferred accurately between systems without loss or corruption. Test the connector and workflow with minimum and maximum valid input values Check how the system behaves when input data exceeds specified limits or when unexpected data formats are encountered Try test data with values near to boundary values Verify that they handle edge cases correctly Test the robustness of the connector by simulating network failures or timeouts during communication with the target system. Ensure that data is transferred accurately between systems without loss or corruption and appropriate error messages are returned. Authentication is successful and Sample test Try loading data with VALID values data is available in Source system Try loading data with INVALID values 3 4 5 22/07/2024 Transformation Data Accuracy Negative Case EXPECTED RESULTS From Connector, trigger a connection request to the Source System Try connecting with INVALID values 2 ACTION STEPS Validate Data transformed Authentication is successful and Sample test Validate Data transformation in case of data is available in Source system failures Ensure data load is successful and transformation workflow is triggered Ensure that data is transferred accurately between systems without loss or corruption and appropriate error messages are returned. Ensure that timestamps, date ranges, or other temporal data are handled correctly. 1 Test Case - Connector Integration Testing.xlsx Test Strategy - NEW Connector To verify that the functionality of NEW Connector works according to the specifications. The test will execute and verify the test scripts, identify, fix and retest all high and medium severity defects per the entrance criteria, and prioritize lower severity defects for future fixing. Test Goals/ Objectives Sprint timelines A connector workflow will connect to a particular data source (Authentication/Authorization), extract metadata relevant to Atlan, and transform it in a way so it can be loaded/published to the product’s storage layer.Every meaningful entity brought in is defined as an Asset with any relevant information or properties defined as asset attributes. ● We are running a Sprint of Two weeks. ● Features implemented in a Sprint are deployed after ● Projected turn-around time for each feature is based on Estimation of the card in the Sprint Planning, discussed and planned on the complexity of it. Ready for Dev: ● HLD is prepared. ● Kick-Off for the card is done. Ready for Testing: ● Test case is designed and reviewed. ● Desk-check for the card is done. Lifecycle of Tasks / Cards Complete: ● Code is deployed to the QA environment. ● Manual testing is complete. ● High and Medium Bugs are fixed for the feature. In Production: ● Code is deployed to the PROD environment. ● Show-Case for the Sprint / Card is Complete. Identify required Test types Test Automation 1. Positive Scenarios Testing - Happy Path 2. Negative Scenarios Testing - Simualte Network and Server issues, Invalid Test data 3. Boundary Value Testing - Valid and invalid Edge and Boundary data conditions 4. Concurrency and Performance Testing - Load testing, Volume Testing, Response Time testing 5. Security Testing - common security vulnerabilities 6. Integration Testing - End to end scenarios, syncronization and consisitency 7. Usability - User experience 8. Compability Testing - work with different operating systems, browsers, or environments where it may be deployed. Our test automation strategy follows Test Pyramid approach to cover: ● Unit tests ● Integration tests ● End-to-End tests Defect tracking and reporting will be done in Trello in each story picked. Defect tracking & Reporting 22/07/2024 Severity of Defects: ● Blocker /Highest is a type of a bug that blocks further testing because the app or software crashes in a specific environment due to the bug. ● Critical error is connected with security and leads to the program shutdown, data loss or other serious damage. ● Major/High level of severity is assigned to a bug which negatively affects large areas of the software checked through certain types of testing. ● Minor/Medium error does not influence the app’s basic functions or the process of testing. ● Low - Bugs of low severity level have little impact on the program functioning. 2 Test Case - Connector Integration Testing.xlsx Connector Upgrade Testing Understanding the Changes: Review the release notes and documentation for the new version of the connector to understand the changes, enhancements, bug fixes, and any deprecated features. Identify the areas of the connector that are affected by the upgrade, such as APIs, configuration options, data formats, or compatibility with third-party systems. Regression Testing: Conduct comprehensive regression testing to ensure that existing functionality remains intact after the upgrade. Re-run existing test cases to verify that all previously implemented features and use cases still work as expected with the upgraded connector. Pay particular attention to critical functionalities and areas of the connector that are likely to be impacted by the upgrade. Compatibility Testing: Test the upgraded connector for compatibility with other systems, platforms, libraries, or dependencies in the environment. Verify that the connector works correctly with the latest versions of any third-party APIs, frameworks, or libraries it interacts with. Ensure backward compatibility with existing integrations and configurations to prevent disruptions to downstream systems or workflows. Functional Testing: Validate the new features, enhancements, or changes introduced in the upgraded connector. Develop and execute test cases specifically targeting the new functionality to ensure it behaves as expected and meets the requirements. Verify that any reported bugs or issues addressed in the upgrade have been resolved satisfactorily. Performance Testing: Measure the performance of the upgraded connector under various load conditions to ensure it meets performance requirements. Conduct stress testing, load testing, and endurance testing to assess how the connector handles concurrent requests, large data volumes, or extended periods of operation. Compare performance metrics, such as response times and throughput, between the old and upgraded versions to identify any performance improvements or regressions. Security Testing: Perform security testing to identify and mitigate potential security vulnerabilities introduced by the upgrade. Verify that sensitive data is handled securely, encryption protocols are up to date, and access controls are properly enforced. Test for common security vulnerabilities, such as injection attacks, authentication bypass, or data leakage, and ensure they are addressed. User Acceptance Testing (UAT): Involve end-users or stakeholders in UAT to validate that the upgraded connector meets their expectations and fulfills business requirements. Collect feedback from users regarding usability, functionality, and any issues encountered during testing. Address any reported issues or concerns before finalizing the upgrade for production deployment. Rollback Plan: Develop a rollback plan in case the upgrade causes unexpected issues or disruptions in production. Ensure that backups are in place and that the environment can be reverted to the previous state quickly and safely if necessary. Documentation and Training: Update documentation, user guides, and training materials to reflect the changes introduced by the upgraded connector. Provide training sessions or resources for administrators, developers, or end-users to familiarize them with the new features and functionality. Post-Upgrade Monitoring: Monitor the upgraded connector in production to detect any issues or performance regressions that may arise after deployment. Set up alerts, logging, and monitoring tools to track system health, error rates, and other relevant metrics. Continuously monitor user feedback and support tickets to address any post-upgrade issues promptly. 22/07/2024 3