This is what we would do with Analytics.js tests, since we actually want to be testing the physical built file itself, we're actually a layer above Duo because we're trying to test the Duo build process, which normal module testing shouldn't concern itself with. Use `-` in filenames instead of `/` since Gist has limitations.

component.json

{
  "name": "analytics",
  "dependencies": {...}
}

index.js

module.exports = analytics;

Makefile

build: index.js
  duo index.js --global analytics > analytics.js 

test: index.js test-index.js
  duo test-index.js > test-build.js
  open test-index.html # which adds both builds via <script> tags

test-component.json

{
  "name": "analytics-tests",
  "dependencies": {
    "component/assert": "0.x"
  }
}

test-index.html

<script src="analytics.js"></script>
<script src="test-build.js"></script>

test-index.js

var analytics = window.analytics;
var assert = require('component/assert');
 
// Tests here...