Git Android Project Integration with End-to-End Automatic Testing

Overview

This document outlines the integration between your Git Android project and the end-to-end automatic testing system. With this integration, when creating a pull request (PR), developers have the ability to add labels to generate an APK and trigger the automatic tests. The automatic test will run only on a portion of the end-to-end tests, ensuring efficient testing and faster feedback loops during the development process.

Integration Workflow

1. Pull Request Creation

When a developer creates a pull request on the Git Android project repository, they can include specific labels to trigger the APK feature generation and initiate the automatic test suite.

Above you can see how to find the label on PR creation.

2. Labeling System

A predefined set of labels has been established to facilitate the integration:

• generate-apk: This label triggers the generation of the APK feature associated with the changes made in the pull request.
• run-auto-test: This label initiates the execution of the automatic test suite.
• partial-auto-test: This label signifies that only a portion of the end-to-end automatic tests will be executed.

3. APK Generation

Upon the inclusion of the apk feature label in the pull request, the system initiates the process of generating an APK feature containing the changes proposed in the PR. This APK feature allows stakeholders to review the changes directly on a test device or emulator.

4. Automatic Test Suite Execution

Full Test Suite

The entire end-to-end automatic test suite will be executed by going to action tab on github, then run the apk feature script with UI test true. This comprehensive testing ensures the integrity of the application across various scenarios.

Partial Test Suite

When the partial-auto-test like the list below, only a portion of the end-to-end automatic tests will be executed. This selective testing approach aims to streamline the testing process, focusing on critical functionalities affected by the changes introduced in the pull request.

@chatlist @conversation @notifeed @crushTime @hub @listOfLikes @map @spots @notificationsFeed @deeplinks @editPictures @editProfile @editTraits @matchingPreferences @profileCertification @shops @various @checkFAQ @contactCustomerService @bannedAccount @report

5. Test Results and Feedback

Upon completion of the automatic test suite execution, developers receive detailed feedback regarding the test results directly within the pull request interface. Any failures or issues detected during testing are promptly highlighted, enabling developers to address them promptly with the allure report. The link of this report can be find in slack channel

Benefits

• Efficient Testing: The integration streamlines the testing process by automating APK generation and test suite execution based on predefined labels, reducing manual effort and time.
• Focused Testing: Developers can choose to run either the full test suite or a partial suite based on the nature of the changes, ensuring that testing efforts are focused on critical functionalities.
• Faster Feedback Loop: By providing immediate feedback within the pull request interface, developers can quickly identify and address any issues or failures detected during testing, facilitating faster iteration cycles.

Conclusion

The integration between your Git Android project and the end-to-end automatic testing system enhances the development workflow by automating key testing processes and providing developers with timely feedback. By leveraging the labeling system, developers can efficiently generate APK features and execute automatic tests, ensuring the quality and reliability of the application throughout the development lifecycle.