In this session, we explored setting up Playwright, an end-to-end testing tool for simulating browser interactions and running TestBox tests. Participants learned to configure Playwright for applications, simulate user interactions to stress-test forms, and handle scenarios like taking screenshots, recording sessions, capturing Chrome dev tools traces, testing login failures, and managing broken JavaScript. The session also covered using Playwright with non-ColdBox sites, providing practical insights into enhancing testing capabilities.
This document discusses continuous delivery in an open source project. It begins with an introduction of the speaker and then discusses various tools used in the continuous delivery process like Travis CI for continuous integration. It outlines the build pipeline for the project including deploying to Bintray and updating GitHub pages. It also covers code quality tools like Codecov and promoting the project on the internet through blogs, conferences and other forums.
Java Web Start czyli jak żyć z tą dziwną technologią? & Continuous Delivery w projekcie Open Source - Marcin Stachniuk JUG Łódź
Everyone who wasn't writing JavaScript, probably is now. Atwood's Law: any application that can be written in JavaScript, will eventually be written in JavaScript. That's great, but how do we test it? In ColdFusion we have CFCs, most languages have classes... but JavaScript doesn't have classes (yet). So how do I write unit tests, what units are there, and how do I make my code look like that? JavaScript is a flexible language, and with great flexibility comes great complexity and responsibility. Take your JavaScript spaghetti and make it unit testable. Attendees should have some exposure to JavaScript, but this is for the Professional Newbie... who always needs to learn and adapt.
Everyone who wasn't writing JavaScript, probably is now. Atwood's Law: any application that can be written in JavaScript, will eventually be written in JavaScript. That's great, but how do we test it? In ColdFusion we have CFCs, most languages have classes... but JavaScript doesn't have classes (yet). So how do I write unit tests, what units are there, and how do I make my code look like that? JavaScript is a flexible language, and with great flexibility comes great complexity and responsibility. Take your JavaScript spaghetti and make it unit testable. Attendees should have some exposure to JavaScript, but this is for the Professional Newbie... who always needs to learn and adapt.
The document outlines 15 ways to optimize Spring Boot applications for the cloud. It recommends using services provided by cloud platforms for monitoring, Spring Cloud Sleuth for request tracing, Spring Boot Actuator for metrics and health checks, and circuit breakers to prevent failures from cascading. It also suggests keeping dependencies up-to-date, using Eclipse OpenJ9 to reduce memory usage, enabling zero-downtime configuration changes, and introducing chaos testing into production environments.
As a Front End Web Developer, experimenting with new tools to add to your workflow (and going down the rabbit hole with them!) is all part and parcel of refining your craft. Chris Eccles, Technical Manager at Building Blocks has been doing just this and has some invaluable insight into CSS Visual Regression using Backstop.JS. CSS Visual Regression testing is the process of running automated visual test comparisons on pages or elements in your projects. Using Backstop.JS, Chris has discovered that this tool is intuitive, allowing quick configuration to allow you to get up and rolling quickly. Backstop.JS serves your tests via a webpage which gives you the visual feedback needed for targeting bugs caused from CSS related issues. These comparisons can uncover bugs you’d otherwise not learn about until it’s too late. A very useful tool to have in your Front End arsenal, wouldn’t you agree? Chris has been sharing his insights with the BB team and wanted to share with our blog readers also. So, sit back and enjoy the ride through the wonderful world of Backstop.JS.
Andi Smith provides an overview of setting up an automated workflow for front-end development using Grunt or Gulp. They discuss choosing a task runner, common tasks for setup like concatenation and minification, tasks for development like autoprefixing and live reloading, and tasks for build like image optimization and compression. The presentation emphasizes setting up a workflow that focuses on speeding up the development process and only including necessary tasks.
The document outlines 17 ways to optimize Spring Boot applications for the cloud. Some of the key recommendations include using services provided by cloud platforms for monitoring and tracing requests. It also recommends using circuit breakers to prevent failures from cascading, keeping dependencies up-to-date, and enabling class sharing with Eclipse OpenJ9 to reduce memory usage. Continuous delivery pipelines and configuration management are also suggested for deploying changes with zero downtime.
A quick walkthrough for those of you looking for more details on Selenium Grid and how to work with cloud-based solutions…
Airware's cloud automation team returns with a year’s worth of lessons learned, and will share the challenges involved with building a full-stack test automation framework with Node.js while using the latest and greatest in JavaScript tools. Topics Async / Await - an alternative to Webdriver’s built-in control flow. Limitations with control flow. Use Babel to write the latest ES6 JavaScript syntax. Custom reporter with screenshots from Sauce Labs. Parallel tests and accurate reporting. Type-safe JavaScript with Facebook’s Flow-type library. Robust visual diffs
This document provides a step-by-step procedure to configure CRX DE Lite to your Eclipse workspace. It details the 7 steps to: 1) install the AEM Developer Tools plugin, 2) configure a Sling server and import projects from source control, 3) build projects with Maven, 4) add projects to the Sling server, 5) convert existing projects to Sling bundles and content projects, 6) initiate content syncing from CRX, and 7) debug by starting the CQ instance and Sling server in debug mode.
Recorded at the London Microservices Meetup: https://www.meetup.com/London-Microservices/ - Date: 05/08/2020 - Event page: https://www.meetup.com/London-Microservices/events/272223163/ Follow us on Twitter! https://twitter.com/LondonMicrosvc --- Services interpreted at runtime often suffer from slow startup times when components are intitialized at runtime. Ahead of time compilation allows condensing down an application by stripping down unused dependencies and pre-initializing components for a short time to first request served. This is explored by the example of GraalVM and native images. Key takeaways: - Be aware what your service contains - Approaches to improve startup time of a service - Reduction of resource requirements for a service Tobias works at Loveholidays.com as a senior software engineer extending it's microservice architecture and turning it more event-driven.
Operators are automated software managers for Kubernetes applications that extend the Kubernetes API to create, configure, and manage instances of complex stateful applications on behalf of a Kubernetes user. The Operator Framework is used to build operators which reconcile the desired state specified in a Custom Resource with the actual state of the cluster. Operators can be built using the Operator SDK and can leverage different runtimes like Go, Ansible, or Helm. Once installed, end users can create operator-managed resources like Postgres in their own namespaces through the Kubernetes API.
Learn why you should put your blackbox (or system/integration) tests into Docker Containers. Brief (remedial) overview of Docker for software testers who don't know docker, and only need to know the basics to wrap their regression tests inside of a container.
The document discusses best practices for testing Spark applications including setting up test environments for unit and integration testing Spark in both batch and streaming modes. It also covers performance testing Spark applications using Gatling, including developing a sample performance test for a word count Spark job run on Spark job server. Key steps for testing, code coverage, continuous integration and analyzing performance test results are provided.
Annotated slides for phpCE workshop on November 3, 2017. Workshop repository: https://github.com/OndraM/selenium-workshop-phpce The workshop covered: - setting up local development environment (using Docker) - practical examples of functional tests implementation - exploring possibilities of Selenium WebDriver - parallel test execution using Steward - hands-on Page Object design pattern - dealing with asynchronous elements of web-pages (AJAX, JavaScript) - general tips & tricks how to keep a maintainable suite of functional tests in a long-term
Angular grew significantly in the past few years from both a tooling and developer experience standpoint. This talk will explore many of the features and newer improvements in the pipeline that allow anyone to build and deploy performant apps with very little overhead. Through real demos and examples, we’ll cover Ivy, bundle budgeting, differential serving, automatic code-splitting, and progressive rehydration of SSR elements. In the second part of the talk, we’ll focus on how to efficiently prefetch and preload different modules and components.
Sami provided a beginner-friendly introduction to Amazon Web Services (AWS), covering essential terms, products, and services for cloud deployment. Participants explored AWS' latest Gen AI offerings, making it accessible for those starting their cloud journey or integrating AI into coding practices.