npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

playwright-feature-reporter

v1.3.0

Published

Custom Playwright reporter that generates a Markdown file documenting app features based on test cases

Downloads

271

Readme

playwright-feature-reporter

Custom Playwright reporter for self-documenting via tests. Populates a Markdown file documenting app features based on test cases.

(the below features and to-do sections are auto-generated from the reporter's test cases)

Installation

npm i -D playwright-feature-reporter

Features

Markdown generation

  • :white_check_mark: Supports nested describe blocks
  • :white_check_mark: Marks passing, failing and skipped tests
  • :white_check_mark: Supports comment annotations
  • :white_check_mark: Supports test-type annotations, and doesn't report non-behavioral tests
  • :white_check_mark: Supports embedding markdown in an existing file between placeholders
  • :white_check_mark: Supports embedding markdown in an existing file without closing placeholder
  • :white_check_mark: Merges features from across suites

Configuration

  • :white_check_mark: Define output file with 'outputFile' option (Implicitly tested)

To do

  • :construction: Supports embedding different test types in different parts of the document
  • :construction: Display generation date
  • :construction: Support custom emojis
  • :construction: Support including a link to a full test report

Usage

Basic usage

Include as a reporter in your playwright.config.ts. eg:

export default defineConfig({
  reporter: [
    ['list'],
    ['playwright-feature-reporter', {  outputFile: '../FEATURES.md' }]
  ],

Annotating tests

You can annotate tests with the following annotations:

  • test-type: Used to annotate the type of test. Only tests with a test-type of behavior will be reported. Tests without the test-type annotation will be assumed to be behavior tests.
  • comment: Used to add a comment to a test. The comment will appear in parentheses after the test name.

Example:

test('Example of a test with a comment', 
  {annotation: [{type: 'comment', description: 'This is an example comment'}]}, () => {
});

test('Example of a test with a test-type annotation', 
  {annotation: [{type: 'test-type', description: 'behavior'}]}, () => {
});

You can also similarly annotate a describe block. All tests within the describe block will inherit the annotation.

test.describe('Compatibility tests', 
  {annotation: [{type: 'test-type', description: 'compatibility'}]}, () => {
    test('this test will be annotated with "compatibility"', () => {
    });
});

Appending to an existing file

If you want to append the results to an existing file, include the following prefix in the file:

<!-- playwright-feature-reporter--start -->

You can additionally include a closing placeholder:

<!-- playwright-feature-reporter--end -->

For example:

# Features
<!-- playwright-feature-reporter--start -->
<< your features will be rendered here >>