简体   繁体   English

测试,问题跟踪,持续集成 - 推荐GAE和Android应用程序的标准工具

[英]Testing, Issue Tracking, Continuous Integration — recommended standard tooling for GAE and Android apps

I wanted to solicit some opinions on what would be ideal tools for the job. 我想征求一些关于什么是理想工具的意见。 I'd like to ideally use as few as possible and as tightly integrated as possible. 我希望尽可能少地使用并尽可能紧密地集成。 (I've read about 20 different threads on this and have some experience at work as well) (我已经阅读了大约20个不同的主题,并且在工作中也有一些经验)

For any of those, I would favor integrated solutions (so for example if a feature as a native capability of Android Studio, I'd rather use it) 对于其中任何一种,我都赞成集成解决方案(例如,如果一个功能作为Android Studio的本机功能,我宁愿使用它)

1) testing 1)测试

  • GAE backend -- LocalServiceTestHelper testing, regular unit testing GAE后端 - LocalServiceTestHelper测试,定期单元测试
  • App frontend -- Roboelectric, Robotium, Monkey App前端 - Roboelectric,Robotium,Monkey

2) test coverage -- EMMA??? 2)测试覆盖率 - EMMA ??? I think TeamCity comes with that as well. 我认为TeamCity也是如此。 anything else? 还要别的吗?

3) VCS -- Git/Github 3)VCS - Git / Github

4) issue detection + tracking 4)问题检测+跟踪

  • GAE backend -- dev console, logging GAE后端 - 开发控制台,日志记录
  • App frontent-- Crashlytics, debug builds local-log as well App frontent-- Crashlytics,debug也构建了local-log

Should I go with the integrated issue tracking in Github, or try JIRA? 我应该使用Github中的集成问题跟踪,还是尝试JIRA? Crashlytics seems to have integration with both which is good, or is there a different preferred tool by the community? Crashlytics似乎与两者融为一体,或社区有不同的首选工具?

5) CI 5)CI

  • GAE backend -- Jenkins? GAE后端 - 詹金斯? TeamCity? TeamCity的? Perhaps some google solution in dev? 也许开发中的一些谷歌解决方案?
  • App frontend -- Jenkins? App前端 - 詹金斯? TeamCity? TeamCity的?

6) Communicating with your users -- an integrated solution that can update facebook, twitter, google+ and potentially a forum-based community site. 6)与您的用户沟通 - 一个集成的解决方案,可以更新Facebook,Twitter,谷歌+和潜在的基于论坛的社区网站。 Any nifty solutions in that space? 那个空间里有什么漂亮的解决方案吗?

Thanks very much. 非常感谢。

While this question does bring up excellent discussion points, it is not one that can have a specific technical answer. 虽然这个问题确实提出了很好的讨论要点,但它不是一个可以有特定技术答案的问题。 The appropriateness of tools for continuous integration using Google App Engine depends on business needs, scale, budget, development team, skills, etc. 使用Google App Engine进行持续集成的工具的适当性取决于业务需求,规模,预算,开发团队,技能等。

I strongly suggest posting this interesting question/discussion on the App Engine Google Groups for a hopefully lively and heated exchange. 我强烈建议在App Engine Google Groups上发布这个有趣的问题/讨论,以获得充满希望的热烈交流。 Should you choose to do so, please post a link to the thread here in a comment so others finding this post can follow through. 如果您选择这样做,请在评论中发布此帖子的链接,以便其他人查找此帖子可以继续。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM