flybirds

Flybirds | English Version

Cross-end cross-frame BDD UI automation test solution

background

Flybirds is a front-end UI automation testing framework based on BDD mode, providing a series of out-of-the-box tools and complete documentation.

Multi-end R&D is an unavoidable topic for front-end development in today's era. In order to solve these problems, many development solutions have been launched in the industry, but there are not many solutions for cross-end UI automation testing.

Since its open source in early 2022, Flybirds has launched a cross-end and cross-framework testing solution of v0.4 through communication and feedback with active users in the community. It has launched a multi-terminal and plug-in architecture design, which also facilitates community developers to join and expand freely and jointly build and grow together.

What kind of multi-terminal testing solution do we need

In recent years, many new development frameworks have emerged every once in a while, which has brought better development experience and performance, and has also created many problems for automated testing.

What kind of multi-terminal testing solution do we need? From the perspective of Flybirds, we hope that multi-terminal testing will not become an obstacle in the R&D process, especially when the multi-terminal ecosystem is booming, automated testing solutions should grow together with development solutions.

Whether it is Web, Android, iOS, Flutter, React Native or mini-programs, the ideal solution should be adapted to multiple ends, retain good expansion, take into account more frameworks, and be jointly built by the community to promote overall ecological prosperity. Therefore, there is a cross-end cross-frame test solution provided by Flybirds to the community.

Plug-in architecture

The plug-in architecture helps us separate the capabilities of each end. The plug-in provides the components, APIs and configurations required at runtime, and Flybirds injects them into the corresponding life cycles separately.

• Based on Behave, the BDD tools needed to implement the association of "natural language test case documents" and "automated test code" in BDD.
• Based on Airtest, the APP-side UI automation testing capabilities are required to implement the APP-side UI automation testing capabilities required for "test cases can be executed on an automated test platform" in BDD.
• Based on Playwright, the Web-side UI automation testing capability is required to realize that "test cases can be executed on an automated test platform" in BDD.
• Based on PaddleOCR and OpenCV, the OCR and image recognition capabilities required in BDD that "test cases can be executed on an automated test platform" are realized.
• Based on Multiple-cucumber-html-reporter, visual test report is realized

File structure

 																
├─ cli	                        脚手架
├─ core
|   ├─ config_manage.py         配置管理
|   ├─ dsl
|   │    ├─ globalization       国际化处理
|   │    └─ step                Step 列表
|   ├─ global_resource.py       全局配置
|   ├─ launch_cycle             生命周期管理
|   └─ plugin
|        ├─ event               事件管理
|        ├─ plugin_manager.py   插件管理
|        └─ plugins					
|             ├─ android        Andriod 相关处理
|             ├─ ios            iOS 相关处理
|             └─ web            Web 相关处理
├─ report                       报告
├─ template                     模板处理
└─ utils								

characteristic

Using Flybirds you can complete most of the mobile phone automation operations. Here are some feature descriptions that help get started:

• Based on BDD pattern, natural language syntax
• Supports automated operations, form submission, UI element verification, keyboard input, Deeplink jump, etc.
• Supports Android, iOS, React Native, Flutter, Web
• Multi-end script reuse
• Supports multi-browser rendering engines: Chromium, WebKit and Firefox
• Supports compatibility testing in multi-browser concurrency mode
• By default, support English and Chinese languages, and support more language extensions
• Plug-in design, supports user-defined automation extensions
• Provide cli scaffolding to quickly build projects
• Provide html report

Enjoying this?

Please support us and click a Star

Tutorial

• Frequently Asked Questions
• Environmental preparation
• Check before running
• run
• Project details
• DSL step
• Android terminal example
• iOS terminal example
• OCR&OpenCV usage examples
• Web end example
• Multi-terminal application examples
• Data-driven parameterization
• Multi-browser concurrency
• Custom framework extensions
• Multilingual
• Continuous integration
• More details

contribute

1. Fork warehouse
2. Create a branch ( git checkout -b my-new-feature )
3. Submit modification ( git commit -am 'Add some feature' )
4. Push ( git push origin my-new-feature )
5. Create a PR

Welcome fork and feedback

If you have any suggestions or comments, please feel free to ask questions in the GitHub issues area

protocol

This warehouse complies with the MIT protocol

Acknowledgements

Thanks to the following repositories for making Flybirds better:

• airtest
• behave
• playwright
• multiple-cucumber-html-reporter
• PaddleOCR

Technical communication