question:
1. Lack of timely and effective communication between testing, development, and products.
2. Lack of definition of on-line standards.
3. The test time is relatively short and there is a shortage of personnel.
ways to improve:
1. After the product requirements come out, the test needs to write test cases according to the product requirements, and review and confirm the use cases together with the test, development and product.
2. During the testing process, the testing needs to carry out common types of testing (generally including: functional testing, user experience testing, weak network testing, compatibility testing, performance testing).
3. Every day before the release, the test will count the severity and status distribution of BUG, and list the serious problem BUG list, and then copy it to the development and product, so that they can understand the situation of modifying the product BUG.
4. Every day before the release, testers need to track the progress of developing and fixing bugs. If the development and fixing problems are relatively slow, they need to communicate and coordinate with developers in time to track the progress of development and problem-solving.
5. Version release standards, such as (all functions are implemented as required, the problems found in the test have been closed, there is no bug in the main process, the number of bugs above the severity level is 0, the number of low-level bugs <= 5, test cases have been executed).
6. The content involved in each release version (installation package files, SQL scripts, documents, etc.) needs to be placed on the corresponding SVN according to the version, and the package (test, pre-release, official) belonging to which environment is specified.
7. The front-end (android and IOS) release version needs to include the version number, the MD5 value of the package file, and the timestamp of the package file. The corresponding package file needs to be uploaded to SVN.
8. Before the version is released, it needs to go through the acceptance test. Generally, the product manager is required to intervene in the acceptance test. After the product is accepted, the test will be carried out according to the release standard to determine whether it can be launched.
9. Before the version is released, the version release operation will be started only after the release standard is met and the release email notification is passed through the test release. The development and testing need to assist the operation and maintenance in the release operation.
Article from: https://www.cnblogs.com/NiceTime/p/8555829.html
Enterprise certification can enjoy Testin exclusive gift package
Remote real machine/automatic test duration: 240 minutes
Standard Compatibility Test: You can test once a day, and you can choose from 100 models each time
Automated security testing: one free test per day
Google Android Oreo real device test
Google Android P Monkey 自动化兼容测试
价值千元的测试培训课全部免费观看
测试行业白皮书
测试培训精品文章
BUG 探索免费咨询服务
Testin 新功能抢先体验
客户成功服务
了解更多权益，欢迎登录：https://www.testin.cn/account/register.htm?channel=&utm_source=content&utm_campaign=article&utm_term=bottom-adv（点击或复制此网址到浏览器打开即可）
【你离事半功倍的 App 测试，只差一个 Testin 企业认证的距离】
推荐阅读：