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

wct-teamcity-reporter

v1.0.1

Published

WCT plugin to enable test reporting in TeamCity.

Downloads

5

Readme

#wct-teamcity-reporter

###WCT plugin to enable test reporting in TeamCity.

Uses TeamCity Service messages described in TeamCity Documentation

The plugin produces messages for testStarted, testFinished, testFailed and testIgnored events.

The test names used are formatted as suite.testname.browserName+browserVersion. For example test_suite.passing.chrome40

##Installing

npm install wct-teamcity-reporter

After installation, run wct with the plugin enabled: wct --plugin teamcity-reporter

or you can also enable it in your wct.conf.js

module.exports = {
  plugins: {
    local: {
      browsers: ['chrome']
    },
    sauce: false,
    'teamcity-reporter': true
  }
};

##Testing

You can test the plugin manually by running tests for test/index.html with wct

Before that you need to install webcomponentsjs with bower install webcomponentjs

Then, install the local version of the plugin with

npm pack
npm install wct-teamcity-reporter-1.0.0.tgz

And then run the tests with wct

Running tests will produce an output like this:

Starting Selenium server for local browsers
Selenium server running on port 54761
Web server running on port 54767 and serving from /Users/Saulis/Dev
chrome 40                Beginning tests via http://localhost:54767/wct-teamcity-reporter/test/index.html?cli_browser_id=0
##teamcity[testStarted name='test_suite.passing.chrome40']
##teamcity[testFinished name='test_suite.passing.chrome40' duration='0']
##teamcity[testStarted name='test_suite.failing.chrome40']
chrome 40                ✖ index.html » test suite » failing

  assert.fail()
    <unknown> at   Context.<anonymous> at /wct-teamcity-reporter/test/index.html:17:0

##teamcity[testFailed name='test_suite.failing.chrome40' message='assert.fail()' details='assert.fail()|n  Context.<anonymous> at /wct-teamcity-reporter/test/index.html:17']
##teamcity[testFinished name='test_suite.failing.chrome40' duration='0']
##teamcity[testIgnored name='test_suite.ignored.chrome40']
chrome 40                Tests failed: 1 failed tests
Test run ended in failure: 1 failed tests

chrome 40 (1/1/1)


1 failed tests