<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shashi Deep on Medium]]></title>
        <description><![CDATA[Stories by Shashi Deep on Medium]]></description>
        <link>https://medium.com/@shashidulam83?source=rss-379c67d74881------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Hjn8ejM0AmlMRiHkUDsaUw.jpeg</url>
            <title>Stories by Shashi Deep on Medium</title>
            <link>https://medium.com/@shashidulam83?source=rss-379c67d74881------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:05:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shashidulam83/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automating Kubernetes Deployment Using eksctl + kubectl + awscli — Part 1]]></title>
            <link>https://medium.com/@shashidulam83/automating-kubernetes-deployment-using-eksctl-kubectl-awscli-part-1-3d5a683b64ed?source=rss-379c67d74881------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d5a683b64ed</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Shashi Deep]]></dc:creator>
            <pubDate>Sun, 05 Jul 2020 20:17:42 GMT</pubDate>
            <atom:updated>2020-07-05T21:02:51.818Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automating Kubernetes Deployment Using eksctl + kubectl + awscli — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*I3pW1rjFFZ2LgI2tqp4nsg.png" /></figure><blockquote>We will configure , deploy various tasks with eksctl , kubectl and awscli. Launch a Webapp with MySQL DB and integrate K8s with helm to use Prometheus , Grafana for monitoring and visualization.</blockquote><h3><strong>Installing AWS CLI on Linux :</strong></h3><pre>curl “<a href="https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip">https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip</a>&quot; -o “awscliv2.zip”<br>unzip awscliv2.zip<br>sudo ./aws/install</pre><pre>pip3 install — upgrade — user awscli</pre><h3><strong>Configuring AWS CLI by creating a programmatic user :</strong></h3><blockquote>We can get the access key and secret from AWS Console — IAM → Users → Add User → Create programmatic User</blockquote><pre>$ aws configure<br>AWS Access Key ID [None]: Access Key ID<br>AWS Secret Access Key [None]: Secret Access Key<br>Default region name [None]: region-code<br>Default output format [None]: json</pre><h3>Configuring eksctl :</h3><blockquote>eksctl is a simple CLI tool for creating clusters on EKS - Amazon&#39;s new managed Kubernetes service for EC2. It is written in Go, and uses CloudFormation.</blockquote><pre>curl — silent — location “<a href="https://github.com/weaveworks/eksctl/releases/latest/download/eksctl_$(uname">https://github.com/weaveworks/eksctl/releases/latest/download/eksctl_$(uname</a> -s)_amd64.tar.gz” | tar xz -C /tmp<br>sudo mv /tmp/eksctl /usr/local/bin</pre><pre>eksctl version</pre><h3><strong>Launching of worker nodes with different configs :</strong></h3><p>Worker machines in Kubernetes are called nodes. Amazon EKS worker nodes run in your AWS account and connect to your cluster’s control plane via the cluster API server endpoint. You deploy one or more worker nodes into a node group. A node group is one or more Amazon EC2 instances that are deployed in an Amazon EC2 Auto Scaling group. All instances in a node group must:</p><ul><li>Be the same instance type</li><li>Be running the same Amazon Machine Image (AMI)</li><li>Use the same <a href="https://docs.aws.amazon.com/eks/latest/userguide/worker_node_IAM_role.html">Amazon EKS worker node IAM role</a></li></ul><p>A cluster can contain several node groups, and each node group can contain several worker nodes. If you deploy <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">managed node groups</a>, then there is a maximum number of nodes that can be in a node group and a maximum number of node groups that you can have within a cluster.</p><blockquote>Here we configuring and launching two node groups with 3 EC2 instances. Nodegroup 1 having two instances of t2.micro from ap-south-1 region and one in nodegroup2 having t2.small instance from the same region.</blockquote><pre>apiVersion: eksctl.io/v1alpha5<br>kind: ClusterConfig<br>metadata:<br> name: ekstest1<br> region: ap-south-1</pre><pre>nodeGroups:<br> — name: nodegroup1<br> desiredCapacity: 2<br> instanceType: t2.micro</pre><pre>- name: nodegroup2<br> desiredCapacity: 1<br> instanceType: t2.small</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m9RIqC09KSwJPLWm5HR3PQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PQOhJ7eSWRWcmN9IPN2o4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdcjRBG2soCtkrWaTmpdrg.png" /></figure><h3><strong>Creating Spot instances with eksctl :</strong></h3><blockquote>eksctl has support for spot instances through the MixedInstancesPolicy for Auto Scaling Groups.</blockquote><blockquote>Here is an example of a nodegroup that uses 50% spot instances and 50% on demand instances:</blockquote><pre>apiVersion: eksctl.io/v1alpha5<br>kind: ClusterConfig</pre><pre>metadata:<br>  name: ekstest1 <br>  region: ap-south-1</pre><pre>nodeGroups:<br>  - name: nodegroup1<br>    desiredCapacity: 2<br>    instanceType: t2.micro<br>    ssh:<br>      publicKeyName: redhat</pre><pre>- name: nodegroup2<br>    desiredCapacity: 1<br>    instanceType: t2.small</pre><pre>- name: nodegroup3<br>    minSize: 2<br>    maxSize: 5<br>    instanceDistribution:<br>      maxPrice: 0.017<br>      instanceTypes: [&quot;t3.small&quot;,&quot;t3.medium&quot;]<br>      onDemandBaseCapacity: 0<br>      onDemandPercentageAboveBaseCapacity: 50<br>      spotInstancePools: 2</pre><h3><strong>Creating kubectl config file :</strong></h3><pre>aws eks update-kubeconfig — name ekstest1</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*YR8D8apo8FbWL4p4VFF7aQ.png" /></figure><h3><strong>Creating a deployment with a docker image :</strong></h3><blockquote>The docker image we are using have an apache web server pre-installed and configured with a sample PHP code.</blockquote><pre>kubectl create deployment testweb — image=shashi/test-apache-php</pre><h3><strong>Scaling deployment with multiple replicas :</strong></h3><p>A ReplicaSet’s purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often used to guarantee the availability of a specified number of identical Pods.</p><pre>kubectl scale deployment testweb — replicas=4</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1OYgR7EVukqYvolmH9BQmg.png" /></figure><h3><strong>Adding load balancer to the deployment :</strong></h3><blockquote>Amazon EKS supports the Network Load Balancer and the Classic Load Balancer for pods running on Amazon EC2 instance</blockquote><pre>kubectl expose deployment webtest — type=LoadBalancer — port=80</pre><h3><strong><em>Updating files with kubectl :</em></strong></h3><blockquote>Updating a sample php code that returns test server</blockquote><pre>kubectl cp index.php testweb-66f5869f69-dp7rs:/var/www/html/index.php</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*cekQzHkLwByFSCpwYgK6Cg.png" /></figure><h3><strong>Adding persistent storage to the pods :</strong></h3><blockquote>Pods use PersistentVolumeClaims to request physical storage that requests a volume of at least three gibibytes that can provide read-write access for at least one Node.</blockquote><blockquote>We are mounting 10Gb PersistentVolume by creating a dynamic pvc. Whenever a pod goes down PersistentVolume will be attached to the pod without any data loss.</blockquote><h3><strong>Creating pvc with yml :</strong></h3><p>kubectl create -f pvc.yml</p><pre>apiVersion: v1<br>kind: PersistentVolumeClaim</pre><pre>metadata:<br>  name: testpvc</pre><pre>spec:<br>  accessModes:<br>    -  ReadWriteOnce<br>  resources:<br>    requests:<br>      storage: 10Gi</pre><h3><strong>Attaching volume and mounting it to deployment:</strong></h3><pre>spec:<br> volumes: <br> — name: testvol1<br> persistentVolumeClaim:<br> claimName: testpvc<br> containers:<br> — image: shashi/testapp-php<br> volumeMounts:<br> — mountPath: /var/www/html<br> name: testvol1</pre><h3><strong>Updating storage class :</strong></h3><blockquote>Cuurently we have gp2 Storage class from ebs. We are updating storage class for a better IOPS.We are keeping reclaimPolicy as retain .So volume with data will be available even if the pod goes down.</blockquote><pre>apiVersion: storage.k8s.io/v1<br>kind: StorageClass<br>metadata:<br> name: testsc1<br>provisioner: kubernetes.io/aws-ebs<br>parameters:<br> type: io1<br>reclaimPolicy: Retain</pre><h3><strong>Launching a WebApp with MySQL DB :</strong></h3><pre>apiVersion: v1<br>kind: Service</pre><pre>metadata:<br>  name: wordpress-mysql<br>  labels:<br>    app: wordpress</pre><pre>spec:<br>  ports:<br>    - port: 3306<br>  selector:<br>    app: wordpress<br>    tier: mysql<br>  clusterIP: None<br>---</pre><pre>apiVersion: v1<br>kind: PersistentVolumeClaim<br>metadata:<br>  name: mysql-pv-claim<br>  labels:<br>    app: wordpress<br>spec:<br>  accessModes:<br>    - ReadWriteMany<br>  resources:<br>    requests:<br>      storage: 20Gi<br>---</pre><pre>apiVersion: apps/v1 <br>kind: Deployment</pre><pre>metadata:<br>  name: wordpress-mysql<br>  labels:<br>    app: wordpress<br>spec:<br>  selector:<br>    matchLabels:<br>      app: wordpress<br>      tier: mysql<br>  strategy:<br>    type: Recreate<br>  template:<br>    metadata:<br>      labels:<br>        app: wordpress<br>        tier: mysql<br>    spec:<br>      containers:<br>      - image: mysql:5.6<br>        name: mysql<br>        env:<br>        - name: MYSQL_ROOT_PASSWORD<br>          valueFrom:<br>            secretKeyRef:<br>              name: mysql-pass<br>              key: password <br>        ports:<br>        - containerPort: 3306<br>          name: mysql<br>        volumeMounts:<br>        - name: mysql-persistent-storage<br>          mountPath: /var/lib/mysql<br>      volumes:<br>      - name: mysql-persistent-storage  <br>        persistentVolumeClaim:<br>          claimName: mysql-pv-claim</pre><pre>apiVersion: v1<br>kind: Service</pre><pre>metadata:<br>  name: wordpress<br>  labels:<br>    app: wordpress<br>spec:<br>  ports:<br>    - port: 80<br>  selector:<br>    app: wordpress<br>    tier: frontend<br>  type: LoadBalancer<br>---</pre><pre>apiVersion: v1<br>kind: PersistentVolumeClaim<br>metadata:<br>  name: wp-pv-claim<br>  labels:<br>    app: wordpress<br>spec:<br>  accessModes:<br>    - ReadWriteMany<br>  resources:<br>    requests:<br>      storage: 20Gi</pre><pre>---</pre><pre>apiVersion: apps/v1 <br>kind: Deployment</pre><pre>metadata:<br>  name: wordpress<br>  labels:<br>    app: wordpress</pre><pre>spec:<br>  selector:<br>    matchLabels:<br>      app: wordpress<br>      tier: frontend<br>  strategy:<br>    type: Recreate<br>  template:<br>    metadata:<br>      labels:<br>        app: wordpress<br>        tier: frontend<br>    spec:<br>      containers:<br>      - image: wordpress:4.8-apache<br>        name: wordpress<br>        env:<br>        - name: WORDPRESS_DB_HOST<br>          value: wordpress-mysql<br>        - name : WORDPRESS_DB_PASSWORD<br>          valueFrom:<br>            secretKeyRef:<br>              name: mysql-pass<br>              key: password <br>        ports:<br>        - containerPort: 80<br>          name: wordpress<br>        volumeMounts:<br>        - name: wordpress-persistent-storage<br>          mountPath: /var/www/html<br>      volumes:<br>      - name: wordpress-persistent-storage  <br>        persistentVolumeClaim:<br>          claimName: wp-pv-claim</pre><h3>Using kustomize to launch the above YAML files:</h3><blockquote>kustomize lets you customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is.</blockquote><pre>apiVersion: kustomize.config.k8s.io/v1beta1</pre><pre>kind: Kustomization<br>secretGenerator:<br>- name: mysql-pass<br>  literals:<br>  - password= password</pre><pre>resources:<br>  - deploy-mysql.yaml<br>  - deploy-wordpress.yaml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DfmcUOpkjVZFwBSbDkXDg.png" /></figure><p>In Part -2 , We will integrate K8s with helm and use Prometheus and Grafana for monitoring.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d5a683b64ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Launch Of a WebApp Using Terraform.]]></title>
            <link>https://medium.com/@shashidulam83/automating-launch-of-a-webapp-using-terraform-5e348460c9a7?source=rss-379c67d74881------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e348460c9a7</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Shashi Deep]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 17:29:41 GMT</pubDate>
            <atom:updated>2020-06-15T17:43:14.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*IRAGVUvKvfVntmLjIy93AA.jpeg" /></figure><blockquote><strong>Automating Launch of a WebAPP built on EC2 + EBS + S3 + CloudFront using Terraform and GitHub in series of tasks.</strong></blockquote><ul><li>Creating and storing a key and creating a Security Group which allows the port 22 (SSH) and port 80 (HTTP) for ingress.</li><li>Launching an EC2 instance with the key and security group which we have created earlier. Storing the Public-IP Generated.</li><li>Installing httpd , PHP and GIT command and enabling auto-restart using systemctl.</li><li>Creating and launching one EBS (Elastic Block Store) Volume with 1 GB storage.</li><li>Formatting and Attaching the created EBS on EC2 instance that has been created earlier</li><li>Pulling a public GitHub Repo /var/www/html into EBS.</li><li>Creating an S3 bucket and to deploy the images from GitHub repo into the s3 bucket and change the permission for public access.</li><li>Creating a Cloudfront using s3 bucket(which contains images) and using the Cloudfront URL for updating the code in /var/www/html.</li></ul><p>Code :</p><p>Providing the cloud provider name for terraform to access it.</p><pre>provider “aws” {<br> region = “ap-south-1”<br> profile = “terraform_task1”<br>}</pre><p>Launching EC2 with the Stored Key and Security Group and installing required dependencies using sudo :</p><pre>resource &quot;aws_instance&quot; &quot;myin&quot; {<br>ami=&quot;ami-052c08d70def0ac62&quot;<br>instance_type=&quot;t2.micro&quot;<br>key_name=&quot;redhat&quot;<br>security_groups=[&quot;launch-wizard-1&quot;]</pre><pre>connection {<br> <br> type = &quot;ssh&quot;<br> user = &quot;ec2-user&quot;<br> private_key=file(&quot;/home/shashi/Downloads/redhat.pem&quot;)<br> host =aws_instance.myin.public_ip<br>}</pre><pre>provisioner &quot;remote-exec&quot; {<br> <br> inline=[<br>  &quot;sudo yum install httpd php git -y&quot;,<br>  &quot;sudo systemctl restart httpd&quot;,<br>  &quot;sudo systemctl enable httpd&quot;<br> ]<br>}</pre><pre>tags= {</pre><pre>Name=&quot;terraform os&quot;<br>}<br>}</pre><p>Creating an EBS Volume with 1GB Storage :</p><pre>resource &quot;aws_ebs_volume&quot; &quot;ebs1terra&quot; {<br>  availability_zone = aws_instance.myin.availability_zone<br>  size              = 1<br> <br>  tags = {<br>    Name = &quot;ebshardisk&quot;<br>  }<br>}</pre><p>Attaching the EBS volume to a created instance :</p><pre>resource &quot;aws_volume_attachment&quot; &quot;ebs_attach_myin&quot; {<br>  device_name = &quot;/dev/sdh&quot;<br>  volume_id   = aws_ebs_volume.ebs1terra.id<br>  instance_id = aws_instance.myin.id<br>  force_detach=true<br>}</pre><p>Executing and Storing the Public-IP generated</p><pre>resource &quot;null_resource&quot; &quot;nulllocal8&quot; {</pre><pre>provisioner &quot;local-exec&quot; {<br> <br> command = &quot;echo ${aws_instance.myin.public_ip} &gt; public_ip.txt&quot;<br>}<br>}</pre><p>Use depends_on function to make sure formatting and cloning of git repo happens only after attaching EBS</p><p>Formating EBS volume and Cloning of Git Repo :</p><pre>resource &quot;null_resource&quot; &quot;nullremote9&quot; {</pre><pre>depends_on=[<br>  <br>  aws_volume_attachment.ebs_attach_myin,</pre><pre>]</pre><pre>connection {<br> <br> type = &quot;ssh&quot;<br> user = &quot;ec2-user&quot;<br> private_key=file(&quot;/home/shashi/Downloads/redhat.pem&quot;)<br> host =aws_instance.myin.public_ip<br>}</pre><pre>provisioner &quot;remote-exec&quot; {<br> <br> inline=[<br>  &quot;sudo mkfs.ext4 /dev/xvdh&quot;,<br>  &quot;sudo mount /dev/xvdh /var/www/html&quot;,<br>  &quot;sudo rm -rf /var/www/html/*&quot;,<br>  &quot;sudo git clone <a href="https://github.com/Shashideep83/pull_terraform.git">https://github.com/Shashideep83/pull_terraform.git</a> /var/www/html&quot;</pre><pre>]<br>}<br>}</pre><p>Creating and Publishing image to S3 Bucket :</p><pre>resource &quot;aws_s3_bucket&quot; &quot;terra-bucket&quot; {<br> bucket = &quot;terra-bucket&quot;<br> acl = &quot;public-read&quot;<br> tags = {<br>  Name = &quot;terra-bucket&quot;<br> }<br>}</pre><pre>resource &quot;aws_s3_bucket_object&quot; &quot;image-png&quot; {<br> bucket = &quot;terra-bucket&quot;<br> key = &quot;image.png&quot;<br> source = &quot;../image/image.png&quot;<br> etag = filemd5(&quot;../image/image.png&quot;)<br> acl = &quot;public-read&quot;<br>}</pre><pre>locals {<br> s3_origin_id = &quot;s3-origin&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fo52wgR_qDvgXqnk8w9fJg.png" /></figure><p>Configuring CloudFront for fast content delivery with low latency and high transfer speeds.</p><pre>resource &quot;aws_cloudfront_distribution&quot; &quot;terra-cloudfront&quot; {<br> enabled = true<br> is_ipv6_enabled = true<br> <br> origin {<br>  domain_name = aws_s3_bucket.terra-bucket.bucket_regional_domain_name<br>  origin_id = local.s3_origin_id<br> }</pre><pre>restrictions {<br>  geo_restriction {<br>   restriction_type = &quot;none&quot;<br>  }<br> }</pre><pre>default_cache_behavior {<br>  target_origin_id = local.s3_origin_id<br>  allowed_methods = [&quot;HEAD&quot;, &quot;DELETE&quot;, &quot;POST&quot;, &quot;GET&quot;, &quot;OPTIONS&quot;, &quot;PUT&quot;, &quot;PATCH&quot;]<br>     cached_methods  = [&quot;HEAD&quot;, &quot;GET&quot;, &quot;OPTIONS&quot;]</pre><pre>forwarded_values {<br>        query_string = false<br>        cookies {<br>          forward = &quot;none&quot;<br>        }<br>  }</pre><pre>viewer_protocol_policy = &quot;redirect-to-https&quot;<br>     min_ttl                = 0<br>     default_ttl            = 120<br>     max_ttl                = 86400<br> }</pre><pre>viewer_certificate {<br>     cloudfront_default_certificate = true<br>   }<br>}</pre><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e348460c9a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile Application Automation Tools]]></title>
            <link>https://medium.com/@shashidulam83/mobile-application-automation-tools-650cb751f4f?source=rss-379c67d74881------2</link>
            <guid isPermaLink="false">https://medium.com/p/650cb751f4f</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-testing]]></category>
            <dc:creator><![CDATA[Shashi Deep]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 07:06:55 GMT</pubDate>
            <atom:updated>2019-12-27T11:22:25.213Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mobile App Automation Tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*N5M8NJtZp83EMrK1WGhjjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*vWqv-nXbJi-0WzvBueFsnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*YTaDFa7lRcJ4oX3Mdk-a3Q.jpeg" /></figure><p>A comprehensive curated list of Mobile Application automation frameworks, tools, libraries and software to easily bootstrap test automation. and when to Use the Most Popular Automation Tools Appium and Selendroid</p><h4>Table of content:</h4><ul><li>Android Automation Tools</li><li>Environments</li></ul><h3>Android Automation Tools</h3><ul><li><a href="http://appium.io/?source=post_page---------------------------"><strong>Appium</strong></a><strong> </strong>— An open-source mobile test automation tool to test Android and iOS applications. Developers can test native, mobile web and Hybrid mobile apps on this software. To run the tests, Appium uses WebDriver interface. It supports C#, Java, Ruby, and many other programming languages that belong to WebDriver library. Testers can test native apps that are written in Android and iOS SDKs, mobile web apps that can be accessible through mobile browser, and hybrid apps that contain web view. Being a cross-platform tool, it allows programmers to reuse the source code amongst Android and iOS.</li><li><a href="http://selendroid.io/"><strong>Selendroid</strong></a> — Selendroid is a good option if you’re thinking of developing only Android apps. Its main selling point is its backward compatibility; it supports Android API 10 (Android 2.3.3) through API 19 (Android 4.4).</li><li><a href="https://code.google.com/p/robotium/"><strong>Robotium</strong></a> — An Android test automation framework that fully supports native and hybrid applications. Robotium makes it easy to write powerful and robust automatic black-box UI tests for Android applications. With the support of Robotium, test case developers can write function, system and user acceptance test scenarios, spanning multiple Android activities.</li><li><a href="http://developer.android.com/tools/help/uiautomator/index.html"><strong>UIautomator</strong></a> — Provides an efficient way to test UIs. It creates automated functional test cases that can be executed against apps on real Android devices and emulators. It includes a viewer, which is a GUI tool to scan and analyze the UI components of an Android app.</li><li><a href="https://code.google.com/p/android-test-kit/wiki/Espresso"><strong>Espresso</strong></a> — A pretty new test automation framework that got open-sourced just last year, making it available for developers and testers to hammer out their UIs. Espresso has an API that is small, predictable, easy to learn and built on top of the Android instrumentation framework. You can quickly write concise and reliable Android UI tests with it.</li></ul><h3>Comparing Two Top Automation tools -</h3><h3><a href="http://appium.io/?source=post_page---------------------------">Appium</a></h3><ul><li>A lot of the distinct advantages that Appium has over Selendroid make it a stronger choice. Unlike Selendroid, Appium supports the testing of iOS apps along with Android. It also offers an easier experience over Selendroid by not having to use an SDK, and removes the need to recompile applications to test them. This also means that the app you test is the one you ship without having to modify anything just for the purpose of testing. Appium has its own UI inspector, but the Android Studio tool, uiautomatorviewer, can be used as well.</li><li>Although Appium cannot be used to test apps for Android APIs lower than 17, it does come with a Selendroid mode to help with that. Selendroid came bundled with Appium v1.2 onwards, and under Appium’s Selendroid mode, it can help test apps on older Android versions, but with a few limitations — such as lacking the ability to locate UI elements like Selendroid, or the ability to use the same script in either modes without modification. These limitations can be overcome by using Selendroid as a standalone tool, separate from Appium</li></ul><h3><a href="http://selendroid.io/">Selendroid</a></h3><ul><li>Selendroid is a good option if you’re thinking of developing only Android apps. Its main selling point is its backward compatibility; it supports Android API 10 (Android 2.3.3) through API 19 (Android 4.4).</li><li>Also notable is that Selendroid contains an Inspector tool which can inspect UI elements of the app being tested. Although you can find UI elements in Appium as well, the advantage that Selendroid has over Appium is that Selendroid can find UI elements for older Android versions, too.</li><li>There are a few other features Selendroid has in its arsenal. During tests, devices can be plugged or unplugged without interrupting the test being run, also called “hot plugging.” This in turn is helped by Selendroid’s ability to interact with multiple Android devices at the same time, which includes emulators and hardware devices, saving you a lot of time in the process</li></ul><h3>Environments</h3><ul><li><a href="http://bbc.github.io/hive-ci/">Hive CI</a> is a CI system built around devices. Connect your physical devices to a hive and run your tests on the same platforms as your users</li><li><a href="https://github.com/openstf/stf">STF</a> — STF (or Smartphone Test Farm) is a web application for debugging smartphones, smartwatches and other gadgets remotely, from the comfort of your browser.</li><li><a href="https://github.com/square/spoon">spoon</a> — Distributing instrumentation tests to all your Androids.</li><li><a href="https://www.genymotion.com/">Genymotion</a> — Genymotion is one of the best free Android emulators on the market. The software, which is both powerful and easy to use, will be of interest to the naturally curious, as well as for Android developers.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=650cb751f4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>