#gametest

[igb120bob]

IGB120 | Play on gd.games

[igb120bob]

Another playtast told me that the maps were too simple. Indeed, it seemed that no one in our group had systematically studied the map design of platform jumping games, so the maps were all generated by AI. Therefore, the maps were easy to pass without any challenge.

[igb120bob]

According to the playtests conducted by my acquaintances, they think that the feedback when receiving damage is too small. At the same time, after receiving damage, you will not receive the same type of damage again. For example, if you step on a floor of different colors, you will lose your health, but then you will be invincible and don't need to care about the different colors.

I think this phenomenon will seriously affect the gaming experience, so we will immediately try to fix it.

[igb120bob]

time | Play on gd.games

Play time on gd.games, a game created with GDevelop, the free and easy game-making app.

trying to improve the game art

[51testing]

Exploratory Testing in Game Testing

The game test is actually mainly manual testing. When it comes to manual testing, it will definitely talk about exploratory testing.

The Definition of Exploratory Testing

“ What is exploratory testing?

EXPLORATORY TESTING is a type of software testing where test cases are not created in advance but testers check the system when processing. The focus of exploratory testing is more on testing as a “thinking” activity. ”

The test methods mentioned in the book Exploratory Testing are very useful for game testing. And this is what we will share today.

Guide Test Method

It is to review the functions strictly in accordance with the plan. This is the most basic and most important method.

Selling Point Test Method

This method is to encourage testers to watch the demo from the point of view of sales and understand the biggest selling point of the game. The selling point is not necessarily the core function of the game, but it must be given the same attention as the core function. For example, the biggest selling point of the mobile game “League of Goddess” is naturally the goddess, but the goddess is not the core function of the game, but auxiliary gameplay, but players are keen on this, it is very necessary to test more.

Landmark Test Method

The method is that if we want to go to a place, we usually set the flags representing the steps on the map, but no one stipulates where we should follow the steps. Since there are quite a lot of related functions in the game, the landmark test method can be said to be a very commonly used method when we test. For example, if the player kills a monster, the player will get +1 experience point(EXP). Will the player gain EXP by just hitting the last monster? Will the player gain experience point when the monster is killed while also dying?

Limit Test Method

Test the limit of the functional program. For example, one hundred players attacked a monster at the same time and check the result.

Late Night Test Method

This method is mainly used for some functions such as data backup and has little connection with game testing.

Museum Test Method

This method is used for long-term projects. Some old functions have been running normally. After new functions are released, whether the old functions are still normal.

Deep Alley Test Method

This method is mainly used for observing some points where no one pays attention, such as the function of HELP.

Overnight Test Method

This method is used to checking whether the function is normal when it runs continuously for a long time.

Long Path Test Method

Check the result that requires the most operation steps, and every step to reach this result.

Supermodel Test Method

You may think this method not very useful at first glance, isn’t it just looking at the interface? I watch it every day. But in fact, it is different to look at the interface with the mentality of finding bugs. For example, I look at an enhanced interface every day, but until I plan to find bugs, I really discovered that the tabbed text on this interface is a few pixels crooked compared to the text on other tabs. This is what I haven’t noticed before. Interface in the game is a very important thing, so the use of supermodel testing is of great help to us.

Cancel Test Method

Close the operation interface, close the application, switch the line when the program is processing to check whether there is bugs.

Sluggard Test Method

Choose the most trouble-free step to achieve the result, and check whether the result is correct.

Obsessive-compulsive Disorder Test Method

Keep repeating the operation to check whether the function responds normally. I think the most likely thing in the game is to use a mouse simulator to continuously click.

We use different methods to test different games and it is necessary to keep summarizing which methods are often used in the games.

For test engineers looking for game testing jobs, it is necessary to accumulate different game testing methods. For exploratory testing in game testing, I think that the methods mentioned above are very helpful. In software testing, you can use brain maps to write test methods and use cases. The more you write, the more proficient you will be.

[himegoto-fan]

We had the opertunity to try a closed beta of the game Broken Lines wich is a top down turnbased strategy game where you are in the 1940s.

I think the game is fun and interesting since i dont play many stradegy games and i am happy that i get to try the beta.

I did not get that far into the game but even so i still think it was fun and i whant to play more

[gconnell-design-blog]

Taking Hardware Into Account

My Hardest Bug Ever

http://www.gamasutra.com/blogs/DaveBaggett/20131031/203788/My_Hardest_Bug_Ever.php

A blog on a blog. This story was recommended by a teacher while we were in our Q&A module. Not only was it a very interesting read but it also goes to show to think outside the box if what you’re looking for just isn’t working

When something is not working as intended we go to the code and decompile it as much as possible looking for the flaw and 99.9% of the time it works out that way. The worst bug you can have are game breaking or worse, break your memory card and wipe all data from it. To add onto this, this specific bug occurred at random with no significant patterns, which spells disaster for the programmer.

As part of our testing we had to list what CPU and graphics card was running the game which seems a little specific but after reading stories like this where hardware problems can be something that occurs, it does make it a reasonable thing to list and make you want to test on multiple pieces of hardware. Once you release the game and a bug that isn’t caused by your code surfaces, good luck.

Makes me a tad worried to learn programming because of these types of bugs which is something that we shouldn’t need to consider but unfortunately you need to take everything into account. Highly recommend to read the entire blog.

[testbytes]

Types Of Game Testing - Testbytes