An open API service indexing awesome lists of open source software.

https://github.com/petrbroz/forge-continuous-testing

Experimental test suite for automated testing of Autodesk Forge services.
https://github.com/petrbroz/forge-continuous-testing

autodesk-forge continuous-testing forge-model-derivative travis-ci

Last synced: 3 months ago
JSON representation

Experimental test suite for automated testing of Autodesk Forge services.

Awesome Lists containing this project

README

        

# forge-continuous-testing

> Experimental automated testing of [Autodesk Forge](https://forge.autodesk.com) services using [Travis CI](https://travis-ci.org).

| Branch | Status |
|-------------|--------|
| master | [![Build Status](https://travis-ci.org/petrbroz/forge-continuous-testing.svg?branch=master)](https://travis-ci.org/petrbroz/forge-continuous-testing) |
| tests/rvt | [![Build Status](https://travis-ci.org/petrbroz/forge-continuous-testing.svg?branch=tests%2Frvt)](https://travis-ci.org/petrbroz/forge-continuous-testing) |
| tests/iam | [![Build Status](https://travis-ci.org/petrbroz/forge-continuous-testing.svg?branch=tests%2Fiam)](https://travis-ci.org/petrbroz/forge-continuous-testing) |
| tests/dwfx | [![Build Status](https://travis-ci.org/petrbroz/forge-continuous-testing.svg?branch=tests%2Fdwfx)](https://travis-ci.org/petrbroz/forge-continuous-testing) |
| tests/nwd | [![Build Status](https://travis-ci.org/petrbroz/forge-continuous-testing.svg?branch=tests%2Fnwd)](https://travis-ci.org/petrbroz/forge-continuous-testing) |

## How To

> Note: most of the following actions can only be taken by collaborators of this github repo.
> If you're not a collaborator yet, ask the admin of this repo to be invited.

### Manually triggering a new test

Go to https://travis-ci.org/petrbroz/forge-continuous-testing, and choose the _Trigger build_ option in the _More options_ menu:

![Custom test](./docs/custom-build.png)

Find the branch you want to test, and start the test using the _Trigger custom build_ button.

> Currently we're testing different types of file formats in their own branches (so that they can run as separate builds/jobs in Travis).
> For example, the _tests/rvt_ branch configures a couple of sample Revit models in the _.travis.yml_ config file.

![Run custom test](./docs/custom-build-run.png)

### Manually restarting a test

Go to https://travis-ci.org/petrbroz/forge-continuous-testing/builds, and find the failing build/test.
On the build page you can choose to restart the entire build using the _Restart build_ button, or just
some of the build "jobs" (representing individual sample files of the tested file format):

![Restart a test](./docs/restart-build.png)

### Updating a test baseline

Follow the same steps as when manually triggering a new test, but customize the config to pass the `--update` flag
to the test script. Currently the only test available is _tests/model-derivative/basic.js_ (accepting a bucket key
and an object key as its two parameters), so the modified config would look like this:

```
script: node tests/model-derivative/basic.js $FORGE_BUCKET_KEY $FORGE_OBJECT_KEY --update
```

![Update test baseline](./docs/update-baseline.png)

### Skipping tests when updating the code

If you want to skip a build when submitting code changes, use `[skip travis]` or a [similar phrase](https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build) in your commit message.