Report browser settings like whatsmybrowser.org.
execute client side tests from browser report back to cli
TypeScript definitions for browser-report
Run tests in the browser, report results in Node
execute client side tests from browser report back to cli
Easily measure performance metrics in JavaScript
Better terminal and file output for cypress test logs.
Info about your dev environment for debugging purposes
Base reporting library for istanbul
Implements https://w3c.github.io/accname/
TypeScript definitions for istanbul-lib-report
HTML5 backend for React DnD
ProseMirror's view component
Allure JS Commons
Generates gorgeous HTML reports from mochawesome reporter.
Reporters for the Jasmine BDD Framework
Allure Vitest integration
Library for reporting click, conversion and view metrics using the Algolia Insights API
A pure and powerful JavaScript Bitcoin library.
Merge several Mochawesome JSON reports
Merges multiple JUnit XML reports into one.
This POC shows how browser crashes could potentially be detected.
The json schema for a mutation testing report.
Measure Visually Complete metrics in real time
Rails engine providing intuitive user interface for constructing simple database queries by end users with no SQL knowledge.
Profile a Ruby on Rails application in your browser and reports detailed metrics to profileit.io.
Run headless browser checks against a URL using Playwright and receive a structured, immutable Ruby report object — framework-agnostic, no persistence.
browsable audits a Rails application's CSS, HTML, ERB, and JavaScript and reports which browsers can actually render and run it, then compares that against the project's declared allow_browser policy. It is a thin Ruby orchestrator over best-in-class external tools (Herb, stylelint, eslint).
Hooks into RSpec and makes browser screenshots in all js-feature specs. It works, by hooking into Capybara's click_on, click_button, etc. methods and will make a screenshot before and after each click. After all tests run, it will generate a report page, default under public/screenshot_overview (which can conveniently be viewed through the dev server: http://localhost:3000/screenshot_overview/).
Bidi2pdf is a powerful PDF generation tool that uses Chrome's BiDirectional Protocol to render web pages as high-quality PDF documents. It offers: * Command-line interface for easy PDF generation * Support for cookies, headers, and basic authentication * Waiting conditions (window loaded, network idle) * Headless Chrome operation for server environments * Docker compatibility * Customizable PDF output options Bidi2pdf uses ChromeDriver to control Chrome through its BiDi protocol, providing precise rendering for reports, invoices, documentation, and other PDF documents from web-based content. It automatically manages the ChromeDriver binary and browser sessions for a seamless experience.
== DESCRIPTION: websitary (formerly known as websitiary with an extra "i") monitors webpages, rss feeds, podcasts etc. It reuses other programs (w3m, diff etc.) to do most of the actual work. By default, it works on an ASCII basis, i.e. with the output of text-based webbrowsers like w3m (or lynx, links etc.) as the output can easily be post-processed. It can also work with HTML and highlight new items. This script was originally planned as a ruby-based websec replacement. By default, this script will use w3m to dump HTML pages and then run diff over the current page and the previous backup. Some pages are better viewed with lynx or links. Downloaded documents (HTML or ASCII) can be post-processed (e.g., filtered through some ruby block that extracts elements via hpricot and the like). Please see the configuration options below to find out how to change this globally or for a single source. This user manual is also available as PDF[http://websitiary.rubyforge.org/websitary.pdf]. == FEATURES/PROBLEMS: * Handle webpages, rss feeds (optionally save attachments in podcasts etc.) * Compare webpages with previous backups * Display differences between the current version and the backup * Provide hooks to post-process the downloaded documents and the diff * Display a one-page report summarizing all news * Automatically open the report in your favourite web-browser * Experimental: Download webpages on defined intervalls and generate incremental diffs.
QA Robusta is an automation framework easing pain points away from automation test case writers. How is pain relieved? * Elements, such as links, buttons, and other html objects are defined in one location. This ensures over time the user won't have definitions spread out throughout different layers of code requiring time consuming updates if the application under test is modified. * Well defined flows allows the user to have a common means for navigating and controlling interactions with the application under test. This takes all logic out of test classes and yields in higher more modular code re-use. * When an application requiring testing has the elements and flows implemented less code savy resources can easily add new test cases once trained on how to access the flows and elements. * When ever a link or button is clicked a screen shot is taken * Results are available under site/results directory in html format. Report includes the rdoc on a per test class method along with any screen shots taken. Example report: https://cyberconnect.biz/opensource/demo_results.html * Transparent remote Unix command execution leading to well defined interfaces for common task. For example, one may have a class defined specifically for RemoteUnixNetwork. This class would have methods such as, assign_ip, ifup, ifdown, etc. This class then would be able to perform these task on any remote Unix machine. * Executes the same on Windows or Linux/Unix environments. Developers have the freedom to develop on the platform of choice. * Mechanize extension: Allows the user to define a web application's page elements in a YAML format and provide navigation paths accessing the YAML structure to interact with the web application. Users can also perform direct http.post or any other mechanize functionality when defining state-full interfaces to hit a web application without going through a browser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.