Skip to main content
100%

running simpletests

✓ Published0🌍 Public
Aalexfinnarn
Last edited Aug 21, 2018
Created on Aug 21, 2018

This visualization shows the execution of Backdrop CMS’s SimpleTest suite through a shell script. It demonstrates how the script enables the Testing module via Drush, then runs tests using PHP’s `run-tests.sh` against a local server URL, passing specific test classes from the environment variable `SIMPLETEST_CLASSES`. The code relies on Drush’s `en` command and the PHP CLI, with no graphical rendering or data-binding libraries present. The output is purely a terminal-driven test run, not a chart or interactive graphic.

AI-generated description

Similar vizzes

Loading thumbnail…

running some drush commands

This example shows a shell script that automates the setup and management of a Backdrop CMS site using Drush commands. It demonstrates the sequence of installing the site with a MySQL database, starting a local development server, and enabling a specified module. The code relies on the Drush command-line interface, invoking `drush si`, `drush backdrop-runserver`, and `drush en` with flags for database configuration and non-interactive execution. The script uses environment variables for the module name and targets a localhost port, with output redirected to suppress server logs.

Aalexfinnarn
72% match
Loading thumbnail…

new travis file for Backdrop testing template

This example shows a Travis CI configuration file that automates testing for a Backdrop CMS module. It defines a PHP 7.1 build environment with MySQL services, restricts branches to the 1.x-1.x branch, and enables Sauce Connect for browser testing. The script section runs Behat tests with headless and JavaScript tag filters, followed by SimpleTest classes, using shell scripts like `build-code.sh`, `setup-config.sh`, and `install-backdrop.sh`. It caches Composer dependencies and uses environment variables to manage module dependencies and test parameters.

Aalexfinnarn
66% match
Loading thumbnail…

install codebase

The visualization shows the sequence of shell commands used to install a Backdrop codebase, from cloning the core repository to enabling contrib modules. It maps the command structure through a nested tree layout, likely rendered with D3’s hierarchical layout and `d3.forceSimulation` for positioning. The code explicitly calls `git clone` for Backdrop and each contrib module, then runs `drush en` via the Composer-installed Drush binary, revealing the dependency chain between repository downloads and module activation. The rendering approach follows the script’s execution order, with branching for the module loop.

Aalexfinnarn
65% match
Loading thumbnail…

Showing how much better Gists look than Medium code blocks.

This example highlights the visual superiority of GitHub Gists over Medium’s code blocks by presenting a shell script that conditionally runs Behat tests. The code checks whether a Travis CI push event or a JavaScript commit triggers the test suite, using environment variables and the Behat testing framework. The gist’s clean syntax highlighting and line numbering make the conditional logic immediately readable, whereas Medium’s plain styling obscures the script’s flow. It demonstrates how gist embeds preserve code clarity for technical audiences.

Aalexfinnarn
59% match
Loading thumbnail…

Gist 653d17f45fc4a94d6a52

This example catalogs browser-based testing and frontend performance tools, organizing them by category: visual regression, CSS testing, performance measurement, monkey testing, and general testing frameworks. It lists concrete libraries such as Wraith, PhantomCSS, Phantomas, browser-perf, perfjankie, gremlins.js, and DalekJS, with links to their documentation and related articles. The collection highlights both established tools and emerging practices, including telemetry-based benchmarks from Topcoat and Chromium. The page itself is a simple markdown file with hyperlinks, serving as a curated resource rather than an interactive visualization.

Aalessioalex
58% match
Loading thumbnail…

example travis file

This example shows a Travis CI configuration file for automated testing of a PHP-based Drupal module, using YAML syntax to define the build pipeline. It specifies the PHP version, branches, and services like MySQL, while enabling Sauce Connect for browser testing. The script stages orchestrate installation, setup, and execution of Behat and SimpleTest suites, relying on shell commands and cached dependencies in `$HOME/.composer/cache` to speed up builds.

Aalexfinnarn
57% match
Loading thumbnail…

Gist 93f2b4ad88451cab624a50ea0da1d8dc

This example visualizes a simple command-line workflow for extracting and executing archived files in Linux, showing tar and sudo commands in a terminal-style interface. The visualization uses D3.js to render the text output, likely employing `d3.select` and `d3.text` to load and display the command results. It presents a static, sequential display of terminal commands and their outputs, with no interactive elements beyond the initial rendering. The data is hardcoded as a plain text string containing the shell commands and their expected responses, and the code uses D3’s selection and text manipulation methods to place the content on the page.

MMistyBlunch
55% match
Loading thumbnail…

Gist 290788

This example visualizes the output of a Node.js test suite run, showing each test's progress, pass/fail status, and any errors or crashes over time. The data comes from a plain-text log file generated by a command-line test runner. The visualization uses D3.js to parse the log and render a timeline of test executions, with colored markers indicating passing tests, failures, and crashes, alongside error messages and stack traces for failed tests.

XXXX
54% match