# beats-tester

**Repository Path**: jiemo/beats-tester

## Basic Information

- **Project Name**: beats-tester
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2017-01-08
- **Last Updated**: 2020-12-19

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# The Beats Tester

Vagrant + Ansible setup for testing the OS packages and basic e2e tests for all
the [Beats](https://www.elastic.co/products/beats)


## Execute

First, you need to bring the machines up:

    vagrant up

and make them known by name to SSH:

    vagrant ssh-config >> ~/.ssh/config

Then you can use Ansible to run the tests. Because they involve lots of VMs and
commands executed over SSH, these tests are slow (currently 15 minutes in
total). However, while creating tests or checking something quickly, you can
use different Ansible commands to execute only a subset.

Here are some execution examples:

* Test the most recent nightly builds (excluding OS X):

        make nightlies

* All tests, all platforms, a particular release:

        ansible-playbook -i hosts -e @run-settings-1.0.0-beta3.yml site.yml

* Only a particular Beat, Packetbeat in the example:

        ansible-playbook -i hosts -e @run-settings-nightly.yml --tags packetbeat site.yml

* Only a particular OS, Debian 6 amd64 in the example:

        ansible-playbook -i hosts -e @run-settings-nightly.yml --limit tester-debian6-64 site.yml