Kea2-python 0.3.0__tar.gz → 0.3.2__tar.gz

{kea2_python-0.3.0 → kea2_python-0.3.2}/Kea2_python.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: Kea2-python
-Version: 0.3.0
+Version: 0.3.2
 Summary: A python library for supporting and customizing automated UI testing for mobile apps
 Author-email: Xixian Liang <xixian@stu.ecnu.edu.cn>
 Requires-Python: >=3.8
@@ -10,6 +10,7 @@ Requires-Dist: rtree>=1.3.0
 Requires-Dist: jinja2>=3.0.0
 Requires-Dist: uiautomator2>=3.3.3
 Requires-Dist: adbutils>=2.9.3
+Requires-Dist: setuptools>=75.3.2
 Dynamic: license-file
 
 
@@ -17,6 +18,7 @@ Dynamic: license-file
 [![PyPI](https://img.shields.io/pypi/v/kea2-python.svg)](https://pypi.python.org/pypi/kea2-python)
 [![PyPI Downloads](https://static.pepy.tech/badge/kea2-python)](https://pepy.tech/projects/kea2-python)
 ![Python](https://img.shields.io/badge/python-3.8%2B-blue)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/ecnusse/Kea2)
 
 <div>
     <img src="https://github.com/user-attachments/assets/84e47b87-2dd2-4d7e-91d1-e8c1d1db0cf4" style="border-radius: 14px; width: 20%; height: 20%;"/> 
@@ -31,6 +33,13 @@ The group has reached its capacity. Please contact Xixian Liang at [xixian@stu.e
 
 ## About 
 
+<div align="center">
+    <img src="docs/images/kea2_logo.png" alt="kea_logo" style="border-radius: 14px; width: 20%; height: 20%;"/>
+</div>
+<div align="center">
+    <a href="https://en.wikipedia.org/wiki/Kea">Kea2's logo: A large parrot skilled in finding "bugs"</a>
+</div>
+
 Kea2 is an easy-to-use tool for fuzzing mobile apps. Its key *novelty* is able to fuse automated UI testing with scripts (usually written by human), thus empowering automated UI testing with human intelligence for effectively finding *crashing bugs* as well as *non-crashing functional (logic) bugs*. 
 
 Kea2 is currently built on top of [Fastbot](https://github.com/bytedance/Fastbot_Android), *an industrial-strength automated UI testing tool*, and [uiautomator2](https://github.com/openatx/uiautomator2), *an easy-to-use and stable Android automation library*.
@@ -40,7 +49,7 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 
 <div align="center">
     <div style="max-width:80%; max-height:80%">
-    <img src="docs/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
+    <img src="docs/images/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
     </div>
 </div>
 
@@ -60,11 +69,17 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 | **Finding crashes in deep states** |  | :+1: | :+1: |
 | **Finding non-crashing functional (logic) bugs** |  |  | :+1: |
 
-## Kea2's Known Users
+## Kea2's Users
+
+Kea2 (and its idea) has been used/integrated by
 
-[OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app
+- [OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app. OPay uses Kea2 for regression testing on POS machines and mobile devices.
 
-We are glad to hear if you are using Kea2 for your app.
+- [WeChat's iExplorer]() --- WeChat's in-house testing platform
+
+- [ByteDance's Fastbot](https://github.com/bytedance/Fastbot_Android)
+
+Please let us know and willing to hear your feedback/questions if you are also using Kea2.
 
 ## Design & Roadmap
 Kea2 currently works with:
@@ -82,7 +97,7 @@ In the future, Kea2 will be extended to support
 
 Running environment:
 - support Windows, MacOS and Linux
-- python 3.8+, Android 5.0+ (Android SDK installed)
+- python 3.8+, Android 5.0~16.0 (Android SDK installed)
 - **VPN closed** (Features 2 and 3 required)
 
 Install Kea2 by `pip`:
@@ -193,7 +208,7 @@ In Feature 3, a script is composed of three elements:
 In a social media app, message sending is a common feature. On the message sending page, the `send` button should always appears when the input box is not empty (i.e., has some message).
 
 <div align="center">
-    <img src="docs/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
+    <img src="docs/images/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
 </div>
 
 <div align="center">
@@ -230,7 +245,55 @@ You can find the [user manual](docs/manual_en.md), which includes:
 - How to run Kea2 and Kea2's command line options
 - How to find and understand Kea2's testing results
 - How to [whitelist or blacklist](docs/blacklisting.md) specific activities, UI widgets and UI regions during fuzzing
-- [Common Q&A for PBT and Kea2](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink)
+- [Q&A for Kea2 and PBT (对Kea2和PBT技术的常见问题和回答)](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink) 
+
+Some blogs on Kea/Kea2 (in Chinese):
+- [别再苦哈哈写测试脚本了，生成它们吧！(一)](https://mp.weixin.qq.com/s/R2kLCkXpDjpa8wCX4Eidtg)
+- [别再苦哈哈写测试脚本了，生成它们吧！(二)](https://mp.weixin.qq.com/s/s4WkdstNcKupu9OP8jeOXw)
+- [别再苦哈哈写测试脚本了，生成它们吧！(三)](https://mp.weixin.qq.com/s/BjXyo-xJRmPB_sCc4pmh8g)
+- [2025 Let’s GoSSIP 软件安全暑期学校预告第一弹——Kea2](https://mp.weixin.qq.com/s/8_0_GNNin8E5BqTbJU33wg)
+- [功能性质驱动的测试技术：下一代GUI自动化测试技术](https://appw8oh6ysg4044.xet.citv.cn/p/course/video/v_6882fa14e4b0694ca0ec0a1b) --- 视频回放&PPT@MTSC 2025
+
+工业界对Kea2的理解和评价（点击箭头查看详情）：
+
+<details>
+  <summary>Kea2的性质是什么含义？Kea2意义和价值是什么？</summary>
+
+    kea2 其实是一个工具，它是python+u2+fastbot的集合体。 它本身更像是一台装好了发动机和轮子的汽车底盘。
+
+    性质是苏老师他们团队提出的一个概念， 转换到测试领域的实际工作中，性质对应的是最小单位的功能（原子级功能），性质的依赖条件很少或没有，它可以自身运行。一个典型的性质就是登录，它仅仅具有输入用户名，输入密码，提交。再举个例子，给视频点个赞，也就是简单的两三步。就是一个性质。
+
+    性质与kea2结合的意义是在于解决过去使用appium过重的问题。用appium去测试一个性质通常要写很多行的代码，引导界面到达性质的位置。但使用kea2，就只需要编写性质，如何到其所在的位置是交给fastbot和它的学习算法来搞定的。 
+
+    kea2另个重大的价值是，它解决了上述思想所需要的技术支撑，比appium更轻量的UI编写方式，fastbot编写性质的能力不足，以及无法编写逻辑和断言。整体上是保留了fastbot以往的优秀品质，完善了其不足和短板。
+
+    简而言之，需要做传统的编排型的功能测试，仍然使用appium，使用kea2也行，但你感觉不到它的价值。本身有需要做混沌测试，模糊测试，兼容性测试。那么强烈，强烈推荐kea2。kea2更偏探索性测试而非编排型。
+</details>
+
+<details>
+  <summary>kea2组成是什么？kea2的核心作用？kea2做了什么？</summary>
+
+kea2 组成：
+
+    fastbot  --  fuzz测试引擎，负责跑路。
+    u2 -- 负责进行业务空间的操作。与使用selenium，appium，没什么区别。
+    python --  u2的操作，逻辑的编写，定制化的实现。
+
+kea2的核心作用：
+
+    提供了条件触发器。 在FB跑路的时候，会不停遍历条件触发器，一旦触发，挂起FB，开始执行触发器指定的 ui test 及 assert。执行完毕，继续切回FB跑路。
+
+hea2做了什么：
+
+    替换了FB的条件触发功能。
+    替换了FB的黑名单，黑控件功能。
+    替换了FB剪枝功能。
+    增加了多元化的元素空间操作能力。
+    增加了fuzz测试中的 逻辑设定。
+    增加了断言能力。
+    增加了元素操作能力。
+</details>
+
 
 ## Open-source projects used by Kea2
 

{kea2_python-0.3.0 → kea2_python-0.3.2}/Kea2_python.egg-info/requires.txt

@@ -2,3 +2,4 @@ rtree>=1.3.0
 jinja2>=3.0.0
 uiautomator2>=3.3.3
 adbutils>=2.9.3
+setuptools>=75.3.2

{kea2_python-0.3.0 → kea2_python-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: Kea2-python
-Version: 0.3.0
+Version: 0.3.2
 Summary: A python library for supporting and customizing automated UI testing for mobile apps
 Author-email: Xixian Liang <xixian@stu.ecnu.edu.cn>
 Requires-Python: >=3.8
@@ -10,6 +10,7 @@ Requires-Dist: rtree>=1.3.0
 Requires-Dist: jinja2>=3.0.0
 Requires-Dist: uiautomator2>=3.3.3
 Requires-Dist: adbutils>=2.9.3
+Requires-Dist: setuptools>=75.3.2
 Dynamic: license-file
 
 
@@ -17,6 +18,7 @@ Dynamic: license-file
 [![PyPI](https://img.shields.io/pypi/v/kea2-python.svg)](https://pypi.python.org/pypi/kea2-python)
 [![PyPI Downloads](https://static.pepy.tech/badge/kea2-python)](https://pepy.tech/projects/kea2-python)
 ![Python](https://img.shields.io/badge/python-3.8%2B-blue)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/ecnusse/Kea2)
 
 <div>
     <img src="https://github.com/user-attachments/assets/84e47b87-2dd2-4d7e-91d1-e8c1d1db0cf4" style="border-radius: 14px; width: 20%; height: 20%;"/> 
@@ -31,6 +33,13 @@ The group has reached its capacity. Please contact Xixian Liang at [xixian@stu.e
 
 ## About 
 
+<div align="center">
+    <img src="docs/images/kea2_logo.png" alt="kea_logo" style="border-radius: 14px; width: 20%; height: 20%;"/>
+</div>
+<div align="center">
+    <a href="https://en.wikipedia.org/wiki/Kea">Kea2's logo: A large parrot skilled in finding "bugs"</a>
+</div>
+
 Kea2 is an easy-to-use tool for fuzzing mobile apps. Its key *novelty* is able to fuse automated UI testing with scripts (usually written by human), thus empowering automated UI testing with human intelligence for effectively finding *crashing bugs* as well as *non-crashing functional (logic) bugs*. 
 
 Kea2 is currently built on top of [Fastbot](https://github.com/bytedance/Fastbot_Android), *an industrial-strength automated UI testing tool*, and [uiautomator2](https://github.com/openatx/uiautomator2), *an easy-to-use and stable Android automation library*.
@@ -40,7 +49,7 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 
 <div align="center">
     <div style="max-width:80%; max-height:80%">
-    <img src="docs/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
+    <img src="docs/images/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
     </div>
 </div>
 
@@ -60,11 +69,17 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 | **Finding crashes in deep states** |  | :+1: | :+1: |
 | **Finding non-crashing functional (logic) bugs** |  |  | :+1: |
 
-## Kea2's Known Users
+## Kea2's Users
+
+Kea2 (and its idea) has been used/integrated by
 
-[OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app
+- [OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app. OPay uses Kea2 for regression testing on POS machines and mobile devices.
 
-We are glad to hear if you are using Kea2 for your app.
+- [WeChat's iExplorer]() --- WeChat's in-house testing platform
+
+- [ByteDance's Fastbot](https://github.com/bytedance/Fastbot_Android)
+
+Please let us know and willing to hear your feedback/questions if you are also using Kea2.
 
 ## Design & Roadmap
 Kea2 currently works with:
@@ -82,7 +97,7 @@ In the future, Kea2 will be extended to support
 
 Running environment:
 - support Windows, MacOS and Linux
-- python 3.8+, Android 5.0+ (Android SDK installed)
+- python 3.8+, Android 5.0~16.0 (Android SDK installed)
 - **VPN closed** (Features 2 and 3 required)
 
 Install Kea2 by `pip`:
@@ -193,7 +208,7 @@ In Feature 3, a script is composed of three elements:
 In a social media app, message sending is a common feature. On the message sending page, the `send` button should always appears when the input box is not empty (i.e., has some message).
 
 <div align="center">
-    <img src="docs/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
+    <img src="docs/images/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
 </div>
 
 <div align="center">
@@ -230,7 +245,55 @@ You can find the [user manual](docs/manual_en.md), which includes:
 - How to run Kea2 and Kea2's command line options
 - How to find and understand Kea2's testing results
 - How to [whitelist or blacklist](docs/blacklisting.md) specific activities, UI widgets and UI regions during fuzzing
-- [Common Q&A for PBT and Kea2](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink)
+- [Q&A for Kea2 and PBT (对Kea2和PBT技术的常见问题和回答)](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink) 
+
+Some blogs on Kea/Kea2 (in Chinese):
+- [别再苦哈哈写测试脚本了，生成它们吧！(一)](https://mp.weixin.qq.com/s/R2kLCkXpDjpa8wCX4Eidtg)
+- [别再苦哈哈写测试脚本了，生成它们吧！(二)](https://mp.weixin.qq.com/s/s4WkdstNcKupu9OP8jeOXw)
+- [别再苦哈哈写测试脚本了，生成它们吧！(三)](https://mp.weixin.qq.com/s/BjXyo-xJRmPB_sCc4pmh8g)
+- [2025 Let’s GoSSIP 软件安全暑期学校预告第一弹——Kea2](https://mp.weixin.qq.com/s/8_0_GNNin8E5BqTbJU33wg)
+- [功能性质驱动的测试技术：下一代GUI自动化测试技术](https://appw8oh6ysg4044.xet.citv.cn/p/course/video/v_6882fa14e4b0694ca0ec0a1b) --- 视频回放&PPT@MTSC 2025
+
+工业界对Kea2的理解和评价（点击箭头查看详情）：
+
+<details>
+  <summary>Kea2的性质是什么含义？Kea2意义和价值是什么？</summary>
+
+    kea2 其实是一个工具，它是python+u2+fastbot的集合体。 它本身更像是一台装好了发动机和轮子的汽车底盘。
+
+    性质是苏老师他们团队提出的一个概念， 转换到测试领域的实际工作中，性质对应的是最小单位的功能（原子级功能），性质的依赖条件很少或没有，它可以自身运行。一个典型的性质就是登录，它仅仅具有输入用户名，输入密码，提交。再举个例子，给视频点个赞，也就是简单的两三步。就是一个性质。
+
+    性质与kea2结合的意义是在于解决过去使用appium过重的问题。用appium去测试一个性质通常要写很多行的代码，引导界面到达性质的位置。但使用kea2，就只需要编写性质，如何到其所在的位置是交给fastbot和它的学习算法来搞定的。 
+
+    kea2另个重大的价值是，它解决了上述思想所需要的技术支撑，比appium更轻量的UI编写方式，fastbot编写性质的能力不足，以及无法编写逻辑和断言。整体上是保留了fastbot以往的优秀品质，完善了其不足和短板。
+
+    简而言之，需要做传统的编排型的功能测试，仍然使用appium，使用kea2也行，但你感觉不到它的价值。本身有需要做混沌测试，模糊测试，兼容性测试。那么强烈，强烈推荐kea2。kea2更偏探索性测试而非编排型。
+</details>
+
+<details>
+  <summary>kea2组成是什么？kea2的核心作用？kea2做了什么？</summary>
+
+kea2 组成：
+
+    fastbot  --  fuzz测试引擎，负责跑路。
+    u2 -- 负责进行业务空间的操作。与使用selenium，appium，没什么区别。
+    python --  u2的操作，逻辑的编写，定制化的实现。
+
+kea2的核心作用：
+
+    提供了条件触发器。 在FB跑路的时候，会不停遍历条件触发器，一旦触发，挂起FB，开始执行触发器指定的 ui test 及 assert。执行完毕，继续切回FB跑路。
+
+hea2做了什么：
+
+    替换了FB的条件触发功能。
+    替换了FB的黑名单，黑控件功能。
+    替换了FB剪枝功能。
+    增加了多元化的元素空间操作能力。
+    增加了fuzz测试中的 逻辑设定。
+    增加了断言能力。
+    增加了元素操作能力。
+</details>
+
 
 ## Open-source projects used by Kea2
 

{kea2_python-0.3.0 → kea2_python-0.3.2}/README.md

@@ -3,6 +3,7 @@
 [![PyPI](https://img.shields.io/pypi/v/kea2-python.svg)](https://pypi.python.org/pypi/kea2-python)
 [![PyPI Downloads](https://static.pepy.tech/badge/kea2-python)](https://pepy.tech/projects/kea2-python)
 ![Python](https://img.shields.io/badge/python-3.8%2B-blue)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/ecnusse/Kea2)
 
 <div>
     <img src="https://github.com/user-attachments/assets/84e47b87-2dd2-4d7e-91d1-e8c1d1db0cf4" style="border-radius: 14px; width: 20%; height: 20%;"/> 
@@ -17,6 +18,13 @@ The group has reached its capacity. Please contact Xixian Liang at [xixian@stu.e
 
 ## About 
 
+<div align="center">
+    <img src="docs/images/kea2_logo.png" alt="kea_logo" style="border-radius: 14px; width: 20%; height: 20%;"/>
+</div>
+<div align="center">
+    <a href="https://en.wikipedia.org/wiki/Kea">Kea2's logo: A large parrot skilled in finding "bugs"</a>
+</div>
+
 Kea2 is an easy-to-use tool for fuzzing mobile apps. Its key *novelty* is able to fuse automated UI testing with scripts (usually written by human), thus empowering automated UI testing with human intelligence for effectively finding *crashing bugs* as well as *non-crashing functional (logic) bugs*. 
 
 Kea2 is currently built on top of [Fastbot](https://github.com/bytedance/Fastbot_Android), *an industrial-strength automated UI testing tool*, and [uiautomator2](https://github.com/openatx/uiautomator2), *an easy-to-use and stable Android automation library*.
@@ -26,7 +34,7 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 
 <div align="center">
     <div style="max-width:80%; max-height:80%">
-    <img src="docs/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
+    <img src="docs/images/intro.png" style="border-radius: 14px; width: 80%; height: 80%;"/> 
     </div>
 </div>
 
@@ -46,11 +54,17 @@ Kea2 currently targets [Android](https://en.wikipedia.org/wiki/Android_(operatin
 | **Finding crashes in deep states** |  | :+1: | :+1: |
 | **Finding non-crashing functional (logic) bugs** |  |  | :+1: |
 
-## Kea2's Known Users
+## Kea2's Users
+
+Kea2 (and its idea) has been used/integrated by
 
-[OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app
+- [OPay Business](https://play.google.com/store/apps/details?id=team.opay.pay.merchant.service) --- a financial & payment app. OPay uses Kea2 for regression testing on POS machines and mobile devices.
 
-We are glad to hear if you are using Kea2 for your app.
+- [WeChat's iExplorer]() --- WeChat's in-house testing platform
+
+- [ByteDance's Fastbot](https://github.com/bytedance/Fastbot_Android)
+
+Please let us know and willing to hear your feedback/questions if you are also using Kea2.
 
 ## Design & Roadmap
 Kea2 currently works with:
@@ -68,7 +82,7 @@ In the future, Kea2 will be extended to support
 
 Running environment:
 - support Windows, MacOS and Linux
-- python 3.8+, Android 5.0+ (Android SDK installed)
+- python 3.8+, Android 5.0~16.0 (Android SDK installed)
 - **VPN closed** (Features 2 and 3 required)
 
 Install Kea2 by `pip`:
@@ -179,7 +193,7 @@ In Feature 3, a script is composed of three elements:
 In a social media app, message sending is a common feature. On the message sending page, the `send` button should always appears when the input box is not empty (i.e., has some message).
 
 <div align="center">
-    <img src="docs/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
+    <img src="docs/images/socialAppBug.png" style="border-radius: 14px; width:30%; height:40%;"/>
 </div>
 
 <div align="center">
@@ -216,7 +230,55 @@ You can find the [user manual](docs/manual_en.md), which includes:
 - How to run Kea2 and Kea2's command line options
 - How to find and understand Kea2's testing results
 - How to [whitelist or blacklist](docs/blacklisting.md) specific activities, UI widgets and UI regions during fuzzing
-- [Common Q&A for PBT and Kea2](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink)
+- [Q&A for Kea2 and PBT (对Kea2和PBT技术的常见问题和回答)](https://sy8pzmhmun.feishu.cn/wiki/SLGwwqgzIiEuC3kwmV8cSZY0nTg?from=from_copylink) 
+
+Some blogs on Kea/Kea2 (in Chinese):
+- [别再苦哈哈写测试脚本了，生成它们吧！(一)](https://mp.weixin.qq.com/s/R2kLCkXpDjpa8wCX4Eidtg)
+- [别再苦哈哈写测试脚本了，生成它们吧！(二)](https://mp.weixin.qq.com/s/s4WkdstNcKupu9OP8jeOXw)
+- [别再苦哈哈写测试脚本了，生成它们吧！(三)](https://mp.weixin.qq.com/s/BjXyo-xJRmPB_sCc4pmh8g)
+- [2025 Let’s GoSSIP 软件安全暑期学校预告第一弹——Kea2](https://mp.weixin.qq.com/s/8_0_GNNin8E5BqTbJU33wg)
+- [功能性质驱动的测试技术：下一代GUI自动化测试技术](https://appw8oh6ysg4044.xet.citv.cn/p/course/video/v_6882fa14e4b0694ca0ec0a1b) --- 视频回放&PPT@MTSC 2025
+
+工业界对Kea2的理解和评价（点击箭头查看详情）：
+
+<details>
+  <summary>Kea2的性质是什么含义？Kea2意义和价值是什么？</summary>
+
+    kea2 其实是一个工具，它是python+u2+fastbot的集合体。 它本身更像是一台装好了发动机和轮子的汽车底盘。
+
+    性质是苏老师他们团队提出的一个概念， 转换到测试领域的实际工作中，性质对应的是最小单位的功能（原子级功能），性质的依赖条件很少或没有，它可以自身运行。一个典型的性质就是登录，它仅仅具有输入用户名，输入密码，提交。再举个例子，给视频点个赞，也就是简单的两三步。就是一个性质。
+
+    性质与kea2结合的意义是在于解决过去使用appium过重的问题。用appium去测试一个性质通常要写很多行的代码，引导界面到达性质的位置。但使用kea2，就只需要编写性质，如何到其所在的位置是交给fastbot和它的学习算法来搞定的。 
+
+    kea2另个重大的价值是，它解决了上述思想所需要的技术支撑，比appium更轻量的UI编写方式，fastbot编写性质的能力不足，以及无法编写逻辑和断言。整体上是保留了fastbot以往的优秀品质，完善了其不足和短板。
+
+    简而言之，需要做传统的编排型的功能测试，仍然使用appium，使用kea2也行，但你感觉不到它的价值。本身有需要做混沌测试，模糊测试，兼容性测试。那么强烈，强烈推荐kea2。kea2更偏探索性测试而非编排型。
+</details>
+
+<details>
+  <summary>kea2组成是什么？kea2的核心作用？kea2做了什么？</summary>
+
+kea2 组成：
+
+    fastbot  --  fuzz测试引擎，负责跑路。
+    u2 -- 负责进行业务空间的操作。与使用selenium，appium，没什么区别。
+    python --  u2的操作，逻辑的编写，定制化的实现。
+
+kea2的核心作用：
+
+    提供了条件触发器。 在FB跑路的时候，会不停遍历条件触发器，一旦触发，挂起FB，开始执行触发器指定的 ui test 及 assert。执行完毕，继续切回FB跑路。
+
+hea2做了什么：
+
+    替换了FB的条件触发功能。
+    替换了FB的黑名单，黑控件功能。
+    替换了FB剪枝功能。
+    增加了多元化的元素空间操作能力。
+    增加了fuzz测试中的 逻辑设定。
+    增加了断言能力。
+    增加了元素操作能力。
+</details>
+
 
 ## Open-source projects used by Kea2
 

{kea2_python-0.3.0 → kea2_python-0.3.2}/kea2/bug_report_generator.py

@@ -9,7 +9,7 @@ from concurrent.futures import ThreadPoolExecutor
 
 from PIL import Image, ImageDraw, ImageFont
 from jinja2 import Environment, FileSystemLoader, select_autoescape, PackageLoader
-from kea2.utils import getLogger
+from kea2.utils import getLogger, catchException
 
 logger = getLogger(__name__)
 
@@ -421,27 +421,24 @@ class BugReportGenerator:
         step_data["Info"] = json.loads(step_data["Info"])
         return step_data
 
+    @catchException("Error when marking screenshot")
     def _mark_screenshot(self, step_data: StepData):
-        try:
-            step_type = step_data["Type"]
-            screenshot_name = step_data["Screenshot"]
-            if not screenshot_name:
-                return
-
-            if step_type == "Monkey":
-                act = step_data["Info"].get("act")
-                pos = step_data["Info"].get("pos")
-                if act in ["CLICK", "LONG_CLICK"] or act.startswith("SCROLL"):
-                    self._mark_screenshot_interaction(step_type, screenshot_name, act, pos)
-
-            elif step_type == "Script":
-                act = step_data["Info"].get("method")
-                pos = step_data["Info"].get("params")
-                if act in ["click", "setText", "swipe"]:
-                    self._mark_screenshot_interaction(step_type, screenshot_name, act, pos)
+        step_type = step_data["Type"]
+        screenshot_name = step_data["Screenshot"]
+        if not screenshot_name:
+            return
 
-        except Exception as e:
-            logger.error(f"Error when marking screenshots: {e}")
+        if step_type == "Monkey":
+            act = step_data["Info"].get("act")
+            pos = step_data["Info"].get("pos")
+            if act in ["CLICK", "LONG_CLICK"] or act.startswith("SCROLL"):
+                self._mark_screenshot_interaction(step_type, screenshot_name, act, pos)
+
+        elif step_type == "Script":
+            act = step_data["Info"].get("method")
+            pos = step_data["Info"].get("params")
+            if act in ["click", "setText", "swipe"]:
+                self._mark_screenshot_interaction(step_type, screenshot_name, act, pos)
 
 
     def _mark_screenshot_interaction(self, step_type: str, screenshot_name: str, action_type: str, position: Union[List, Tuple]) -> bool:
@@ -528,65 +525,61 @@ class BugReportGenerator:
         img.save(screenshot_path)
         return True
 
+    @catchException("Error rendering template")
     def _generate_html_report(self, data: ReportData):
         """
         Generate HTML format bug report
         """
-        try:
-            # Format timestamp for display
-            timestamp = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
-
-            # Ensure coverage_trend has data
-            if not data["coverage_trend"]:
-                logger.warning("No coverage trend data")
-                # Use the same field names as in coverage.log file
-                data["coverage_trend"] = [{"stepsCount": 0, "coverage": 0, "testedActivitiesCount": 0}]
-
-            # Convert coverage_trend to JSON string, ensuring all data points are included
-            coverage_trend_json = json.dumps(data["coverage_trend"])
-            logger.debug(f"Number of coverage trend data points: {len(data['coverage_trend'])}")
-
-            # Prepare template data
-            template_data = {
-                'timestamp': timestamp,
-                'bugs_found': data["bugs_found"],
-                'total_testing_time': data["total_testing_time"],
-                'executed_events': data["executed_events"],
-                'coverage_percent': round(data["coverage"], 2),
-                'total_activities_count': data["total_activities_count"],
-                'tested_activities_count': data["tested_activities_count"],
-                'tested_activities': data["tested_activities"],
-                'total_activities': data["total_activities"],
-                'all_properties_count': data["all_properties_count"],
-                'executed_properties_count': data["executed_properties_count"],
-                'items_per_page': 10,  # Items to display per page
-                'screenshots': self.screenshots,
-                'property_violations': data["property_violations"],
-                'property_stats': data["property_stats"],
-                'property_error_details': data["property_error_details"],
-                'coverage_data': coverage_trend_json,
-                'take_screenshots': self.take_screenshots,  # Pass screenshot setting to template
-                'property_execution_trend': data["property_execution_trend"],
-                'property_execution_data': json.dumps(data["property_execution_trend"]),
-                'activity_count_history': data["activity_count_history"],
-                'crash_events': data["crash_events"],
-                'anr_events': data["anr_events"]
-            }
-
-            # Check if template exists, if not create it
-            template_path = Path(__file__).parent / "templates" / "bug_report_template.html"
-            if not template_path.exists():
-                logger.warning("Template file does not exist, creating default template...")
+        # Format timestamp for display
+        timestamp = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
+
+        # Ensure coverage_trend has data
+        if not data["coverage_trend"]:
+            logger.warning("No coverage trend data")
+            # Use the same field names as in coverage.log file
+            data["coverage_trend"] = [{"stepsCount": 0, "coverage": 0, "testedActivitiesCount": 0}]
+
+        # Convert coverage_trend to JSON string, ensuring all data points are included
+        coverage_trend_json = json.dumps(data["coverage_trend"])
+        logger.debug(f"Number of coverage trend data points: {len(data['coverage_trend'])}")
+
+        # Prepare template data
+        template_data = {
+            'timestamp': timestamp,
+            'bugs_found': data["bugs_found"],
+            'total_testing_time': data["total_testing_time"],
+            'executed_events': data["executed_events"],
+            'coverage_percent': round(data["coverage"], 2),
+            'total_activities_count': data["total_activities_count"],
+            'tested_activities_count': data["tested_activities_count"],
+            'tested_activities': data["tested_activities"],
+            'total_activities': data["total_activities"],
+            'all_properties_count': data["all_properties_count"],
+            'executed_properties_count': data["executed_properties_count"],
+            'items_per_page': 10,  # Items to display per page
+            'screenshots': self.screenshots,
+            'property_violations': data["property_violations"],
+            'property_stats': data["property_stats"],
+            'property_error_details': data["property_error_details"],
+            'coverage_data': coverage_trend_json,
+            'take_screenshots': self.take_screenshots,  # Pass screenshot setting to template
+            'property_execution_trend': data["property_execution_trend"],
+            'property_execution_data': json.dumps(data["property_execution_trend"]),
+            'activity_count_history': data["activity_count_history"],
+            'crash_events': data["crash_events"],
+            'anr_events': data["anr_events"]
+        }
 
-            # Use Jinja2 to render template
-            template = self.jinja_env.get_template("bug_report_template.html")
-            html_content = template.render(**template_data)
+        # Check if template exists, if not create it
+        template_path = Path(__file__).parent / "templates" / "bug_report_template.html"
+        if not template_path.exists():
+            logger.warning("Template file does not exist, creating default template...")
 
-            return html_content
+        # Use Jinja2 to render template
+        template = self.jinja_env.get_template("bug_report_template.html")
+        html_content = template.render(**template_data)
 
-        except Exception as e:
-            logger.error(f"Error rendering template: {e}")
-            raise
+        return html_content
 
     def _add_screenshot_info(self, step_data: StepData, step_index: int, data: Dict):
         """
@@ -697,9 +690,7 @@ class BugReportGenerator:
                     data["property_violations"].append({
                         "index": index,
                         "property_name": property_name,
-                        "precondition_page": start_step,
-                        "interaction_pages": [start_step, end_step],
-                        "postcondition_page": end_step
+                        "interaction_pages": [start_step, end_step]
                     })
                     index += 1
 

{kea2_python-0.3.0 → kea2_python-0.3.2}/kea2/fastbotManager.py

@@ -3,7 +3,7 @@ from retry.api import retry_call
 from dataclasses import asdict
 import requests
 from time import sleep
-
+from pkg_resources import parse_version
 
 from uiautomator2.core import HTTPResponse, _http_request
 from kea2.adbUtils import ADBDevice, ADBStreamShell_V2
@@ -28,6 +28,7 @@ class FastbotManager:
         self._device_output_dir = None
         ADBDevice.setDevice(options.serial, options.transport_id)
         self.dev = ADBDevice()
+        self.android_release = parse_version(self.dev.getprop("ro.build.version.release"))
 
     def _activateFastbot(self) -> ADBStreamShell_V2:
         """
@@ -219,7 +220,7 @@ class FastbotManager:
         if self.thread.is_running():
             logger.info("Waiting for Fastbot to exit.")
             return self.thread.wait()
-        return self.thread.poll()
+        return self.thread.poll() if self.android_release >= parse_version("7.0") else 0
 
     def start(self):
         # kill the fastbot process if runing.