testerbot

Automatic Front-End Testing

Purpose

During development, there isn't enough time to write tests, so our only option is manual testing! We don't need a reminder of how inefficient, time-consuming, error-prone and boring that can get! When we get around to writing test-automations, we spend a lot of time writing tests from scratch. However, most of the test-cases for testing web-applications can be automated and reused.

We created Testerbot to automatically test web-applications during the development process via Puppeteer which talks to Google Chrome Headless Browser.

The basic framework is ready and we have implemented a few test-cases, but we need help in adding more reusable test-cases.

Note: I started this project several months ago and built a SaaS product, but realized that an open-source test automation package will help catch issues quickly during development. I recently stumbled upon https://frontendchecklist.io/ and created github issues to automate as many of those tests as possible into Testerbot.

Install

npm i testerbot -D

Usage

Quick-Start

# Without any arguments, we default to http://localhost:3000
testerbot 

# Specify a url via --url
testerbot --url http://localhost:5000

# Specify multiple comma seoparated urls via --url
testerbot --urls http://localhost:5000,http://localhost:5000/toc.html

Testerbot Configuration

You can also run Testerbot by providing a configuration file which allows you to skip specific tests or run only specific tests.

By default, it will look for testerbot.config.js in your project root:

// Testerbot Run Configuration

module.exports = [{
  url:
    'http://localhost:5000',

  tests: {
  
    // Test name(s) go here
    // These tests will be skipped
    skip: [
      'Open Graph'
    ],

    // Test name(s) go here
    // These are the only tests to be run
    filter: [
      'Viewport' 
    ]
  }
}]

You may also specify a path to the config file via:

testerbot --config ./config/testerbot.config.js

Basic Features

• A comprehensive set of pre-defined test cases
• Support for multiple URL's in a test run
• Ability to skip tests or run only specific tests
• Integrated dashboard
• Platform and language agnostic
• Ability to run in CI build process

Todo: Advanced Features

[ ] Authentication

[ ] Custom Scenarios (workflows)

[ ] Tags

[ ] Custom Reporter

[ ] Automatic Crawling

[ ] Filling Forms

Contribution

This is a work-in-progress and we would like your help. Please consider contributing to this project on one of the following:

• Framework Improvements

• Dashboard Improvements

• Test Cases

• Provide User Feedack / Bug Reports

License

MIT License