GMS是什么认证？具体需要注意什么？

谷歌GMS认证（Google Mobile Services Test Certification ）是谷歌公司为了确保全世界的硬件厂商设计和生产的安卓为基础的各种智能硬件产品的兼容性、稳定性，以及这些硬件与安卓各种自带的各种软件APP产品和服务的兼容性、稳定性方面的测试和认证。凡是通过GMS认证的产品，将获得谷歌的徽标授权，同时产品的型号将列出在谷歌相关的网站中。
（1）GMS认证主要目的：
1，提升产品Android系统的兼容性和稳定性；
2，授权使用Google的 手机APP和服务；
3，授权使用Android LOGO；
4，产品可以进入欧美的大卖场。
（2）GMS认证的要求：
1，产品必须能通过CTS测试，CTS测试（英文名字Compatibility Test Suite，兼容性测试包），这是一组用以测试的apk程序之类的集合；
2，产品必须通通过CTS Verify测试；
3，产品必须能通过GTS测试，GTS测试（英文名字Google Mobile Services Test Suite ，GMS套件测试），用于GMS应用的测试的自动化的测试套件；
4，产品必须使用80以上的安卓版本才可以进行认证；
5，产品有义务通过CE，FCC，BT，WIFI等硬件认证。（非硬性指标）
（3）GMS认证流程：
1，申请谷歌MADA协议；
2，产品做软硬件测试；
3，提交测试报告给谷歌审核；
4，获得谷歌认证授权。
（4）申请GMS认证需要准备的材料：
1，附件两份申请表，请填写回传给我们。
2，准备8台样机，其中4台交谷歌存档，4台用于做测试。
（5）申请GMS认证周期：
在实验室做GMS认证的平均周期为6~8周。如因客户产品修改延误，周期需要顺延。
6）和实验室合作流程
1 双方签署合同。
2 贵司提供样机和申请表。
3 贵司安排付款。
4 实验室做CTS, CTS verify, GTS等测试。
5 中联检检测提交测试报告给谷歌审核。
6 通过谷歌GMS认证，获得谷歌相关服务授权

如果是谷歌安卓GMS认证的话请看下面流程：
（1）GMS认证主要目的：
提升产品Android系统的兼容性和稳定性；
授权使用Google的 手机APP和服务；
授权使用Android LOGO；
产品可以进入欧美的大卖场。
（2）GMS认证的要求：
产品必须能通过CTS测试；
产品必须通通过CTS Verify测试；
产品必须能通过GTS测试；
产品必须使用70以上的安卓版本才可以进行认证；
产品有义务通过CE，FCC，BT，WIFI等硬件认证。（非硬性指标）
（3）GMS认证流程：
1，申请谷歌MADA协议；
2，产品做软硬件测试；
3，提交测试报告给谷歌审核；
4，获得谷歌认证授权。
（4）申请GMS认证需要准备的材料：
1，附件两份申请表，请填写回传给我们。
2，准备6台样机，其中4台交谷歌存档，2台用于做测试。
（5）申请GMS认证周期：
在实验室做GMS认证的平均周期为4~8周。如因客户产品修改延误，周期需要顺延。
（6）和实验室合作流程
1 双方签署合同。
2 贵司提供样机和申请表。
3 贵司安排付款。
4 实验室做CTS, CTS verify, GTS等测试。
5 提交测试报告给谷歌审核。
6 通过谷歌GMS认证，获得谷歌相关服务授权
如果还有什么可以找我们。

本文整理来自pro Apache jmter web application和Wikipedia

在一定的负载条件下，评估系统或应用的响应时间，吞吐量等相关指标

功能测试通过之后

对系统进行性能评估，并通过测试发现系统瓶颈，分析定位瓶颈发生的原因，协助开发修复性能问题，提高系统的处理能力。对比不同的系统，确认更好的系统。

主要指标： 响应时间、吞吐量、资源利用率。

The time taken by the application to respond to the user’s request is called the response timeEvery application should strive to minimize the response time

应用程序响应用户请求所需的时间称之为--响应时间。响应时间越小越好

对于常见的B/S结构的响应时间，如下图：

从用户发起请求，到服务完全完成响应的时间。

用户感知时间，有点预加载的意思。即本来一个页面全部信息同时返回，现在改成优先加载一部分内容

服务器处理时间。服务器处理请求并响应的这段时间。与请求的复杂性、系统的硬件及系统服负载有关。

吞吐量：单位时间内处理的事务个数。通常由transactions/second 或 bandwidth (bytes/second)来衡量。吞吐量越大越好。

服务器资源利用率，不应该超过80%的利用率。利用率越低越好。

Scalability measures how well the system can expand its capacity when additional resources are addedIdeally the system capacity will increase linearly as additional resources are added However, this is rarely achieved in practice It’s a good measure to know the resources that would be needed so that the system can handle the projected future loadVertical scalability is achieved by upgrading the hardware For example, by adding more memory, disk,
a better CPU, or additional CPUsHorizontal scalability is achieved by adding servers to the cluster For example, by adding more web
servers and application servers to a webfarm/cluster

主要有压力测试，负载测试，配置测试等

压力测试是应用程序处于超出负荷状态下长时间运行，以测试服务器的稳定性和性能表现。

A load test is a kind of performance test that’s performed at the specified load level So ideally, we would like to perform load tests at varying load levels to note the behavior of the application

在一定的负载条件下，测试应用程序的性能表现。通过不同的负载程度（load levels）,观察应用程序的性能表现来得到最大的用户数，响应时间以及资源利用率等指标。

A peak load test is performed at the load that the application is expected to handle For example, e-commerce web sites experience their peak traffic during Black Friday, Cyber Monday, and the Christmas holidays So a peak load test in this case would test the application within the load specification but at the higher end

Note stress tests test beyond the peak load

In a soak test (also called an endurance test), the application is subjected to a specified load that is within the specified limit but for a long duration It is performed for many hours at a time This test determines if the application is properly reusing its resources
This test will surface problems like the following:

Successful web applications experience massive and sometimes exponential growth So it is wise to measure how the application scales Scalability is defined as how well the application handles the increase in load while still meeting the desired performance criteria

A scalability test would increase the resources and test whether or not the application is providing
a corresponding increase in capacity Ideally, we expect linear scalability (ie, doubling the hardware resources should result in double the application capacity)

A capacity test is a load test that establishes the maximum load that the application can handle while
meeting the desired performance criteria The resulting metric is called the maximum capacity It is used in scaling the application and to estimate costs for future growth

A spike test is a load test where the application is subjected to brief periods of sudden increment in load, a small fraction beyond the maximum capacity It is usually done to estimate the weakness/strength of an application The application is expected to be robust and continue to meet the performance criteria during the spike This metric is called the burst capacity

In a performance smoke test, a few common and essential use-cases along with use-cases pertaining to the
code subject to change are together tested for performance It is only when the smoke test succeeds that
the full suite of performance tests are conducted If the smoke test fails, no further performance tests areconducted until the performance defect has been rectified

Modern web application infrastructure is designed to be highly available and resilient to hardware and software failures Ideally, the architecture should ensure that there is no single point of failure and that there are standby servers that can transparently take over without impacting the user experience
In this test various equipment and software failures are simulated and relevant performance tests are
run to verify that the application is still meeting the performance criteria

Rather than testing for performance from a load perspective, tests are created to determine the effects of configuration changes to the system's components on the system's performance and behaviour A common example would be experimenting with different methods of load-balancing

---