Test Case of Android Translator Application

Activities Testing

Activities Testing involves producing a layout that describes user interface interaction or
behaviour with layouts. It involves reviewing the test basis, identifying the test conditions based
on analysis of test items. Activities serve as containers for every user interaction within our app,
so it's important to test how your app's activities behave during device-level events, such as the
following:

 Another app, such as the device's phone app, interrupts your app's activity.

 The system destroys and recreates your activity.

 The user places your activity in a new windowing environment, such as picture-in-picture (PIP)
or multi-window.

Run Time Test

Runtime testing is performed when an android application is running (or being executable). That
is, when we start application running in a android os. During execution of android application we
test it through “Logcat” which runs with android studio. If any error occours in android activities
then Logcat stops the application while it running on mobile phone.

Voice Testing / Input Testing

In GUI testing we test object in activities. GUI testing is defined as the process of testing the
system's Graphical User Interface of the android application under test. GUI testing involves
checking the screens with the controls like menus, buttons, icons, and all types of bars - toolbar,
menu bar, dialog boxes etc.

As per requirement our application works with voice cammands. So we test the microphone of
mobile.
Process Testing
In android os activities has different process that are running in background of android os.

When an application component starts and the application does not have any other components
running, the Android system starts a new Linux process for the application with a single thread
of execution. By default, all components of the same application run in the same process and
thread (called the "main" thread). If an application component starts and there already exists a
process for that application (because another component from the application exists), then the
component is started within that process and uses the same thread of execution.