How to join The Walking Dead: Road To Survival beta
We are getting a lot of interest from our visitors around this topic so I want to share a small FAQ here.
The Walking Dead Road to Survival is the definitive Walking Dead strategy RPG game, brought to you by Robert Kirkman, creator of The Walking Dead comic series.
Project details: WD: RTS on the TestingCatalog
This game uses a closed beta testing model and it uses closed Google Plus community to manage beta access. It also has a very high position in the TestingCatalog (currently TOP 3). This high position means that it has a lot of likes from our testers and it also has frequent updates with detailed changelogs.
However, it is not that easy to get an access to the beta app. Google+ community is closed, which means that you have to ask for the access first and wait until your request will be accepted by the google+ community moderator....
Android App Testing Sessions Summary for week 20 of 2017
A while ago I started adding small test reviews to the published daily beta apps. I also want to collect all of them in one place in case if someone missed them and also you don't have to click on the each app if you just want to read reviews.
Here is a list of the first seven apps:
- Apex Launcher beta
- Trello beta
- Transitions beta
- Dice Smash beta
- Rising Warriors beta
- BeyoundPod Podcast Manager beta
- Liquidsky beta
1. Apex Launcher beta
Very customisable launcher with many settings.
Bug 1: Google search widget doesn't work, it doesn't react on user taps (but it can be resized or deleted)
Bug 2: Pre customised Google folder contains S planner app from Samsung. Expected behaviour - Google folder should contain only google apps
How to Beta Test via Android App Developer Console?
Before you start, you should decide for yourself the following
What is the goal which you are trying to achieve with your beta test?
Android Developers Console for beta testing purpose
Beta Access Management
Depending on your goal, you can run an Open beta test or a Closed beta test
- Open beta test is the easiest way to go. It will make your app discoverable on the Google Play and everyone who has a link will be able to get a beta version.
- Closed beta test. There are always reasons why you may want to run a closed beta test. Your app can be a very popular and you don’t want to receive a lot of spam reviews. You may want to run a targeted research for a limited amount of users. It is possible to submit a list of emails and distribute the app only through pre-selected testers. Another way is to use Google+ community or a Google Group. Community or group can be closed or open and in the meantime, you will need to take some effort on moderation.
Beta App Distribution
You have a link to the Google Play and you can do your best on marketing to promote your app to the users.
Users can submit their feedback via Google Play as usual except a possibility to rate your app.
Early Access Promotion
You also can apply to the Google Play Early Access program via this form - Early Access Form if you want your app to be listed in the Early Access section....
How to join Telegram beta on Android
Update from 16.06.17
There is also another simplest way to get Telegram beta APK file, via the Hockeyapp
*Thanks to Jacob Ha for the link
I am happy to share this information here because we are getting a lot of search requests for Telegram in our TestingCatalog. Now you can search for it and get a result. However, it will lead you to the normal version which is published on the Google Play. For some reason, Telegram team decided not to go with the Google’s way of beta app distribution and they are sharing beta app files in the specific telegram channel. The same channel can be also used if you want to report any issues, so please keep it in mind.
- Download normal an app from the Google Play - https://www.testingcatalog.com/project/500
- Open an app > Search for “tgrambeta” or open this link - https://t.me/tgrambeta
TestingCatalog on Android updated, your rating is needed
As many of you know, we have a simple web app for android which can be found on Google Play
I updated it recently and latest changelog includes some bugfixes and new colour scheme.
Android app changelog:
WHAT'S NEW in v2.02
- fixed bug when tester avatars are not displayed correctly
- fixed a bug when links from footer are opening at the webview
- changed header colour according to the new colour scheme
Major changes on the website from latest release
- no adds
- search box
- my profile page
- help section
- testers rating
- testers tab in the project details
- app changelogs tab in the project details
- app changelogs now include "what's new" from Google Play
There still a lot of things to be done but most of them wouldn't touch android native part and you will get them as soon as they will be available on the website. Which is one the biggest benefit of having a web app 😃
Besides that, I also did some changes on the website - UPDATES tab...
Beta testers rating on TestingCatalog
Greetings beta testers and developers!
I decided to start publishing TestingCatalog changelogs and updates in the blog section also to make it accessible for all our beta testers.
Sometimes those posts will be small and sometimes big, but I will always try to have them focused around some topic.
So here we go, Changelog from 20.03.17:
- User rating (beta points) was introduced, check an explanation below
- Beta testers list ranking by rating
- A/B testing pages (feedback, surveys) removed
- Minor fixes
- Updates from Closed Google Plus communities, https://www.testingcatalog.com/update/
- User profile badges (beta points + joined at), see them here https://www.testingcatalog.com/project/410/testers
In order to display top beta testers higher in the list of testers, I added Beta points. The current logic behind those points is very simple and will evolve in future. Those badges will appear as soon as your rating will be changed next time.
To acquire Beta points you can do the following:
- Mark project as a favourite - 1 point
- Fill "about me” information in the user profile - 20
- Check, “I am beta tester” checkbox in the user profile - 3
- Check, “Newsletter subscription” checkbox in the user profile - 5
- Check, “Updates subscription” checkbox in the user profile - 5
- Check, “Events subscription” checkbox in the user profile - 5
You can find your user profile here https://www.testingcatalog.com/user/profile
As soon as “What’s new” updates will be ready, we a going to move forward towards one of those directions:
- Beta surveys
- Users feedback
- Testers courses
- Testing challenges
My current vision is forwarded towards option 4 and if you are an app developer and if you want to sponsor a testing challenge for your application - ping me here https://www.testingcatalog.com/contacts/
How to make a beta app to crash?
Android application stress testing with monkey tool
Before we start, if you want to know what is "stress testing" please check this article on Wikipedia. If you what to know what is "Monkey tool" please check this documentation - Monkey. Monkey tool is a part of android platform tools, to install them, please visit PlatformTools and ADB documentation.
In a case of any questions about installation or usage, feel free to leave a comment via Disqus. In this post, I would like to show how you can easily perform automated stress testing for any beta application on your device.
Monkey is a command line ADB tool with several options to adjust. You will need to know a package name of your android application.
The command itself looks like that
adb shell monkey -p com.sidekix.app -v --pct-syskeys 0 3000
com.sidekix.app is a package name of Sidekix: Walking Navigation
What is does.
- It will automatically execute a script command against the main activity of Sidekix application.
- The script will start executing different events on your device such as touches, swipes etc.
- The script will print all events to the log. In a case of any crash - you will see an error StackTrace in the logs.
It has many parameters to adjust and here I would like to focus on the most important things.
- p com.sidekix.app - This parameter allows you to specify an application package name.
- v - Verbose mode. It will let you see the detailed log of the script execution. —pct-syskeys 0 - Percentage of system keys events. By default all events sent to your device are random and a chance that monkey will start smashing your system keys is very big. Usually, you will want to minimise an amount of those events because it can turn volume to the maximum level and turn your music player on after.
- 3000 - This value in the end specifies and an amount of events to execute. Don’t put too many numbers here because it is tricky to stop this script and it will continue running even if you will unplug it.
In parallel with Monkey, I am using screenrecord tool to capture a video from the device screen.
adb shell screenrecord /sdcard/monkey_test.mp4
It can be very helpful because it may help you or developer to reproduce the problem. For better understanding, you can enable touches highlighting in the developer settings of your device. All monkey events are executed against the device which means that if you have this option enabled, you will be able to see all performed actions on the video.
How to crash apps
It is a part of the best practice for the developer to use a Monkey tool. However, it is hard to cover all corner cases. In the video below I turned internet connection off which sometimes may cause unexpected results.
Click to watch
No internet connection, location service turned off, horizontal rotation, etc. Many of those circumstances may cause an app to crash. That is the most helpful part of the Monkey tool - you can quickly play around those conditions by stress testing your app with Monkey.
What to do next
Always report an app crash to the developer. In most cases, it is enough for them to identify a problem and fix it.
If you think that they may need an additional information.
- capture a video
- save an error traceback or full monkey log
- capture a screenshot of a crash if you don’t have a video
- write down your pre-conditions (device name, android version, application version, etc..)
- try to reproduce found crash manually and describe steps to reproduce
By the way - here is an example of Monkey tool log with a StackTrace.
How to reproduce
Well, here is where the challenge comes in. Usually, it is tricky to figure out what your monkey did with the app to make it crash. That is why video record can be very helpful. Depending on the difficulty of reproducing you can give a priority to the found issue. As harder it to reproduce as lower the priority is. Why? Because it means that if you cannot reproduce it, other users will have the same chance for this crash to happen.
What this error means for end users
I wasn’t able to reproduce this particular crash and most probably not that many users will see this app crashing because of my case. But there is no guaranty that this issue wouldn’t rise after several updates as a massive critical issue because of some code change. Fixing those kinds of issues asap is always a good practice :)
I would also like to say that you should give Sidekix: Walking Navigation a try. It has a nice design and I got a good user experience during my tests. Don’t forget to report your feedback! Cheers!
How to join any android application beta testing program
Four simple steps are needed:
- Choose an application in TestingCatalog.
- Click JOIN COMMUNITY button if available and join Google Plus community with your Google Play account.
- Click OPT-IN button and press BECOME A TESTER button.
- Press "Download the app on Google Play" link at the bottom of the page.
Let's take a look closer at the each of them!
1. Choose an application on TestingCatalog.
All applications are listed on our Home page, feel free to pick whatever you like.
Crowdtesting for Android. Are there any problems?
A crowdtesting concept can fix a lot of problems as an addition to the traditional in-house testing process. Better device coverage, testing in the real environment, additional feedback from real users and so on.
In the same time, a crowdtesting concept has a lot of problems.
An amount of projects, available for testing is a lot lower than an amount of testers. It is a very common situation when tester waits for a month until he will be able to start testing. Usually, only a crowdtesting provider is responsible for sales and this model is not ideal.
- A client should be able to order a crowdtesting service easily, by submitting a link to his product and specifying additional information, such as scope or other limitations.
- A tester should be able to sell his work by himself, by submitting a project with his test reports. A crowdtesting platform should provide clients for testers, but it should not limit them. It is like a taxi service — as a driver, you don’t want to sit without any job for a month, just because your company don’t have enough clients, especially if there are a lot of clients around you.
Test reports and feedbacks are private for open projects. Private test reports can be a requirement for security issues or for some closed projects with NDA, but there a lot of open projects that can be tested transparently. Why is it so important?
- A private test report is a black box for clients. A client should be able to know what to expect from crowdtesting service.
- A tester should have an example to be able to grow his testing skills. Testers can grow a lot faster in the transparent environment.
- A quality of public test report is better because testers don’t want to loose their reputation.
Only paid projects are available for testing. There are a lot of testers, who are not interested in rewards. They just want to try something new.
- These testers should be able to share their feedback with client easily, in the same way as others.
What am I working on?
I am organising exploratory test events for android applications in google+ community and sharing gathered test data with the developers. All our test data is open and transparent.
Currently, TestingCatalog is in the Beta stage. This platform is a base part of a future crowdtesting powered service.