DEV Community: Jaira Encio

AWS for QA Testing

Jaira Encio — Thu, 03 Aug 2023 01:06:03 +0000

Sharing the content of my topic during AWS Community Day Philippines.

Topics

Importance of Cloud for QA Testers
AWS Services for Testing

Importance of Cloud for QA Testers

Understand how cloud ecosystem works
Gain knowledge on system design
AWS Testing tools

What are some AWS tools and services for QA testers?

AWS Device Farm - Mobile/Web testing tool
Amazon Inspector - Security testing tool
Automation with AWS Tools

AWS Device Farm - Mobile/Web testing tool

Device Farm is an app testing service that you can use to test and interact with your Android, iOS, and web apps on real, physical phones and tablets that are hosted by Amazon Web Services (AWS).

Test on real mobile devices using Automated Testing and Remote Access.

Automated Testing

Testing can be automated. You can upload your application, which is an APK or IPA file, as well as any automated testing frameworks or scripts you may already have with you such as Appium, Kellabash, XC test, or others.

But suppose you don't have any kind of automated scripts in place. Device Farm assists you in this situation by running its own quick tests or exploratory tests on your uploaded application.

Remote Access

You can also use this specific option known as the remote access if you prefer a more manual method of testing on various devices within AWS.

Remote access provides you with a remote access to devices (phones and tablets) for interactive testing.

Desktop browsers

AWS Device farm also has support for desktop browser testing. You can upload and run your Selenium tests on multiple desktop browsers hosted on AWS.
For every browser the test is executed on, Device Farm generates video recordings and Selenium logs to help you quickly identify any issues with your web app.

Device farm pricing

Pay for a particular device per minute
Pay for a particular device for a whole month
For desktop browsers, you pay for every instance minute you run

Amazon Inspector - Security testing tool

Amazon Inspector is a vulnerability management service that continuously scans your AWS workloads for software vulnerabilities and unintended network exposure.

Security testing sample on EC2 Instance

Steps:

Prepare a production EC2 instance on which a network accessibility check is necessary.
Open Port 21 and 22 to create a security concern.
Use Amazon Inspector to do an examination and vulnerability check.

It is generally not advised to leave port 21 open on your production instance or instances because it is Used by FTP to allow file transfers.

This EC2 instance acted as a target instance for assessment and it has found three findings; information, medium, and high.
It's telling you that there is a network exposure and is reachable through the Internet. In case you want to take any action, then the recommendation is that you need to go ahead and edit your security group to remove this particular access.

Amazon Inspector provides a clear list of security and compliance findings assigned a priority by the severity level. Moreover, these findings can be analyzed directly or as part of comprehensive assessment records available via the API or AWS Inspector console.

Importance of Inspector

Amazon Inspector security assessments allows you to make security testing more regular occurrence as part of the development and IT operations.

Automation with AWS Tools

QA engineers can use AWS services to automate and streamline their testing processes and ensure that their applications are ready for deployment.

Services such as CodeBuild, CodePipeline, and many others can be used to create an automation testing tool.

Automation testing samples with AWS

Conclusion

Any software development process must include testing. Quality assurance helps a company create products and services that meet the needs, expectations and requirements of customers. It yields high-quality product offerings that build trust and loyalty with customers.

Setting up Automated API testing with Postman Collection using Newman CLI, AWS Codebuild, CodePipeline, & S3

Jaira Encio — Sat, 12 Nov 2022 15:25:40 +0000

In this post you will learn how to automate your own build of postman collections with aws codecommit, codepipeline, and codebuild.

Newman is a command-line collection runner for Postman.

Postman is an API platform for building and using APIs.

CodeCommit is a secure, highly scalable, managed source control service that hosts private Git repositories.

CodeBuild compiles your source code, runs unit tests, and produces artifacts that are ready to deploy.

CodePipeline is a continuous delivery service you can use to model, visualize, and automate the steps required to release your software.

File Structure

── /CodeCommitRepo/         # root folder
  ├── /buildspec.yml        # source code for build commands
  └── /api.postman_collection.json # postman collection

Overview

Export Postman Collection
Create Buildspec.yml
Create CodeCommit Repository and push files
Create S3 bucket for output report
Create a build project in AWS CodeBuild
Create pipeline in CodePipeline and build all together

1. Export Postman Collection

Open your postman collection and select the more actions icon More actions icon next to the collection, then select Export.

Select the format you'd like your collection to export as then select export to download your newly generated JSON file.

2. Create Buildspec.yml

Copy the code below to buildspec.yml. Make sure to place your file along with your exported postman collection.

version: 0.2

phases:
  pre_build:
    commands:
      - npm install -g newman
      - npm install -g newman-reporter-html

  build:
    commands:
      - newman run -r html,cli test_api.postman_collection.json --reporter-html-export report.html

artifacts:
  files:
    - report.html

This installs newman and newman-reporter-html dependencies for our postman cli. After prebuild, this will run cli command to run and generate html report from our postman collection newman run -r html,cli {name}.postman_collection.json --reporter-html-export report.html.

3. Create CodeCommit Repository and push files

Open the CodeCommit console at https://console.aws.amazon.com/codesuite/codecommit/home then click create repository

Enter Repository name and description (optional) then click create

Clone repository and push your buildspec and postman file. You can specify a certain branch but we will just be using master.

4. Create s3 bucket for report

This will serve as the output folder for our generated html report.

Open the S3 console at https://console.aws.amazon.com/s3/ then click Create bucket

Enter bucket name and click Create bucket

5. Create a build project in AWS CodeBuild

Open the AWS CodeBuild console at https://console.aws.amazon.com/codesuite/codebuild/home then click Create project

Fill in the following sections. Once complete, choose Create build project at the bottom of the page.

Sections:
Project configuration - Name and description
Source provider - AWS Codecommit, repo name
Environment - Ubuntu, Standard, aws/codebuild/standard:6.0
Buildspec
Batch configuration
Artifacts - s3, bucket name
Logs

6. Create pipeline in CodePipeline and build all together

We will now combine our process by using AWS CodePipeline to pull our source code in CodeCommit, run build with AWS CodeBuild and output generated html in S3

Open the CodePipeline console at http://console.aws.amazon.com/codesuite/codepipeline/home and choose Create Pipeline

On the Step 1: Choose pipeline settings page; in Pipeline name, enter the name for your pipeline.

Choose New service role to allow CodePipeline to create a new service role in IAM.

On the Step 2: Add source stage page; in Source provider, select AWS CodeCommit, repo name, and branch name.

On the Step 3: Add build stage page, select AWS Codebuild and project name

On the Step 4: Add deploy stage page, Choose Skip deploy stage.

On the Step 5: Review, Review all changes then click create pipeline.

Output

You should see Succeeded status after running pipeline. The build log shows from prebuild ,running command, and generating output.

Go to your s3 bucket to view successful report

To share this html report with others. You can use presigned URLs

To generate a presigned URL using the AWS Management Console

In the Buckets list, choose the name of the bucket that contains the object that you want a presigned URL for.
In the Objects list, select the object that you want to create a presigned URL for.
On the Actions menu, choose Share with a presigned URL.
Specify how long you want the presigned URL to be valid.
Choose Create presigned URL.
When a confirmation appears, the URL is automatically copied to your clipboard. You will see a button to copy the
presigned URL if you need to copy it again.

References:
https://learning.postman.com/docs/running-collections/using-newman-cli/installing-running-newman/

https://www.npmjs.com/package/newman-reporter-html

https://unmesh.me/2017/06/10/api-testing-with-postman-collections-in-aws-codepipeline/

Setting up Email Notification for EC2 instance changes using Amazon SNS and Eventbridge

Jaira Encio — Thu, 17 Mar 2022 10:57:40 +0000

Output: To receive email notif everytime your EC2 instances changes its status. (Terminated, Stopped, etc)

What is Amazon SNS?
Amazon SNS enables you to send notifications directly to your customers.

What is Amazon EventBridge?
Amazon EventBridge is a serverless event bus that makes it easier to build event-driven applications at scale using events generated from your applications, integrated Software-as-a-Service (SaaS) applications, and AWS services.

Overview

Setup SNS topic
Create email subscription on topic
Setup EC2 Instance State-change Notification eventbridge rule

Setting up SNS topic and email subscription

1. Go to AWS SNS console, and then choose Topics from the navigation pane.

2. Select Create topic.

For the type, I would be selecting Standard. Then just enter name and display name for your topic.

3. Click Create topic.

4. On the Subscriptions tab, click Create subscription.

For Protocol, select Email.
For Endpoint, enter the email address where you want to receive the notifications.

If you want to change this to a SMS notif, you can simple select SMS for protocal then enter mobile number on endpoint where you want to receive notifications.

5. Click Create subscription.

6. Confirm email subscription sent to the email address you entered.

7. Go to your topic then check email status.

It should show that your email is now confirmed.

Setting up EC2 TerminateInstances eventbridge rule

1. Open the EventBridge console, and then click Create Rule

2. Fill up details on define rule detail then click next

Enter a Name and description for your rule.
On rule type, select rule with an event pattern

3. Fill up details on Build event pattern then click next

For Service provider, choose AWS.
For Service name, choose EC2.
For Event type, choose EC2 Instance State-change Notification.

4. Fill up select targets then click next

In Select targets, choose SNS topic from the Target dropdown list.
For Topic, choose the topic name that you created earlier.

5. Click Create rule

You can test this rule by terminating your instance. This rule generates an email notification every time an instance is terminated. You can select other states as well.

Setting up Selenium in Docker Container and Pushing Image in Amazon ECR

Jaira Encio — Thu, 17 Feb 2022 07:06:03 +0000

Overview: Running headless mode selenium in Docker Container then pushing image in Amazon ECR.

What is Amazon ECR?
Amazon Elastic Container Registry (ECR) is a fully managed Docker container registry that makes it easy to store, share, and deploy container images.

What is Docker container?
A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.

File Structure


 shell
── /MyFolder/               # root folder
  ├── /main_test.py         # source code main test
  ├── /requirements.txt     # dependencies
  └── /Dockerfile           # docker commands

Code

Copy the following inside main_test.py


 shell
import unittest
from selenium import webdriver
from time import sleep


class app_test_case(unittest.TestCase):


    def setUp(self):
        chromeOptions = webdriver.ChromeOptions()
        driver_path = '/usr/local/bin/chromedriver'
        chromeOptions.add_argument('--headless')
        chromeOptions.add_argument('--disable-gpu')
        chromeOptions.add_argument('--no-sandbox')


        self.driver = webdriver.Chrome(driver_path, chrome_options=chromeOptions)
        self.driver.implicitly_wait(30)
        self.driver.maximize_window()
        path = 'https://www.google.com/'
        self.base_url = path


    def test_i_d_e_script1(self):
        driver = self.driver
        driver.get(self.base_url)

        get_title = driver.title
        print(get_title, "  ", len(get_title))


    def tearDown(self):
        sleep(5)
        self.driver.quit()


if __name__ == "__main__":
    unittest.main()

Copy the following inside requirements.txt


 shell
selenium==3.12.0
ipython==7.0.1

Copy the following inside Dockerfile


 shell
FROM python:3


WORKDIR /srv


ADD . /srv
RUN apt-get -y update
RUN pip install --upgrade pip
RUN apt-get install zip -y
RUn apt-get install unzip -y


RUN pip install -r requirements.txt


# Install chromedriver
RUN wget -N https://chromedriver.storage.googleapis.com/72.0.3626.69/chromedriver_linux64.zip -P ~/
RUN unzip ~/chromedriver_linux64.zip -d ~/
RUN rm ~/chromedriver_linux64.zip
RUN mv -f ~/chromedriver /usr/local/bin/chromedriver
RUN chown root:root /usr/local/bin/chromedriver
RUN chmod 0755 /usr/local/bin/chromedriver


# Install chrome broswer
RUN curl -sS -o - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
RUN echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list
RUN apt-get -y update
RUN apt-get -y install google-chrome-stable


CMD ["python", "main_test.py"]

Dockerfile is the one that builds a Docker image. The image contains all the dependencies our application needs, including Python itself.

Build and Run New Docker Image

Once Dockerfile and all required config files have been created, we can now build a new docker image


 shell
$ docker build -t myapp .

Check created image



$ docker images

Run image



$ docker run myapp

Output should be like this:

Pushing Image in Amazon ECR

Step 1. Authenticate your Docker client to the Amazon ECR registry to which you intend to push your image


 shell
$ aws ecr get-login --region region --no-include-email

Step 2. Copy and paste the docker login command into a terminal to authenticate your Docker CLI to the registry.

Step 3. Tag your image with the Amazon ECR registry, repository, and optional image tag name combination to use. The registry format is: docker tag image_id aws_account_id.dkr.ecr.region.amazonaws.com/myapp


 shell
$ docker tag image_id aws_account_id.dkr.ecr.region.amazonaws.com/myapp

(Note: You must first create a repository in ECR)

Step 4. Push the image using the docker push command: The registry format is: docker tag image_id aws_account_id.dkr.ecr.region.amazonaws.com/myapp



$ docker push aws_account_id.dkr.ecr.region.amazonaws.com/myapp

Jaira Encio Linkedin

Setting up Selenium CI/CD using AWS Codebuild and Codepipeline

Jaira Encio — Thu, 13 Jan 2022 09:29:10 +0000

In this post we will use CodeBuild and CodePipeline as a build environment for our selenium scripts located in CodeCommit repo.

We will also be using selenium in headless mode so we can run our automated tests without a visible UI shell.

File Structure


 shell
── /MyFolder/               # root folder
  ├── /app.py               # source code main test
  ├── /requirements.txt     # dependencies
  ├── /buildspec.yml        # build spec as part of the source code
  └── /install_driver.sh    # chromedriver and binary

Overview

Create source code files
Create CodeCommit Repository and push files
Create a build project in AWS CodeBuild
Create pipeline in CodePipeline and build all together

1. Create source code files

We will be creating the ff:

buildspec.yml
requirements.txt
install_driver.sh
app.py

Copy the following inside `install_driver.sh`


 sh
# Download and Install chromedriver
wget -N https://chromedriver.storage.googleapis.com/71.0.3578.80/chromedriver_linux64.zip -P ~/
unzip ~/chromedriver_linux64.zip -d ~/
rm ~/chromedriver_linux64.zip
sudo mv -f ~/chromedriver /usr/local/bin/chromedriver
sudo chown root:root /usr/local/bin/chromedriver
sudo chmod 0755 /usr/local/bin/chromedriver


# Install chrome broswer
curl -sS -o - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -
echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list
apt-get -y update
apt-get -y install google-chrome-stable

Copy the following inside `requirements.txt`


 txt
selenium==3.12.0
ipython==7.0.1

Note: I recommend to use chromedriver version between 70 and 63. You can check diff versions in here https://chromedriver.storage.googleapis.com/

Copy the following inside `app.py`



 python

from selenium import webdriver

import unittest

from time import sleep

class app_test_case(unittest.TestCase):

def setUp(self):
    chromeOptions = webdriver.ChromeOptions()
    driver_path = '/usr/local/bin/chromedriver'
    chromeOptions.add_argument('--headless')
    chromeOptions.add_argument('--disable-gpu')
    chromeOptions.add_argument('--no-sandbox')


    self.driver = webdriver.Chrome(driver_path, chrome_options=chromeOptions)
    self.driver.implicitly_wait(30)
    self.driver.maximize_window()
    path = 'https://www.facebook.com/'
    self.base_url = path

def test_i_d_e_script1(self):
    driver = self.driver
    driver.get(self.base_url)

    get_title = driver.title
    print(get_title)


def tearDown(self):
    sleep(5)
    self.driver.quit()



if name == "main":

    unittest.main()

Copy the following inside `buildspec.yml`



 yaml

version: 0.2

phases:

  install:

    commands:

       - pip install -U -r requirements.txt

       - sh install_driver.sh 

  build:

    commands:

       - python app.py

Create CodeCommit Repository and push files

Open the CodeCommit console at https://console.aws.amazon.com/codesuite/codecommit/home then click create repository
Enter Repository name and description (optional) then click create

Clone repository and push all file requirements. You can specify a certain branch but we will just be using master.

3. Create a build project in AWS CodeBuild

Open the AWS CodeBuild console at https://console.aws.amazon.com/codesuite/codebuild/home then click Create project
Fill in the following sections. Once complete, choose Create build project at the bottom of the page.

Sections:
Project configuration - Name and description
Source provider - AWS Codecommit, repo name
Environment - Ubuntu, Standard, aws/codebuild/standard:6.0
Buildspec
Batch configuration
Artifacts - none
Logs

4. Create pipeline in CodePipeline and build all together

We will now combine our process by using AWS CodePipeline to automatically pull our source code in CodeCommit and run build with AWS CodeBuild.

Open the CodePipeline console at http://console.aws.amazon.com/codesuite/codepipeline/home and choose Create Pipeline

On the Step 1: Choose pipeline settings page; in Pipeline name, enter the name for your pipeline.

Choose New service role to allow CodePipeline to create a new service role in IAM.

On the Step 2: Add source stage page; in Source provider, select AWS CodeCommit, repo name, and branch name.

On the Step 3: Add build stage page, select AWS Codebuild and project name

On the Step 4: Add deploy stage page, Choose Skip deploy stage.

On the Step 5: Review, Review all changes then click create pipeline.

Output

You should see Succeeded status after running pipeline. The build log shows from prebuild ,running command, and generating output.

Jaira Encio Linkedin

Create and Deploy Python Django Application in AWS EC2 Instance under 5 mins

Jaira Encio — Wed, 12 Jan 2022 10:19:31 +0000

Hello guys! Here is a simple step by step on how to create and deploy your own Python Django Application in AWS EC2 Instance. The goal of this is to deploy your app in the fastest way possible

Overview

Create and Launch your own EC2 instance
SSH on your EC2
Deploy packages
Run and Create App

Creating EC2 Instance

1. Login your AWS account and open EC2 Console

2. Click Launch Instance

3. Choose an Amazon Machine Image (AMI)

For this I would be selecting either Amazon Linux/Ubuntu (free tier eligible)

4. Choose an Instance Type

For this I would be selecting t2.micro (free tier eligible)

5. Skip and Proceed to Configure Security Groups

You can simply use default or configure your own security groups even later after launching your instance. You must open HTTP port 80 if you wish to check that the Nginx is successfully set up while visiting index.html. Note: You can add additional port for postgresql. this sample is just for default django.

6. Click Review and Launch

7. Review Instance Launch then click Launch

8. Create new key pair then download

Save this file as you would be needing this later.

9. Click Launch Instance

10. Navigate to Instances then check status of running instance

Connect to your Instance via SSH

1. SSH on your EC2 instance

In your terminal type the ff: % ssh -i ~/Desktop/name_of_your_keypair.pem ec2-user@ipaddress
Upon entering this, you will encounter a Warning unprotected file error. With that you need to CHMOD your pem file

2. CHMOD pem file

On your terminal type the ff: % chmod 400 ~/Desktop/umr-example-keypair.pem
then retry connecting again via ssh and you should be able to connect to your ec2 instance now.

Install Packages

Since linux ami has its own python pre installed, I did not include it in my installations. I only added pip and django
sudo apt update sudo apt-get install python3-pip sudo pip3 install gunicorn sudo apt-get install supervisor sudo pip3 install django sudo yum install nginx

Start and check status of nginx

sudo systemctl start nginx sudo systemctl status nginx

You can test this by copying the Public DNS(Ipv4) of your instance in the browser. See the index.html page of Nginx via public ip address ie http://ipadress...
You should see default page for Nginx.

Create and Run python Django App

Create project % django-admin startproject mysite

Creating project from and ec2 instance is really optional, you can always push your app in a repo then clone it inside

Edit settings.py of your django app, set ALLOWED_HOSTS to = ["*"]
Navigate to project and run app
% python3 manage.py runserver 0:8000
Copy and paste the Public DNS(Ipv4):8000 of your instance in your browser

Additional: Configuration for a production ready App

Configure and Integrate Gunicorn and Nginx Configuring both takes a whole lot of steps. I would recommend this documentations related to that:

https://pythoncircle.com/post/697/hosting-django-app-for-free-on-amazon-aws-ec2-with-gunicorn-and-nginx/

https://www.alibabacloud.com/blog/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04_594319

https://dev.to/rmiyazaki6499/deploying-a-production-ready-django-app-on-aws-1pk3#installing-dependencies

Creating an API that runs Selenium via AWS Lambda

Jaira Encio — Fri, 11 Jun 2021 15:06:00 +0000

Being an automation tester, my job is to automate everything. As I was running my test script via terminal I realised that I’m the only who can execute the scripts I made. What if someone wants to run it? like the Devs, Project Manager, etc. It would be a tedious task to clone my repo, install libraries, and run the script. So I decided that maybe I can store my test script inside a serverless machine and make it accessible via API request.

I experimented with various AWS resources such as creating my own lambda function, checking features of API gateway, Codepipeline, etc. After several attempts, I was finally able to run my script inside. And then I just researched how to access my lambda via API.

This will result in higher production and time savings. Engineers may focus on vital work because automated testing does not require human interaction. This is like a portable testing device that anyone could execute. With fast test execution, developers get testing reports in an instant, so whenever a failure occurs, they will react to it quickly. Test automation will make it easier to update programs quickly. As a result, automated testing leads to increased team responsiveness, improved user experience, and increased customer satisfaction.

Overview

Create 2 Lambda layers that has selenium and chromedriver libraries
Include created lambda layers in serverless.yml of lambda then deploy

Creating Selenium Lambda Layer

Place libraries in python/lib/python3.6/site-packages/ to include them in a layer.

Download Selenium to layer directory



$ pip3.6 install -t selenium/python/lib/python3.6/site-packages selenium==3.8.0
$ cd selenium
$ zip -r python.zip python/

Once finished, Create lambda layer then upload zip file

1. Go to AWS Console Lambda/Layers
2. Click Create Layer
3. Input the following in the layer configuration



Name: selenium
Description: Selenium layer
Upload zip file created: python.zip
Compatible runtimes: Python 3.6

4. Click Create

Note: You can user whatever version you prefer, you just need to select compatible runtime when uploading your package

Creating Chromedriver Lambda layer

Download chrome driver



$ mkdir -p chromedriver
$ cd chromedriver
$ curl -SL https://chromedriver.storage.googleapis.com/2.37/chromedriver_linux64.zip > chromedriver.zip
$ unzip chromedriver.zip
$ rm chromedriver.zip

Download chrome binary



$ curl -SL https://github.com/adieuadieu/serverless-chrome/releases/download/v1.0.0-41/stable-headless-chromium-amazonlinux-2017-03.zip > headless-chromium.zip
$ unzip headless-chromium.zip
$ rm headless-chromium.zip

Compress driver and binary



$ ls
chromedriver headless-chromium
$ zip -r chromedriver.zip chromedriver headless-chromium

Once finished, Create lambda layer then upload zip file

1. Go to AWS Console Lambda/Layers
2. Click Create Layer
3. Input the following in the layer configuration



Name: chromedriver
Description: chrome driver and binary layer
Upload zip file created: chromedriver.zip
Compatible runtimes: Python 3.6

4. Click Create

Creating Lambda Function

To ensure that your function code has access to libraries included in layers, Lambda runtimes include paths in the '/opt' directory.

File Structure


 shell
── /lambda/            # lambda function
  ├── /handler.py      # source code of lambda function 
  └── /serverless.yaml # serverless config

Code

Copy the code below to /lambda/handler.py



from selenium import webdriver
from selenium.webdriver.chrome.options import Options

def main(event, context):
    options = Options()
    options.binary_location = '/opt/headless-chromium'
    options.add_argument('--headless')
    options.add_argument('--no-sandbox')
    options.add_argument('--single-process')
    options.add_argument('--disable-dev-shm-usage')

    driver = webdriver.Chrome('/opt/chromedriver',chrome_options=options)
    driver.get('https://www.google.com/')

    driver.close();
    driver.quit();

    response = {
        "statusCode": 200,
        "body": "Selenium Headless Chrome Initialized"
    }

    return response

Copy the code below to /lambda/serverless.yaml.



service: selenium-lambda

provider:
  name: aws
  runtime: python3.6
  region: ap-southeast-2
  timeout: 900

functions:
  main:
    memorySize: 1000
    handler: handler.main
    events:
      - http:
          path: test
          method: get

    layers:
      - arn:aws:lambda:ap-southeast-2:{}:layer:chromedriver:2
      - arn:aws:lambda:ap-southeast-2:{}:layer:selenium:2

resources:
  Resources:
    ApiGatewayRestApi:
      Properties:
        BinaryMediaTypes:
          - "*/*"

Deploy Lambda Function

Go to /lambda directory



$ sls deploy

Output



Serverless: Stack update finished...
Service Information
service: selenium-lambda
stage: dev
region: ap-southeast-2
stack: selenium-lambda-dev
api keys:
  None
endpoints:
  GET - https://{name}.execute-api.ap-southeast-2.amazonaws.com/dev/test
functions:
  main: selenium-lambda-dev-main

You should get same response as below when accessing API



{
"statusCode": 200,
"body": "Selenium Headless Chrome Initialized"
}

This deployment automatically creates cloudformation stack and s3 bucket.

Deprecation note:

Since python3.6 has been deprecated, you can try using the ff packages compatible with 3.9. note that if this exceeds lambda function zip file, you can try using docker image or uploading to s3 instead.



$ python3.9 -m pip install -t python/lib/python3.9/site-packages selenium==4.5.0
$ cd selenium
$ zip -r python.zip python/

Name: selenium
Description: Selenium layer
Upload zip file created: python.zip
Compatible runtimes: Python 3.9



$ mkdir -p chromedriver
$ cd chromedriver
$ curl -SL https://chromedriver.storage.googleapis.com/107.0.5304.62/chromedriver_linux64.zip > chromedriver.zip
$ unzip chromedriver.zip
$ rm chromedriver.zip



$ curl -SL https://github.com/adieuadieu/serverless-chrome/releases/download/v1.0.0-57/stable-headless-chromium-amazonlinux-2.zip > headless-chromium.zip
$ unzip headless-chromium.zip
$ rm headless-chromium.zip

References for new releases:
chromedriver release
https://chromedriver.chromium.org/downloads

serverless-chrome release
https://github.com/adieuadieu/serverless-chrome/releases

Checkout Achim's comment on how he used 3.9 using dockerimage
https://dev.to/achimgrolimund/comment/22d99

Jaira Encio Linkedin

DEV Community: Jaira Encio

AWS for QA Testing

Topics

Importance of Cloud for QA Testers

What are some AWS tools and services for QA testers?

AWS Device Farm - Mobile/Web testing tool

Automated Testing

Remote Access

Desktop browsers

Device farm pricing

Amazon Inspector - Security testing tool

Security testing sample on EC2 Instance

Importance of Inspector

Automation with AWS Tools

Automation testing samples with AWS

Conclusion

Setting up Automated API testing with Postman Collection using Newman CLI, AWS Codebuild, CodePipeline, & S3

File Structure

Overview

1. Export Postman Collection

2. Create Buildspec.yml

3. Create CodeCommit Repository and push files

4. Create s3 bucket for report

5. Create a build project in AWS CodeBuild

6. Create pipeline in CodePipeline and build all together

Output

To generate a presigned URL using the AWS Management Console

Setting up Email Notification for EC2 instance changes using Amazon SNS and Eventbridge

Setting up SNS topic and email subscription

1. Go to AWS SNS console, and then choose Topics from the navigation pane.

2. Select Create topic.

3. Click Create topic.

4. On the Subscriptions tab, click Create subscription.

5. Click Create subscription.

6. Confirm email subscription sent to the email address you entered.

7. Go to your topic then check email status.

Setting up EC2 TerminateInstances eventbridge rule

1. Open the EventBridge console, and then click Create Rule

2. Fill up details on define rule detail then click next

3. Fill up details on Build event pattern then click next

4. Fill up select targets then click next

5. Click Create rule

Setting up Selenium in Docker Container and Pushing Image in Amazon ECR

File Structure

Code

Build and Run New Docker Image

Pushing Image in Amazon ECR

Setting up Selenium CI/CD using AWS Codebuild and Codepipeline

File Structure

1. Create source code files

Copy the following inside install_driver.sh

Copy the following inside requirements.txt

Copy the following inside app.py

Copy the following inside buildspec.yml

Create CodeCommit Repository and push files

3. Create a build project in AWS CodeBuild

4. Create pipeline in CodePipeline and build all together

Output

Create and Deploy Python Django Application in AWS EC2 Instance under 5 mins

Overview

Creating EC2 Instance

1. Login your AWS account and open EC2 Console

2. Click Launch Instance

3. Choose an Amazon Machine Image (AMI)

4. Choose an Instance Type

5. Skip and Proceed to Configure Security Groups

6. Click Review and Launch

7. Review Instance Launch then click Launch

8. Create new key pair then download

9. Click Launch Instance

10. Navigate to Instances then check status of running instance

Connect to your Instance via SSH

1. SSH on your EC2 instance

2. CHMOD pem file

Install Packages

Start and check status of nginx

Create and Run python Django App

Additional: Configuration for a production ready App

Creating an API that runs Selenium via AWS Lambda

Overview

Copy the following inside `install_driver.sh`

Copy the following inside `requirements.txt`

Copy the following inside `app.py`

Copy the following inside `buildspec.yml`