上篇链接

milestone 1 milestone 2
appium 1. 配置在独立机器
2. 使用命令行启动		 n/a
mock server 1. 配置在独立机器
2. 多终端注册
3. 多终端配置加载
4. 使用sql数据库存储配置文件
5. 精简代码，删除无用功能		 1. 梳理日志
test case 1. 排队全套用例
2. 用例模板优化
3. 用例执行过程可以截屏		 1. 用例执行报告（email）
2. 每日构建，自动执行
3. 其它业务线主流程case
完成节点 排队业务主流程回归迁移到自动化测试 n/a

with iOS

前提

  1. iOS本身有清晰化的MVC结构，对View做测试

优点

  1. 组件输入的组合
  2. 包含截图的报表

不够完善

  1. 人肉验证

改进

  1. mock server 平台化，可供 iOS 使用

appium 文档阅读

http://appium.io/slate/en/master/?java#introduction-to-appium

appium的设计思想

  1. You shouldn’t have to recompile your app or modify it in any way in order to automate it.
  2. You shouldn’t be locked into a specific language or framework to write and run your tests.
  3. A mobile automation framework shouldn’t reinvent the wheel when it comes to automation APIs.
  4. A mobile automation framework should be open source, in spirit and practice as well as in name!

Parallel Android Tests

-p the main Appium port
-U the device id
-bp the Appium bootstrap port
–chromedriver-port the chromedriver port (if using webviews or chrome)
–selendroid-port the selendroid port (if using selendroid)

If we had two devices with the ID’s 43364 and 32456, we would start two different Appium servers with the following commands:

node . -p 4492 -bp 2251 -U 32456

node . -p 4491 -bp 2252 -U 43364

ignoreUnimportantViews

Another example of a use-case for settings would be telling appium to ignore elements which are not visible.s