In the previous article, we learned 4 cases for how to  test  Android Applications.

In this article, we will learn more cases for how to  test  Android Applications.

5. Compatibility testing test cases

1. Have you tested on the best test devices and operating systems for mobile apps?
2. How does the app work with different parameters such as bandwidth, operating speed, capacity, etc.?
3. Will the app work properly with different mobile browsers such as Chrome, Safari, Firefox, Microsoft Edge, etc.
4. Does the app's user interface remain consistent, visible and accessible across different screen sizes?
5. Is the text readable for all users?
6. Does the app work seamlessly in different configurations? 

6. Security testing test cases

1. Can the mobile app resist any brute force attack to guess a person's username, password, or credit card number?
2. Does the app allow an attacker to access sensitive content or functionality without proper authentication?
3. This includes making sure communications with the backend are properly secured.  Is there an effective password protection system within the mobile app?
4. Verify dynamic dependencies.
5. Measures taken to prevent attackers from accessing these vulnerabilities.
6. What steps have been taken to prevent SQL injection-related attacks?
7. Identify and repair any unmanaged code scenarios
8. Make sure certificates are validated and whether the app implements certificate pinning
9. Protect your application and network from denial of service attacks
10. Analyze data storage and validation requirements
11. Create  session management to prevent unauthorized users from accessing unsolicited information
12. Check if the encryption code is damaged and repair what was found.
13. Are the business logic implementations secure and not vulnerable to any external attack?
14. Analyze file system interactions, determine any vulnerabilities and correct these problems.
15. What protocols are in place should hackers attempt to reconfigure the default landing page?
16. Protect from client-side harmful injections.
17. Protect yourself from but vicious runtime injections.
18. Investigate and prevent any malicious possibilities from file caching.
19. Protect from insecure data storage in app keyboard cache.
20. Investigate and prevent malicious actions by cookies.
21. To provide regular checks for the  data protection analysis
22. Investigate and prevent malicious actions from custom-made files
23. Preventing memory corruption cases
24. Analyze and prevent vulnerabilities from different data streams 

7. Localization testing test cases

1. The translated content must be checked for accuracy.  This should also include all verification or error messages that may appear. 
2. The language should be formatted correctly.(e.g. Arabic format from right to left, Japanese writing style of Last Name, First Name, etc.) 
3. The terminology is consistent across the user interface. 
4. The time and date are correctly formatted. 
5. The currency is the local equivalent. 
6. The colors are appropriate and convey the right message. 
7. Ensure the license and rules that comply with the laws and regulations of the destination region.
8. The layout of the text content is error free. 
9. Hyperlinks and hotkey functions work as expected. 
10. Entry fields support special characters and are validated as necessary (ie. postal codes)
11. Ensure that the localized UI has the same type of elements and numbers as the source product. 

8. Recoverability testing test cases

1. Will the app continue on the last operation in the event of a hard restart or system crash?
2. What, if any, causes crash recovery and transaction interruptions?
3. How effective is it at restoring the application after an unexpected interruption or crash?
4. How does the application handle a transaction during a power outage?
5. What is the expected process when the app needs to recover data directly affected by a failed connection? 

9. Regression testing test cases

1. Check the changes to existing features
2. Check the new changes implemented
3. Check the new features added 
4. Check for potential side effects after changes start 

That's it. If you want a good application, take these tips and follow cases for Android Application test. It will help to make quality & standardize your Applications.

7. Know your sales Channel

8. Find a new Customer

9. Remove unprofitable service and product

10. Reduce labor costs with part-time workers

11. Develop a CEO monthly letter to employees to create teamwork and communication

12. Invest in your people

13. Send personal notes of congratulations or thank employees at their home

use IlluminateDatabaseEloquentModel;
use SpatieMediaLibraryModelsMedia;
use SpatieMediaLibraryHasMediaHasMedia;
use SpatieMediaLibraryHasMediaHasMediaTrait;

class User extends Model implements HasMedia
{
    use HasMediaTrait;

    public function registerMediaConversions(Media $media = null)
    {
        $this->addMediaConversion('profile-thumb')
              ->width(150)
              ->height(150);
    }
}

$media = User::first()->addMedia($pathToImage)->toMediaCollection();

How to fetch the generated thumbnail? 

$media->getPath();  // the path to the where the original image is stored
$media->getPath('profile-thumb') // the path to the converted image with dimensions 150*150

$media->getUrl();  // the url to the where the original image is stored
$media->getUrl('profile-thumb') // the url to the converted image with dimensions 150*150

How to generate multiple thumbnails for a single image? 

..... in User Model .....
use SpatieImageManipulations;


    public function registerMediaConversions(Media $media = null)
    {
        $this->addMediaConversion('profile-thumb')
              ->width(150)
              ->height(150);
    }

        $this->addMediaConversion('old-profile-thumb')
              ->sepia()
              ->border(8, 'black', Manipulations::BORDER_OVERLAY);
    }

We have recently developed a site into the gatsby. We want to add Google Analytics to the website.

So, this is the way we implemented Google Analytics in the Gatsby site.

Use Gatsby Google GTag Plugin

Gatsby has a plugin gatsby-plugin-google-gtag that be used to easily add Google Global Site Tag to your Gatsby site.

Install the package by running the following command:

npm i gatsby-plugin-google-gtag --save

Configuration

Once the installation is complete, you can now add this plugin to your gatsby-config.js:

Configure trackingIds and other options. Add this into the plugins array. Like,

module.exports = {
  // ...
  plugins: [
    {
      resolve: `gatsby-plugin-google-gtag`,
      options: {
              // You can add multiple tracking ids and a pageview event will be fired for all of them.
              trackingIds: [
                "GA-TRACKING_ID", // Google Analytics / GA
                "AW-CONVERSION_ID", // Google Ads / Adwords / AW
                "DC-FLOODIGHT_ID", // Marketing Platform advertising products (Display & Video 360, Search Ads 360, and Campaign Manager)
              ],
              // This object gets passed directly to the gtag config command
              // This config will be shared across all trackingIds
              gtagConfig: {
                optimize_id: "OPT_CONTAINER_ID",
                anonymize_ip: true,
                cookie_expires: 0,
              },
              // This object is used for configuration specific to this plugin
              pluginConfig: {
                // Puts tracking script in the head instead of the body
                head: false,
                // Setting this parameter is also optional
                respectDNT: true,
                // Avoids sending pageview hits from custom paths
                exclude: ["/preview/**", "/do-not-track/me/too/"],
              },
      },
    },
  ],
}

This plugin automatically sends a “pageview” event to all products given as “trackingIds” on every Gatsby's route change.

If you want to call a custom event you have access to window.gtag where you can call an event for all products.

Check out this code.

typeof window !== "undefined" && window.gtag("event", "click", { ...data })

NOTE: This plugin only works in production mode! To test your Global Site Tag is installed and 

You need to run the following command for firing events correctly.

gatsby build && gatsby serve

If you need to exclude any path from the tracking system, you can add one or more to this optional array.

Development:

What is a Balanced Scorecard (BSC)?

• A Balanced Scorecard is a performance metric used to identify, improve, and control a business's various internal processes and resulting outcomes.
• Balance Scorecard is a framework to implement and manage strategies.
• The Balance scorecard is derived from the idea of looking at strategic measures to get a more balanced view of performance. The concept of a Balanced Scorecard evolved beyond the simple use of perspectives, every business can implement it according to the requirements and therefore it is a holistic system for managing strategy.

Why do we need to implement it?

• The key benefit of using a BSC framework is that it gives way to the organization  to "Connect the Dots" between various components of strategic planning and management and it means there will be a visible connection between Projects and Programs that people are working on it.
• BSC framework also helps management to meet pre-decided targets.

Perspectives of Balanced Scorecard:

The framework Balanced Scorecard divided into four areas (perspectives) that are critical to business success as given below.

1. Financial 
2. Internal process 
3. Learning and Growth 
4. Customer 

1. Functional testing test cases

1. Does the application work as intended when starting and stopping?  
2. Does the app work accordingly on different mobile and operating system versions?
3. Does the app behave accordingly in the event of external interruptions?
4. (i.e. receiving SMS, minimized during an incoming phone call, etc.)
5. Can the user download and install the app with no problem?
6. Can the device multitask as expected when the app is in use or running in the background?
7. Applications work satisfactorily after installing the app.
8. Do social networking options like sharing, publishing, etc. work as needed?
9. Do mandatory fields work as required?  Does the app support payment gateway transactions?
10. Are page scrolling scenarios working as expected?
11. Navigate between different modules as expected.
12. Are appropriate error messages received if necessary? 

2. Performance testing test cases

1. Can the app handle the expected cargo volumes?
2. What are the various mobile app and infrastructure bottlenecks preventing the app from performing as expected?
3. Is the response time as expected?  Are battery drain, memory leaks, GPS and camera performance within the required guidelines?
4. Current network coverage able to support the app at peak, medium and minimum user levels?
5. Are there any performance issues if the network changes from / to Wi-Fi and 2G / 3G / 4G?
6. How does the app behave during the intermittent phases of connectivity?
7. Existing client-server configurations that provide the optimum performance level? 

3. Battery usage test cases

1. Mobile app power consumption 
2. User interface design that uses intense graphics or results in unnecessarily high database queries
3. Battery life can allow the app to operate at expected charge volumes
4. Battery  low and high performance requirements
5. Application operation if used when battery is removed Battery usage and data leaks
6. New features and updates do not introduce new battery usage and data 
7. Related:  The secret art of battery testing on Android 

1. The buttons are of a user-friendly size. 
2. The position, style, etc. of the buttons are consistent within the app
3. Icons are consistent within the application
4. The zoom in and out functions work as expected
5. The keyboard can be minimized and maximized easily.
6. The action or touching the wrong item can be easily undone.
7. Context menus are not overloaded.
8. Verbiage is simple, clear and easily visible.
9. The end user can easily find the help menu or user manual in case of need.
10. Related: High impact usability testing that is actually doable 

We will see more points in our next articles.

dependencies {
    implementation "com.google.android.material:$latest_version"
}

Snackbar.make(view, "Show some message here", Snackbar.LENGTH_SHORT).show()

<?xml version="1.0" encoding="utf-8"?>
<android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:id="@+id/coordinatorLayout"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context="com.example.application.snackbarapp.MainActivity">

    <RelativeLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <Button
            android:id="@+id/button"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_centerHorizontal="true"
            android:layout_centerVertical="true"
            android:text="show snackbar" />

    </RelativeLayout>

</android.support.design.widget.CoordinatorLayout>

import android.graphics.Color;
import android.support.design.widget.CoordinatorLayout;
import android.support.design.widget.Snackbar;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.view.View;
import android.widget.Button;
import android.widget.TextView;

public class MainActivity extends AppCompatActivity {
    private CoordinatorLayout coordinatorLayout;
    private Button button;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        coordinatorLayout = findViewById(R.id.coordinatorLayout);
        button = findViewById(R.id.button);

        button.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View v) {
                showSnackbar();
            }
        });
    }

    public void showSnackbar() {
        Snackbar snackbar = Snackbar.make(coordinatorLayout, "Marked as Read", Snackbar.LENGTH_INDEFINITE)
                .setAction("UNDO", new View.OnClickListener() {
                    @Override
                    public void onClick(View v) {
                        Snackbar snackbar1 = Snackbar.make(coordinatorLayout, "Undo successful", Snackbar.LENGTH_SHORT);
                        snackbar1.show();
                    }
                })
                .setActionTextColor(Color.RED);

        snackbar.show();
    }
}