File: Testing.md

package info (click to toggle)
firefox 147.0.2-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,683,484 kB
  • sloc: cpp: 7,607,246; javascript: 6,533,185; ansic: 3,775,227; python: 1,415,393; xml: 634,561; asm: 438,951; java: 186,241; sh: 62,752; makefile: 18,079; objc: 13,092; perl: 12,808; yacc: 4,583; cs: 3,846; pascal: 3,448; lex: 1,720; ruby: 1,003; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10; exp: 6
file content (29 lines) | stat: -rw-r--r-- 988 bytes parent folder | download | duplicates (15) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
 
# Testing

Speedometer uses [Selenium](https://www.selenium.dev/) for testing of the application itself.
Tests are located in the `/tests` folder.

[Sinon](https://sinonjs.org/): Standalone test spies, stubs and mocks for JavaScript.
[Mocha](https://mochajs.org/): Testing framework.

## Local Testing

To run this locally you'll need the browsers installed along with the corresponding driver:

-   [chromedriver](https://chromedriver.chromium.org/getting-started)
-   [geckodriver](https://github.com/mozilla/geckodriver/releases)
-   [safaridriver](https://developer.apple.com/documentation/webkit/testing_with_webdriver_in_safari)
-   [msedgedriver](https://developer.microsoft.com/microsoft-edge/tools/webdriver).

Once installed you can run the following scripts:

```bash
npm run test:chrome
npm run test:firefox
npm run test:safari
npm run test:edge
```

## Automated Testing

Currently Speedometer's tests run automatically, when pushing to the main branch or when opening a pr.