测试一个移动应用程序_移动银行应用程序：正在测试和需要考虑的4个主要领域-CSDN博客

测试一个移动应用程序

By this time the large percentage of day-to-day transactions have shifted to mobile banking; here QAs must investigate some overriding areas while testing mobile banking apps. So, take a gander at 4 important areas of interest while testing mobile banking applications.

到这个时候，大部分日常交易已经转移到了移动银行。在测试移动银行应用程序时，质量检查人员必须调查一些重要领域。因此，在测试移动银行应用程序时，要先关注四个重要领域。

In a recent survey KPMG reports that by 2019, mobile banking users will double and hit a fourth of the total populace. Similarly, Gartner articulates that it envisages fifty percent of shoppers in the fully grown market to use smartphones for mobile payments by the end of year 2018. With the emergence of internet and arrival of mobile banking services in the market, a large fraction of daily transactions has moved away from bygone channels, for example, ATMs or bank branches.

毕马威会计师事务所（KPMG）最近的一项调查显示，到2019年，手机银行用户将翻一番，达到总人口的四分之一。同样， Gartner明确表示，它预计到2018年底，在完全成长的市场中，有50％的购物者将使用智能手机进行移动支付。随着互联网的出现和移动银行服务的出现，日常交易中很大一部分已从过去的渠道（例如ATM或银行分行）移开。

Banks today understand the need to concentrate on a cross-channel experiences creation for their clients keeping in mind the end goal to hold their consideration. While creating apps that are high on execution and usability is the key, expanding client interest for mobile apps brings a comparable demand for robust mobile testing too.

如今，银行已经意识到有必要为客户着重于跨渠道的体验创建，同时牢记最终目标以保持考虑。尽管创建具有高执行力和可用性的应用程序是关键，但扩大客户对移动应用程序的兴趣也带来了对健壮的移动测试的可比需求。

In the testing situations for banking apps QA teams are liable to concentrate on guaranteeing application security. App security is the major concern in retail banking applications that works on a public (open) platform, where the user is more vulnerable to cyber-thefts. In whatever way, other than assuring security with standard application testing techniques, there are four principal areas that veteran testers tend to neglect.

在对银行应用程序进行测试的情况下，质量检查团队有责任集中精力保证应用程序的安全性。应用程序安全是在公共（开放）平台上工作的零售银行应用程序中的主要问题，在该平台上，用户更容易受到网络盗窃的攻击。无论如何，除了使用标准应用程序测试技术确保安全性之外，资深测试人员还倾向于忽略四个主要方面。

Creating Domain Particular Test Information

创建领域特定的测试信息

Mobile banking app user’s bank account data, phone number, date of birth, and address is the confidential information that can be misused easily if visible in the public domain. Thus, in many nations there are regulatory requirements to safeguard personal information. However, this frequently prompts to inaccessibility of production-like records and presents a challenge for Quality analysts where they might not have admittance to the right sort of test information.

移动银行应用程序用户的银行帐户数据，电话号码，出生日期和地址是机密信息，如果在公共领域可见，则很容易滥用。因此，在许多国家/地区，都有保护个人信息的法规要求。但是，这经常会导致无法获得类似生产的记录，并给质量分析人员带来了挑战，因为他们可能无法接受正确的测试信息。

A decent case for creating the right test information can be found in retail banking applications that permit testing over various gadgets with different screen resolutions. For instance, a client may have a long name and $1,000,000,000 in his account, whereas another client may have a couple of thousand dollars as his account balance. In both cases, testing the application with production-like information is significant to guarantee that the screen design is in place with various information sets.

在零售银行应用程序中可以找到创建正确的测试信息的合适案例，该应用程序允许对具有不同屏幕分辨率的各种小工具进行测试。例如，一个客户可能有一个长名，帐户中有$ 1,000,000,000，而另一个客户可能有几千美元作为帐户余额。在这两种情况下，使用类似于生产的信息来测试应用程序都是非常重要的，以确保屏幕设计具有各种信息集。

Thus, by applying an approach that consolidates data masking as well as synthetic data creation one can effectively manage this matter. With the help of data masking the account related data are veiled via mechanized scripts. The veiled (masked) data are then embedded into a database reduced version for testing. Likewise, engineered – synthetic test data formed in a test environment subsequent to comprehending the business flow endways.

因此，通过应用一种合并数据屏蔽以及合成数据创建的方法，可以有效地解决这一问题。借助数据屏蔽，可通过机械化脚本隐藏与帐户相关的数据。遮掩的（掩盖的）数据然后被嵌入到数据库简化版本中以进行测试。同样，在全面理解业务流程之后，在测试环境中形成了工程化的综合测试数据。

Highlighting Contrasts Plainly in Test Arrangements

在测试安排中突出强调对比

Test arrangements ought to plainly diagram the functional, informational, or technical variances amongst creation and test situations so that the related dangers are moderated well ahead of time. In most banking apps, file transfer over various frameworks in production is automated through File Transfer Protocol; though in most test situations, this file transfer is performed manually.

测试安排应该清楚地说明创建和测试情况之间的功能，信息或技术差异，以便提前消除相关的危险。在大多数银行应用中，生产中各种框架上的文件传输都是通过文件传输协议自动进行的；尽管在大多数测试情况下，此文件传输都是手动执行的。

Suppose the monthly account statement of your bank account (financial balance) is transferred automatically in production to a DWH (data warehouse) keeping in mind the end goal to keep up the transaction history. Yet is being transferred manually in the testing environment (i.e., Quality analysts’ put the file in a designated directory and afterward the DWH expends it).

假设您的银行帐户的月度帐户对帐单（财务余额）在生产中自动转移到DWH（数据仓库），请牢记最终目标以保持交易历史记录。但是，它是在测试环境中手动传输的（即，质量分析人员将文件放在指定的目录中，然后DWH将其消耗掉）。

The automated transfer in production authorizes testing of situations, for example, delay in transfer, transfer of the same file more than once, another record (file) abrogating the current record, and so on. In mobile apps, a deferral in transfer may prompt to critical customer disappointment as smartphone users expect a fast response from the applications. Such situations should be considered and the risks ought to be taken care of or highlighted obviously in test arranges.

生产中的自动传输授权对情况进行测试，例如，传输延迟，相同文件的传输不止一次，另一个记录（文件）废除当前记录等。在移动应用程序中，由于智能手机用户期望从应用程序中获得快速响应，因此推迟传输可能会导致严重的客户失望。应考虑这种情况，并应在测试安排中注意或突出指出风险。

Managing the High Volumes

管理大量

Another testing challenge if there should arise an occurrence of retail banking applications is dealing with the high volume of information that banks keep up. A small operation can produce generous information volume. For example, online client’s easy operation may result in picking up the log in date, time, user location and the entire sequence of steps that he might have performed. Banks may need to keep up adequate assets to store such details that can assist them avert and solve digital violations. Indeed, information capturing is regularly a prerequisite and is a regulatory (administrative) compliance essential. Nevertheless, mobile devices can have limited hardware resources, like RAM, processor speed, and so forth. It is important that gadget execution is tried with high volume of information to guarantee that while utilizing the application the end client's experience is wonderful. The end-user won't wish to use a compromised performance application regardless of the possibility that the hidden usefulness works as anticipated.

如果应该出现零售银行应用程序，则另一个测试挑战是处理银行保留的大量信息。较小的操作会产生大量的信息量。例如，在线客户的简单操作可能会导致获取他可能执行的登录日期，时间，用户位置以及整个步骤序列。银行可能需要保留足够的资产来存储此类详细信息，以帮助他们避免和解决数字违规问题。实际上，信息捕获通常是先决条件，并且是法规（行政）合规性必不可少的。但是，移动设备可能具有有限的硬件资源，例如RAM，处理器速度等。重要的是，尝试使用大量信息尝试执行小工具，以确保在使用应用程序时，最终客户的体验非常出色。最终用户不希望使用性能受损的应用程序，无论隐藏的有用功能是否按预期工作。

For this situation, the test approach must uphold the production of unmistakable information sets for each interface, therefore resolving key ranges of effect for a specific feature across interfaces. Isolated test data sets should likewise be made for every environment because the accessible back-end DB for one environment may induce a different cut-down variant of information from production. While we do as such,the gadget execution should be measured with tools like, Little Eye or Xcode.

对于这种情况，测试方法必须支持为每个接口生成无误的信息集，从而解决跨接口特定功能的关键作用范围。同样应针对每种环境创建隔离的测试数据集，因为针对一种环境的可访问后端DB可能会导致生产信息的缩减形式有所不同。虽然我们这样做，但是应该使用Little Eye或Xcode之类的工具来评估小工具的执行情况。

Comprehending Usage Patterns

理解使用模式

High discontinuity of gadgets and stages is another challenge that a Quality Analysts ordinarily confronts. Endeavoring to test all combinations are frequently an exorbitant and a purposeless practice on a mobile as new combinations are presented consistently in the market. Testing on various platforms like iOS, Android, and Windows, covering different working framework variants like iOS 5.x, 6.x, 7.x, Android 4.4, 5.0 and a scope of gadgets from producers like Nokia, Samsung, HTC or Apple are for all intents and purposes unimaginable.

小工具和阶段的高度不连续性是质量分析师通常面临的另一个挑战。努力测试所有组合通常在移动设备上是过高且毫无目的的做法，因为新组合不断在市场上出现。在iOS，Android和Windows等各种平台上进行测试，涵盖iOS 5.x，6.x，7.x，Android 4.4、5.0等不同的工作框架变体以及诺基亚，三星，HTC或苹果公司的所有意图和目的都是无法想象的。

Rather than going up against a fantastic errand of testing in a divided way, embrace a subjective approach. Select just those platforms or gadgets that have the most astounding penetration in a given topography. For example, in the US and Canada, the attention might be on top-of-the-line iOS/Android smartphones while for Brazil and other Latin American nations, the application might be tried on low-end Android phones. For ideal testing, increase comparative insights by mining information from Google Analytics, Dynatrace and so on.

与其采取分立的方式进行奇妙的测试，不如采用主观的方法。仅选择在给定地形中具有最惊人渗透率的平台或小工具。例如，在美国和加拿大，注意力可能集中在顶级的iOS / Android智能手机上，而在巴西和其他拉丁美洲国家，则可以在低端Android手机上尝试该应用程序。对于理想的测试，请通过挖掘Google Analytics（分析），Dynatrace等的信息来增加比较的见解。

Get contributions from your marketing research teams and know how your clients are dealing with the application. For example, 70%-80% of the clients frequently just get to the retail banking application to check their balance and make some transactions, for example, money transfer or bill payment. Comprehend the client's attitude and the application usage patterns, and organize testing endeavors likewise.

从您的市场研究团队获得帮助，并了解您的客户如何处理该应用程序。例如，70％-80％的客户经常只是进入零售银行应用程序以检查其余额并进行一些交易，例如汇款或账单支付。理解客户的态度和应用程序使用模式，并同样组织测试活动。

At last, application testing teams should be outfitted with the detailed knowledge and follow a strategically innovative and technical bearing. In this manner, when chipping away at specific domains like mobile banking applications, enduring the extra mile, past the standard testing practices is a key part of an analyzer's learning and development.

最后，应用程序测试团队应配备详细的知识，并遵循具有战略意义的创新和技术指导。通过这种方式，当在诸如移动银行应用程序之类的特定领域投入使用时，要忍受额外的艰辛，过去的标准测试实践是分析仪学习和开发的关键部分。