<commit_before>`web-component-tester` makes testing your web components a breeze!

You get a browser-based testing environment, configured out of the box with:

* [Mocha][mocha] as a test framework.
* [Chai][chai] assertions.
* [Async][async] to keep your sanity.
* [Lodash][lodash] (3.0) to repeat fewer things.

Additionally, WCT provides integration with `selenium`, so that you can easily 
run your test suites across multiple browsers. 


# Getting Started

There's a bit of setup necessary.

## Bower

You will need to set up WCT as a dependency of your project. Via bower:

```sh
bower install Polymer/web-component-tester --save
```

In the following examples, we assume that you've installed it in `../`, but any
location will do.


## Test Index

WCT will, by default, run tests declared in `test/index.html`. Generally, 
you'll want to use this to load all your test suites:

```html
<!doctype html>
<html>
  <head>
    <meta charset="utf-8">
    <script src="../../web-component-tester/browser.js"></script>
    <script src="../awesome.js"></script>
  </head>
  <body>
    <script>
      WCT.loadSuites([
        'awesome-tests.js',
        'awesomest-tests.html',
      ]);
    </script>
  </body>
</html>
```


## `.js` Suites

Your test suites can either be `.js` sources, which run in the context of your
text index. For example, `test/awesome-tests.js`:

```js<commit_msg>README: Add platform to index.html<commit_after>`web-component-tester` makes testing your web components a breeze!

You get a browser-based testing environment, configured out of the box with:

* [Mocha][mocha] as a test framework.
* [Chai][chai] assertions.
* [Async][async] to keep your sanity.
* [Lodash][lodash] (3.0) to repeat fewer things.

Additionally, WCT provides integration with `selenium`, so that you can easily 
run your test suites across multiple browsers. 


# Getting Started

There's a bit of setup necessary.

## Bower

You will need to set up WCT as a dependency of your project. Via bower:

```sh
bower install Polymer/web-component-tester --save
```

In the following examples, we assume that you've installed it in `../`, but any
location will do.


## Test Index

WCT will, by default, run tests declared in `test/index.html`. Generally, 
you'll want to use this to load all your test suites:

```html
<!doctype html>
<html>
  <head>
    <meta charset="utf-8">
    <script src="../../platform/platform.js"></script>
    <script src="../../web-component-tester/browser.js"></script>
    <script src="../awesome.js"></script>
  </head>
  <body>
    <script>
      WCT.loadSuites([
        'awesome-tests.js',
        'awesomest-tests.html',
      ]);
    </script>
  </body>
</html>
```


## `.js` Suites

Your test suites can either be `.js` sources, which run in the context of your
text index. For example, `test/awesome-tests.js`:

```js
{'fraction_non_alphanumeric': 0.1345480028030834, 'fraction_numerical': 0.002102312543798178, 'mean_word_length': 3.453978159126365, 'pattern_counts': {'":': 0, '<': 33, '<?xml version=': 0, '>': 33, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7331874', 'n_tokens_mistral': 951, 'n_tokens_neox': 890, 'n_words': 339}