Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Travis CI regression test support #604

Merged
merged 2 commits into from
Jul 26, 2016
Merged

Add Travis CI regression test support #604

merged 2 commits into from
Jul 26, 2016

Conversation

hollie
Copy link
Owner

@hollie hollie commented Jul 12, 2016

This pull request adds the required files to run a basic regression test on the MisterHouse code using Travis.

All control is in the .travis.yml file in the root of the repository.

Every time somebody commits code, a new build is triggered on Travis.

The test code that is executed is:

mh -code_dir code/test

With the current code that is present in that folder, MisterHouse is started, runs for one minute and then exits.

Results are here: https://travis-ci.org/hollie/misterhouse/builds

Rationale:

  • to offer a framework that allows automatic code verification for new pull requests
  • to speed up acceptance of new pull requests that pass the tests

Note:

  • I had to change the exit code of MisterHouse to '0' for an intended exit (so that the test can stop at a certain point in time). That exit code used to be 1, and I changed both the exit code and the loop code that checks the exit code. We need to check if there are other uses of the exit code '1' that could be broken by this change
  • More test code needs to be added to the code/test/ folder. E.g. performing a basic check if the web interface is up, adding specific test code for modules, ...

So: this is a start, I hope we can expand it to cover larger parts of the MisterHouse code.

This pull request adds the required files to run a basic regression test on the MisterHouse code using Travis.

All control is in the `.travis.yml` file in the root of the repository.

Every time somebody commits code, a new build is triggered on Travis.

The test code that is executed is:
```
mh -code_dir code/test
```

With the current code that is present in that folder, MisterHouse is started, runs for one minute and then exits.

Results are here: https://travis-ci.org/hollie/misterhouse/builds

Rationale:
 * to offer a framework that allows automatic code verification for new pull requests
 * to speed up acceptance of new pull requests that pass the tests

Note:
 * I had to change the exit code of MisterHouse to '0' for an intended exit (so that the test can stop at a certain point in time). That exit code used to be 1, and I changed both the exit code and the loop code that checks the exit code. We need to check if there are other uses of the exit code '1' that could be broken by this change
 * More test code needs to be added to the `code/test/` folder. E.g. performing a basic check if the web interface is up, adding specific test code for modules, ...

So: this is a start, I hope we can expand it to cover larger parts of the MisterHouse code.
Added all stable releases and 5.08 on request of Howard.
@hollie hollie merged commit f7e97cf into master Jul 26, 2016
@hollie hollie deleted the add_travis_support branch January 8, 2017 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant