The difference between games and apps in mobile testing

With the popularity of smart devices and the rise of mobile internet, internet giants are moving to the mobile end of the layout and transformation, while the start-up mobile internet companies are also staring at the market hope share. In this environment, the focus of the Internet has slowly shifted from the web to the mobile side, and mobile software testing has become more and more important. Talk today about the two most important directions in mobile testing.

App Automation testing is completely different from hand-guided automated testing

The development of mobile apps and hand tours is different, which leads to the difference between the automated testing techniques. For Android development examples, mobile apps are generally developed using the Android SDK and written in Java. Through the services provided by Android, we can obtain the view information of the app's current window, and then find and manipulate controls such as buttons to complete automated testing, such as Uiautomator. The process is standardized and technically no more difficult, so the methods of automated testing for each company's app are similar.

But the development of the hand tour is not so. Hand tours are generally used in engine development and are now famous for cocos2d and Unity3d. Both are developed using the engine's own language, and the main mainstream is C + + and C #, although there are also concepts of buttons and other controls in the development process. The automation of hand-travel testing is difficult to implement, and now Testbird is a specialized testing company that can drill into the game engine for automated testing.

And then, specifically, the difference.

Different gameplay results in more complex functional testing

Randomness. The scene and process of the game is dynamic and is accompanied by random elements, which is reflected in two points.

1, you repeatedly play a game level, it is likely two times the enemy and the game process is different.

2, you play a hand swim when not to operate, the enemy and the surrounding scene also changes in time.

These two points pose a huge challenge to automated testing, and if the test script is not flexible enough, it can easily cause the last script to run successfully. We need to properly include exploratory and adaptive functionality in our test scripts.

There is no problem with app testing, and most apps are static and repeatable. So automated testing can be written and executed exactly as a test script.

Exploratory. The second play of the Hand tour and app is different from exploratory. Apps are generally functional, and good apps need to tell users about their functions in a straightforward way. And the game is entertainment, need to give players a certain exploration elements. Therefore, when doing the hand-travel test, we need to test the game's user help to clarify whether it is clear, and the follow-up play and exploration process and the previous given the explanation of whether there is a reasonable connection between the instructions of the rule is sufficient prompt.

Difficulty Test. The simpler the app wants to do, the lower the user's cost of using the better. and hand-travel is difficult to set. When we do the hand-tour function test, we will adjust the resources and level to the maximum to facilitate the execution of post-function, but when all the functional tests are done, we need to initialize their resources to "return" to an ordinary player's level, through the view of ordinary players to see whether the game is more difficult to improve is reasonable, Whether the resource allocation is uniform.

Level test. The use of the app is functional, and the reuse of a function is always the same. The concept of a hand tour with a level, even if the same play, levels and levels there are subtle differences between the front level test is correct, does not mean that the following levels must be correct. The author has encountered a bug in the hand tour, when the game to a later level, the game will certainly crash. The cause of this bug is also simple: this level of picture resources in the packaging of the client is not joined. So when we play the front level, it doesn't trigger the bug, but the one to the back of the level goes wrong.

This type of bug is simple, but it's really hard to test. Because each level of play is consistent, but a game of the number of levels is very much. If we go through all the levels, the cost of manpower will be very large. For this kind of repetitive level testing, it is recommended to use an automated script for traversal.

PvP test. The use of the app is generally single, while the hand-tour often has a player PvP pvp mode, good Hand tour is a real-time PvP mode. The test of network latency becomes critical because two of players play games in real-time or in PvP. In testing, we need to simulate the impact of different networks on game latency, observe the two players ' status and data consistency, and experience the impact of network latency on the game feel, which is completely unnecessary in traditional app testing.

Testbird

The difference between games and apps in mobile testing