[boblog] How to test steemgg | [bob日志] 如何测试steemgg
First thing first, thanks to @maiyude LOGO design for steemgg.
[EN]
Is testing https://steemgg.com easy?
Of course not.
Backend Level
- steemgg uses 'Mocha testing framework' to run Unit Test.
- We are using Travis as CI (Continuous Integration) to run it automatically for each commit.
API Level
- TODO: Yep, it's not covered at this moment. Sorry, guys.
- Though the API is public, but we're not officially announce it's public. So we still have time prepare test cases for API testing.
UI Level
- TODO: We will consider TestCafe to test UI automatically for each build. (NOT Selenium/Webdriver).
- UI build is triggered on Travis and deployed to our dev environment automatically.
Code Changing Process
- dev -> staging -> prod
- dev environment is pushed automatically for each commit to develop branch.
- staging environment is pushed after all necessary changes merged from develop to master branch.
- prod environment is pushed after stable tag is marked on master branch.
Dev & Testing Process
- Developer commit the changes with issue numbers (eg. #225), then mark issue label to 'fixed/done'
- Tester verify changes on different environment and mark them with different issue labels as below:
- dev - test new feature/bug fixing
- staging - test new feature/bug fixing, and Regression
- prod - test new feature/bug fixing, and Smoke, and Exploring
Keep Going
- Testing https://steemgg.com is fun.
- If you like testing, welcome to join.
- Any idea or feedback, welcome.
Support steemgg
- Come Play at https://steemgg.com
- Support @steemgg by Upvote, Resteem, Follow and Delegation
- Follow our @steemgg.curation curation trail steemauto
[CN]
测试 https://steemgg.com 容易吗?
当然不.
后端测试
- steemgg 使用 'Mocha testing framework' 来运行 Unit Test.
- 我们使用了 Travis 作为 CI (Continuous Integration 持续集成工具) 来自动集成每次新的代码提交。
API测试
- TODO: 对，这个现在还没来得及做. 不好意思，乡亲父老们.
- 我们还没有正式对外宣称我们的API是对外公开的，虽然代码都已经公开在那里了. 所以我们既然官方还没有承认这个公开的事实，那么我们就还有时间来做这个API测试. 为啥感觉我说得像掩耳盗铃一样的感觉...
前端测试
代码更新流程
- dev -> staging -> prod
- 每一次在develop的代码提交会自动部署到dev环境.
- 所有必要的修改从develop合并到master分支后，才推到staging环境.
- 当master分支正式打上tag后，会推到prod环境.
测试流程
- 开发人员在提交代码的同时附上issue的编号（比如#225），并且标注issue的状态为‘fixed/done’.
- 测试人员在不同的环境下分别进行测试，并根据具体环境的验证情况进行issue状态标注，用来表示在什么环境下已经通过测试:
- dev - 主要测试新功能和bug修复.
- staging - 主要测试新功能和bug修复，以及回归测试.
- prod - 主要测试新功能和bug修复，以及冒烟测试和探索式测试.
继续加油
- 测试 https://steemgg.com 其实很有挑战，也很有趣.
- 如果你也喜欢测试，欢迎来玩.
- 任何点子或返回，欢迎来稿.
支持 steemgg
- 欢迎来玩 https://steemgg.com
- 欢迎点赞，转帖，跟随和代理给 @steemgg
- 欢迎跟随 @steemgg.curation curation trail steemauto