What is Integration Testing

Integration testing focuses on verifying the interfaces and interactions between different modules or components of a software application. For us, this means testing each and every ticket on JIRA that results in a change to the Torus codebase. Integration testing will be ongoing, and all tests should be performed in Argos QA unless otherwise specified.

Integration Testing Checklist

  1. Test the ticket on Argos QA: Verify that the changes made in the ticket are deployed and available for testing in the Argos QA environment.

    1. Make sure the code is MERGED: Confirm that the code changes have been successfully merged into the main codebase and are ready for deployment.

    image.png

    b. Make sure the code is Deployed to the correct environment (Argos QA which is really torus-qa): Verify that the merged code has been deployed to the Argos QA environment, which is also known as torus-qa.

    image.png

    c. On occasion, you will be asked to test in a different environment, such as Argos Stage or Tokamak. Follow the same procedure as above.

  2. Make sure that you are clear on acceptance criteria and what needs to be tested - follow up with Mia if unclear: Review the acceptance criteria and requirements outlined in the ticket to ensure you understand what needs to be tested. If you have any questions or concerns, reach out to Mia for clarification.

  3. Run integration tests for each acceptance criterion: Perform integration tests to verify that each acceptance criterion is met. This may involve testing different scenarios, workflows, or user interactions to ensure the changes work as expected.

  4. Send details to Mia if it passed or not: After completing the integration tests, report the results to Mia, including any issues or defects found during testing. Provide detailed information about the tests performed, the results, and any observations or recommendations.

Additional best practices to consider