Ir al contenido principal

Testing a simple web application using Docker and Galen

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed.

Steps

  • Pre-reqs
    • Have node.js installed (For using galen without docker)
    • Have Java installed (For using galen without docker)
    • And docker installed
  • Create tests using galen
  • Create docker container for the galen-cli container
  • Build, Run and experiment with your new containers

Create a Dockerfile for the galen-cli container

  • Include clean ubuntu container
    • FROM ubuntu
  • Create default/working directory
    • WORKDIR /workdir
  • Install Java
    • RUN apt-get update && \
          apt-get install -y curl && \
          apt-get install -y software-properties-common && \
          add-apt-repository ppa:openjdk-r/ppa && \
          apt-get update && \
          apt-get install -y openjdk-8-jdk && \
          rm -rf /var/lib/apt/lists/* && \
          rm -rf /var/cache/oracle-jdk8-installer
  • Install Node.js
    • RUN curl -sL https://deb.nodesource.com/setup_8.x | bash - && \
          apt-get install -y nodejs
  • Install Galen framework
    • RUN npm install -g galenframework-cli --unsafe-perm=true
  • Declare the entrypoint
    • ENTRYPOINT ["galen"]
  • Add default parameters to be passed to the galen framework
    • CMD ["--help"]

Build & Run

  • Install Galen locally
    • npm install -g galenframework-cli
  • Run Galen locally
    • galen test tests/ --htmlreport reports
  • Build the container
    • docker build -t galenframework .
  • Run the container
    • docker run -it galenframework
  • Run the container against Browser Stack
    • docker run -v $(pwd):/workdir -it galenframework test tests/ --htmlreport reports -Dgalen.browserFactory.selenium.runInGrid=true -Dgalen.browserFactory.selenium.grid.url=http://USERNAME:ACCESSKEY@hub.browserstack.com/wd/hub
  • Run the container against Sauce Labs
    • docker run -v $(pwd):/workdir -it galenframework test tests/ --htmlreport reports -Dgalen.browserFactory.selenium.runInGrid=true -Dgalen.browserFactory.selenium.grid.url=http://USERNAME:ACCESSKEY@ondemand.saucelabs.com/wd/hub

Resources

Comentarios

Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

How to create an AEM component using Reactjs

In this tutorial, I will show how to use use Adobe's archetype to create an AEM application with React.js support and also how to add a new React.js component so that it can be added into a page, above is the vid and below you will find some useful notes. In the second part we will see how to configure the Sling Model for the AEM React component. 1. Pre-reqs Have access to an Adobe Experience Manager instance. You will need aem 6.4 Service Pack 2 or newer. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2.

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name