Jump to content

Instructions for beta testing

Recommended Posts

Instructions for beta testing mobile solutions KL


Beta testing – intensive use of the nearly finished version of the product, to identify the maximum number of errors for later correction before final release. Release of product to market to the mass consumer.

Unlike alpha testing ,conducted by the staff developers or testers, beta testing involves the recruitment of volunteers from among the ordinary future users of the product, which is sent to the current preliminary version of a product (so-called beta). These volunteers (called beta testers) are usually driven by curiosity to a new product – curiosity, for the satisfaction of which they are quite willing to put up with the opportunity to experience the consequences of yet undiscovered (and therefore uncorrected) errors. In addition, beta testing can be used as part of the strategy of product promotion on the market (for example, free distribution of beta allows you to attract wide attention of consumers to expensive final version of the product), as well as to obtain preliminary feedback on it from a wide range of future users.


Attention! "Kaspersky lab" doesn't help responsibility for the work of beta-version of the software! In all your actions, you are responsible only. Therefore, if you are not confident in your abilities and expertise, then you better not take part in the beta testing.


We have provided you with background information that will help you in beta testing.



Section 1.

Section 2.

Section 3.

Section 4.

Section 5.

Section 6.

Share this post

Link to post

Section 1. Used Abbreviations


KISA - Kaspersky Internet Security for Android.

LK - Kaspersky Lab.

KL - Kaspersky Lab.

GBT - Gold Beta Tester - Gold-beta-tester - Rank is given to the most active beta-testers after the end of product development.

FAQ - Frequently Asked Question(s) - Frequently asked questions.


Prototype - the Prototype of a new product.

Alpha - the Initial stage of product development, new functionality is being developed.

Beta - Development functionality was completed, begins the testing of components.

RC - The release candidate is Release Candidate; Build, which later may become a release.

TR - Technical Release - Completely ready on the technical side, the Assembly of the product; then begins the preparation of assemblies for sale (print boxes, creation of knowledge Bases, the development of materials for a product on the website, etc.)

CR - Commercial Release - Beginning of sale of the product; from this point on is official technical support.

MR - Maintenance Release - an Update that contains fixes for bugs found, as well as new functionality is added.


GUI - Graphical User Interface


Change log - a List of changes.

IMHO - In my humble opinion (one of the most used options of the transfer).

Log – Log the event log.

Bug - Error, defect


Share this post

Link to post

Section 2. Start testing: download, installation and activation of beta.


Attention! Before the start of the beta recommend you make a backup of all your personal data (contacts, photos, music etc.) stored on your mobile device, in the event of problems associated with testing, you could easily restore all your data.


In the process of installing the beta version in some products (e.g. KISA) will need to activate the software. Participants of beta testing with a beta version of antivirus are distributed to another non-profit and special activation codes, usually for a period of one month (or until the end of beta testing). From that moment you become a tester of the product.


After the release of a newer beta version, you will need to update your product. Remove from the mobile device the old beta version and then download the new version from the forum or Google Play.

You can then proceed to its installation and testing.


Attention! It is highly recommended not to install the new build over the old one. Do not migrate settings from the old Assembly with a new one (if you're asked to the developers) because it can lead to some problems. Therefore, before installing a new beta build, first completely remove the old one.

Edited by Virus_900

Share this post

Link to post

Section 3. Search bugs.


To find bugs in the program, you need to be clear that this is a bug.

Bug – a slang word that refers to a bug in the program. The term is usually used in relation to the errors that reveal themselves on the stage of the work programme, in contrast to, for example, from design errors or syntax errors. "Bugs" are localized and eliminated in the process of testing and debugging the program. To an issue can occur anytime, anywhere. It can be as permanent incorrect operation of the program, and temporary, which is manifested only under certain conditions (for example, simultaneous operation of another program). Under the definition of a bug is flagged as the negative impact of the tested program to run other programs and the operating system (hereinafter OS).


The task of a beta tester is to highlight a bug, possibly trying to make sure he caused the test program to determine the conditions under which this bug makes itself felt, and the most elaborate in the appropriate forum thread beta product. It is very important to try to understand under what conditions the bug persists (or in professional language – playing), and talk about it on the forum. Perhaps the developers of the product will ask You to provide additional information about You found a bug, and in some cases can send a debug version, so try to observe the messages on the forum.

Besides those mentioned above, bugs are also grammatical errors in the program, the flaws in the graphical user interface (GUI), the problems of excessive power consumption during operation of the program, etc.


Attention! Do not confirm or disprove the issues found in other beta testers, if you are explicitly requested to do so. Remember that each of the participants test unique hardware and software configuration of the mobile phone, so one error can be, and the other does not.


In the process of beta testing of great interest is the compatibility of mobile products with Your device, as well as check product compatibility with other programs, because in the process of alpha testing it is impossible to cover all the multitude of devices and doubly hard to cover all the many programs that may not be compatible for one reason or another. It is therefore necessary to check the compatibility of the product being tested with typical for You kit installed (running) applications. In this case, possibly, it is necessary to inform the developers about the set of programs (better versions) to make it easier to localize and solve the problem.


In identifying deviations in performance after installing the product (e.g., life time battery, the use of the standard phone functions, etc.) to be shared in detail about this in the appropriate forum thread.


The developers of "Kaspersky Lab" may ask you:

- Screenshot - screenshot. Screenshots should be attached to your message on the forum.

- To reproduce the bug if other beta testers encounter bugs, the developers can ask everyone to reproduce it, to make sure that the error is repeated consistently.

- Play at debugnow the Assembly - if the developers can't reproduce the specified bug, they can send You debugnow Assembly. And you will need to install it, to try to reproduce the bug and send them the logs.


Attention! Don't ask after the release of a new build, why not fix that particular error. Everywhere has its own priorities. For fixing some bugs takes time.

Share this post

Link to post

Section 4. Publication of the bugs on the forum.


As soon as the next beta, the forum creates a topic in the branch of the product with sub-topics for the modules of the product.


Found a bug tester is published in the relevant subject (for example, a bug that prevented a virus database update is published to the topic KISA > "Update", etc.).

Each topic is assigned a Topic-Lead (Topic Lead), i.e. a responsible person who will take the complaint and entered into a special document, which will be transferred to the staff of LK for further Troubleshooting. The list of collected problems will be found in the section "List of errors" that is created on each release undergoing beta-testing.


Attention! Before writing about the new error is highly recommended to look at the list of already thereporting bugs, maybe your problem is there was already announced.


Attention! In the topics above please write only in the case, not flood, Express their thoughts clearly. Information in topics that don't relate to beta testing, will be removed. And violators will be penalized up to block access to the forum. Don't make us go to extremes.

Share this post

Link to post

Section 5. Useful tips for Android users.


1. If the application has fallen, in the memory card or internal memory (in shared /mnt/sdcard/, but what there is mounted – this depends on the manufacturer of the device) will be the file stack.trace, which you can pick up any file Manager or even from Windows and provide the description of the situation that caused the fall.


2. If the file has not been created or the bug is not associated with the fall, we need to log what the logcat


The first thing you need to enable USB debugging.

In Android 4.0 and above need to go to Settings - developer. In Android 4.2 and above, you must first display your Developers options: http://juick.com/Umnik/2132459 In Android 2.x - 3.x configure – Program – Development

After you finish testing KISA mode should be disabled for security purposes.


Here are different versions of the collection of the log, one will find convenient:

1. Collection directly from the device itself

a. Put aLogcat

b. Run the utility and switch to KISA

c. Reproduce the problem

d. Switch on the tool and wait a couple seconds and save the log


2. Plugin Total Commander

a. Put the plugin http://wincmd.ru/plugring/android_adb.html

b. The connected device

c. Reproduce the problem

d. Taking the log of TC -> Network -> ADB -> Device -> .logcat -> filename.txt


3. SDK. Option 1, not interactive

a. Download and install JDK http://www.oracle.com/technetwork/java/index-jsp-138363.html

b. Download and install the SDK http://developer.android.com/sdk/index.html

c. Connect the device to your computer

d. Reproduce bug

e. Save the log http://developer.android.com/tools/help/logcat.html (adb logcat-f d:\logcat.txt). The operation is executed for 5 seconds.


4. SDK. Option 2, ghewy

a. All the steps from the previous paragraph, except the last two

b. Run %android-sdk%\tools\monitor.bat

c. To select the desired device

d. To reproduce the problem

e. In the lower quarter select all by Ctrl+A and save by clicking the floppy disk (verbose level)

In this embodiment 4 can and clear the log to reproduce the problem, so not too much got.

Share this post

Link to post

Section 6. Useful tips for users of iOS.


When diagnosing problems on iOS has value providing crash logs.

Crash logs can be collected in three ways:


1) the Logs can be obtained from the AppStore, for this user should be enabled to send diagnostic information to Apple.

To enable it in system settings->Settings - > Privacy->Diagnostics & Usage->Automatically Send


2) the Logs can be delivered to the device, to do this, go to Settings->Privacy->Diagnostics & Usage->Diagnostic & Usage Data-> select the required log, it will likely be very first. contents can be copied or send an email


3) the Logs can be collected via the desktop iTunes, you need to connect your device to computer and sync through iTunes

the logs will be copied to the following directory:

Mac OS X: ~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>

Windows XP: C:\Documents and Settings\<USERNAME>\Application Data\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>

Windows Vista or 7: C:\Users\<USERNAME>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>

Share this post

Link to post
This topic is now closed to further replies.

  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.