Mobile Testing Challenge by Daniel Knott 📖

Hi ShiftSync Community,

I am really looking forward to your comments 🤩. In case you have any kind of questions, please let me know!

Enjoy and have fun!

Love the initiative! I am quite new to the mobile testing besides security testing so this is a great opportunity to try something new!

Hey Daniel and ShiftSync Community!

Thank you for sharing this amazing sheet! It's really helpful!

The app #1 I chose is Starbucks from Brazil's APP Store

Here's the bug report summary from app #1

- When the user taps many times the continue button during the registration flow  (gestures testing strategy)   the apps got frozen and the user is not able to continue the registration process unless send the app to background > put to active again OR kill the app and restart the whole process.

The app #2 is Whatsapp. The pre condition info is that the mobile has to be more than 80% of local storage used.

- In this scenario, users are not allowed to go through favorite stickers/images without crashing the app.


Thanks for stimulate this challenge!

Best, 
​​​​​​​Eduarda

I have tested an unnamed mobile game in which the main goal is to improve your hero. Each day a player is limited by the amount of energy that is consumed after each activity. There is also an ingame shop where a player can buy premium currency in exchange for real money. A daily login bonus is available as well.

Date and time

At 01:00 AM each player receives a daily login bonus. This is usually checked by a server-side event. If you however turn on the “aeroplane mode” and change the system time, it will allow you to pick up a daily reward whenever you want. Changing the default timezone allows for picking up a reward once an hour instead of once a day + having an unlimited amount of energy since we can restart it whenever we want. After  If we change to US time format, the application crashes.

Language

If we select chinese as the language on our phone and open the game, we are then forwarded to the chinese payment gateway instead of the geologically closest one. In case we install the not supported language, the application crashes.

Hello @danielknott  and Shiftsync community!

I'd like to extend my gratitude to Daneil Knot and the entire Shiftsync community for the opportunity to participate in the challenge. During this challenge, I thoroughly tested the Testing Daily application, following a comprehensive cheatsheet. My focus was primarily on two crucial aspects: Usability and Multitasking.

Here is the Link

Introduction:

I've tested the Nanograms Katana app on two mobile phones. I've chosen to test it against two phones because there is a significant difference in the state of the screen. One of the phones has a somewhat cracked screen, while the other has a complete screen with a protective screen on top.

Phone specifications:

Phone 1:

Device name: Huawei Mate 20 lite

EMUI version: 12.0.0

Kernel Version: 4.14.116

Description: The phone that I use during the day. I've had this phone for 4+ years (if I remember correctly) and  I've used and abused it to the max. The phone needs a factory reset, but I don't want to do it because it's too much pain in the … + it's the screen is cracked and it's due to replacement anyway.

Picture:

Phone 2:

Device name: Galaxy A32 5G

Android version: 13.0.0

Kernel Version: 4.14.186

Description: This is my work phone. It's pretty new, and I have minimal non-work-related apps installed. I use it mainly for calls and quick Internet searches. One of the major apps I'm using on it is Spotify as its battery lasts much longer than the one on the Phone 1. It has a protective screen over its 'native' screen for extra protection

Picture:  Couldn't take it as the camera on Phone 1 is not working properly – the camera lens is pretty scratched so it takes foggy pictures. 

App:

I've chosen the Nanograms Katana app as it needs a lot of 'touch' gestures to play it. It's the app in which you fill in the empty grid based on the numbers on the sides. It has lots of touch, drag, and pinch functions so it seemed like a perfect candidate for the test. Here's an example of the game screen:

Testing - gestures:

Conclusion: The app works perfectly on both phones. I expected to see some issues when using it on the Phone 1 as it has a cracked screen, but it wasn't the case.

Testing - multitask:

Conclusion: The Phone 1 has some issues when using multiple apps at the same time. This could be due to the bad state of the phone at the start. Phone 2 is superior in every aspect, but the test should be repeated after some time to check if the current performance persists

🌟Time flies when you’re having fun! We came to the end of our Mobile Challenge.

But the fun doesn’t stop here! We’ll be announcing the winner of the challenge today, so stay tuned for that 🏅

And in the meantime, we want to thank everyone for their submissions and for being a part of this challenge!