OpenJS Foundation / OpenJS World 2021 - Automation

A demanding and complex Open Source Program Offices’ task is to guarantee the health of its organization repositories. Aiming to help OSPOs and OS communities, we, at Sauce Labs, created Check-My-Repo, an automated tool built upon Repolinter, that verifies the main necessary parameters to comply with OS best practices: from Readme to License. By automating this verification OSPO’s maintenance is more effective and effortless, and can help your organization to have compliant software projects easier to service, test, upgrade, and maintain. Built with Node.js, Repolinter and Vue.js, it is designed to run local and automated, displaying results on GitHub page. Just fork it and adjust it to your own configurations using a simple json file. That easy :) This talk is about the importance of such a tool, how it was designed and the benefits it brings to your organization.

A Robust, Modular UI Automation Framework with WebdriverIO - Olga Smolyar, InterSystems

Including automated UI testing as part of a DevOps pipeline has become an industry-standard practice. A variety of tools are available, both open-source and commercial, that provide APIs for simulating user interaction with a web interface. WebdriverIO has emerged as the leading javascript-based platform for functional and UI testing, providing an array of protocols, services, and BDD/TDD frameworks.
Historically, UI automation has been a brittle undertaking, requiring considerable effort to safeguard test suites against flakiness and unreliable results. WebdriverIO addresses some of the inherent instability intrinsically.
Harnessing the full power of any UI automation tool requires the use of strategies to build a robust framework on top of the interaction layer provided by its APIs. We discuss here some of these strategies in the context of a modular, flexible and robust functional testing framework built with WebdriverIO and Cucumber.

Join the speaker for live Q&A on Slack, channel - #openjs_world-automation_ci_cd
Thursday, June 3 from 12:40 - 13:00 PDT / 21:40 - 22:00 CEST
Thursday, June 3 from 13:00 - 13:20 PDT / 22:00 - 22:20 CEST

With the rise of micro services more and more project are now split between multiples repositories. As this change ease the comfort of writing code and tests the solutions it also greatly increase the number of projects and so the time needed to handle everything from configuration to maintenance. With the serverless architecture this trend is having an even greater impact on productivity. One micro service can now be split on more than 30 projects and each time you would have to update a dependence you now have to do it 30 times. But each company can easily overcome this hurdles by spending a bit of time improving their process thanks to automation. In this talk I will show you and share some feedback on how a small team can handle more than 100 serverless functions thanks to automation

The goal of DevOps has stayed the same, but our tools, infrastructure, and operating models have changed. To support modern software delivery, it’s critical for organizations to establish and share proven developer workflows. This talk will cover how existing projects are using GitHub Action with the hope that all projects despite their size can benefit collectively from knowledge sharing. The benefit of Actions is that the majority are open source. Plan to this talk leave with ideas on how you can automate new portions of your software development workflow and gain insight from open-source projects by peaking into their actions folder. To name a few, Octokit, Babel, and Next.js.

Fighting Covid with Serverless and JavaScript - David Gonzalez, NearForm

At NearForm, we built a number of Covid tracking applications but more important: we also open sourced the core. This source can be found at https://github.com/covidgreen/. In this talk, I will explain what are the major pitfalls we found along the way but also how to operate a planetary scale application with a very reduced team of people and a surprisingly low number of outages. Table of contents: - Introduction - Why Serverless - What were the biggest problems - Recommendations for running large scale geographically dispersed apps

Join the speaker for live Q&A on Slack, channel - #openjs_world-automation_ci_cd
Thursday, June 3 from 02:00 - 02:20 PDT / 11:00 - 11:20 CEST
Thursday, June 3 from 07:40 - 08:00 PDT / 16:40 - 17:00 CEST

Docker has become an increasingly important subject when we talk about containers. However, it's made to be used by humans. What if we needed containers to be controlled by other applications? Is it possible to do it by using JavaScript? In this talk, we'll build a container control application that will communicate with a container runtime through gRPC and will manage all our containers. Welcome to the new era of container management!

As we know, IoT devices are all around us. Don’t get left behind as companies around the world create competitive advantage by gathering valuable data through IoT connected devices! This module will show you what software you need and how to start building the programs that will allow you to gather and process data.We will show you some simple devices as well as sample programs that can be used to integrate those devices with business systems.

The presentation will be structured as follows: What is the problem with running your services at scale? The whole process of building, deploying, service discovery, load-balancing, routing, tracing, auth, graceful failures, rate limits, and more—is cumbersome and involves many moving parts. It is complex and nightmare for anyone running their services at scale. How does K8s help to run the services at scale? Let us explore how the K8s container management system, can simplify many of the operational challenges and it includes how to deploy NodeJS services on K8s. What is K8s and how does it work? K8s is the de facto standard for running containerized applications. K8s groups containers that make up an application into logical units for easy management and discovery. We will deep dive into how K8s is architected and how makes it easy to run services at scale.

Automated testing by a developer is still a topic that is heavily contested. Developers continue to struggle to understand how to test their apps, when to test, and how to put this all together into a continuous integration pipeline. This process can be surprisingly simple with the combination of the right tools. In this live-coding session developers will learn how to create a web-app using React. Afterward, we will shift-left by adding some automated unit tests using Jest. Next, we will shift-right by adding some functional tests using Cypress.io. Finally, the developers will learn how to continuously build and test the web app through a Github workflow. By the end of the session, the developers will: - Learn a bit about unit testing with Jest - Learn Cypress for functional testing - Put all of this together into a CI pipeline that builds and tests in a continuous manner

Although WebdriverIO is an extremely powerful and simple tool to use, most of the folks find it extremely difficult to create test framework with WebdriverIO and eventually dropout using the same. Through this presentation and the demo's, Soumya will show quick cool tweaks that you can perform on the tool to successfully build a test framework with WebdriverIO. He will show how WebdriverIO is actually a very simple tool to use. He will also talk about how you can scale thousand's of your tests in no time and perform multiple browser testing with ease with centralised reporting with Allure where you can preserve the historical information of the runs.

Developers love best practices and have strong opinions about our tools. We’re always improving our processes so we can write the most efficient and maintainable code. Our static code analysis tools are a requirement for development. All of our code is stored in revision control systems and we can’t accept updates that haven’t been unit tested. This is how we write great code. Let’s talk about writing code in a cloud environment. "Serverless" ecosystems can remove the complexity of environments, runtimes, and frameworks. Do our typical development processes change when most of our environment is abstracted away from us? I want to discuss how to maintain best practices in the cloud where there is more management and abstraction. I'll also show some new (and old) tools for development and DevOps to facilitate "serverless" development.