Posts Tagged ‘AmyKapernick’
[NDCMelbourne2025] Front End Testing with GitHub Actions – Amy Kapernick
In a dynamic session at NDC Melbourne 2025, Amy Kapernick, a seasoned front-end developer and advocate for automation, unveils a streamlined approach to front-end testing using GitHub Actions. With a focus on practicality, Amy guides developers through constructing a robust continuous integration and continuous deployment (CI/CD) pipeline, ensuring that front-end tests run seamlessly against live websites. Her presentation underscores the necessity of automation to maintain quality in web development, offering actionable insights for teams seeking to integrate testing into their workflows without manual intervention.
The Imperative of Front-End Testing
Amy begins by highlighting the unique challenges of front-end testing, emphasizing that unlike unit tests, which can operate with dummy data, front-end tests require a live, functioning website to evaluate real-world performance. For instance, assessing accessibility for visually impaired users or determining page load speeds demands an environment that mirrors production. Amy illustrates this with a CSS code snippet, questioning whether it can reveal unintended style bleed or performance bottlenecks without a live interface. By advocating for environments as close to production as possible, she ensures that tests yield accurate, actionable results, setting the stage for automation to eliminate manual testing inconsistencies.
Automating with GitHub Actions
The core of Amy’s approach lies in leveraging GitHub Actions to automate front-end testing within a CI/CD pipeline. She explains that GitHub Actions’ workflows, defined in YAML files, enable developers to trigger tests on specific events, such as pull requests to a production branch. Amy walks through creating a workflow with jobs like “build” and “test,” detailing steps such as checking out repository code, setting up Node.js, and installing dependencies. By using existing GitHub Actions packages, like those for checking out code and configuring Node, she simplifies the process, ensuring tests run consistently without manual effort. This automation, Amy notes, prevents code merges that fail tests, safeguarding application quality.
Deploying and Testing Live Websites
A pivotal aspect of Amy’s workflow involves deploying a live website for testing, using Netlify for its ease and deploy preview capabilities. She demonstrates a custom bash script to deploy to Netlify, addressing challenges like handling sensitive data, such as site IDs, which GitHub Actions may flag as secrets. Amy ingeniously encodes the deployment URL to bypass security restrictions, decoding it for testing with tools like Lighthouse and Playwright. These tools provide comprehensive reports on performance and UI functionality, respectively, which Amy configures to upload as artifacts, ensuring developers can review results and address issues before merging code.
Enhancing Workflows with Additional Automation
Beyond testing, Amy showcases GitHub Actions’ versatility by integrating a package that converts code comments into GitHub issues, ensuring tasks like “fix later” are tracked. This automation assigns issues to the code’s author and auto-closes them when resolved, streamlining project management. Amy also touches on other uses, such as linting, checking broken links, and generating assets like static tweet images for blog posts. These examples highlight how GitHub Actions can extend beyond testing to enhance overall development efficiency, making it a powerful tool for modern workflows.
Links:
[NDCOslo2024] Accessibility by Everyone (and for Everyone) – Amy Kapernick
In an epoch where digital dominion dictates daily discourse, Amy Kapernick, a foremost accessibility advocate and consultant, issues an imperative: inclusivity as imperative, not afterthought. With a crusade rooted in user experience and universal design, Amy exposes the exclusions etched into everyday interfaces, advocating for architectures that accommodate all, from the able-bodied to the impaired. Her discourse, dynamic with demonstrations and data, democratizes accessibility, declaring it a collective charge that enriches existence universally.
Amy acknowledges her last-minute logistics—audio absent, yet ardor undimmed—yet plunges into profundity: technology’s ubiquity underscores urgency, as 1.2 billion with disabilities confront barriers baked into bytes. She shatters stereotypes: accessibility aids all—temporary tribulations like fractured limbs or fractured focus benefit from barrier-free builds.
Universal Usability: Beyond Barriers to Broader Benefits
Accessibility, Amy avows, amplifies agency: screen readers summon sightless surfers to seas of content, captions convey clarity amid clamor, alt text unveils visuals to the visionless. Her hierarchy of harmony: POUR principles—Perceivable, Operable, Understandable, Robust—guide guardians toward grandeur.
Amy animates with audits: color contrasts calibrated for chromatic challenges, keyboard cascades for motor maladies, semantic structures for scanner scrutiny. Overlays, she ostracizes: ostensible panaceas that exacerbate, overriding user overrides and inviting incursions.
Collective Custodianship: Crafting Change Collaboratively
Everyone, Amy emphasizes, owns obligation: developers discern deficits, designers dream diversely, managers mandate metrics. Her mosaic: small strides—semantic tags, focus indicators—sum to seismic shifts, serving seniors, multitaskers, multilinguals.
Resources ripple: her repository at capesa11y.com, a cornucopia of checklists and courses, catalyzes competence. Amy’s axiom: inaccessibility isolates, accessibility integrates—elevating equity in an equitable ether.