var selftest = require('../tool-testing/selftest.js');
import { getUrl } from '../utils/http-helpers.js';
var Sandbox = selftest.Sandbox;
var MONGO_LISTENING =
{ stdout: " [initandlisten] waiting for connections on port" };
async function startRun(sandbox) {
var run = sandbox.run();
run.waitSecs(90); // Running from checkout can take a _long_ time
await run.match("myapp");
await run.match("proxy");
await run.tellMongo(MONGO_LISTENING);
// Since the "=> Started MongoDB" message can appear after the
// "Attributes on are not supported" message, we should not
// enforce the opposite order here:
// await run.match("MongoDB");
return run;
};
// Test that the static-html package works. It's hard to do this from a unit
// test.
selftest.define("static-html - add static content to head and body", async () => {
const s = new Sandbox({ fakeMongo: true });
await s.init();
await s.createApp('myapp', 'compiler-plugin-static-html');
s.cd('myapp');
const run = await startRun(s);
// Test that static content is present in HTML response.
const html = await getUrl('http://localhost:3000/');
selftest.expectTrue(
html.indexOf(
``
) !== -1
);
selftest.expectTrue(
html.indexOf(
`I have a body, yet no Blaze!
`
) !== -1
);
await run.stop();
});
// Test that the static-html package throws the right error
selftest.define("static-html - throws error", async () => {
const s = new Sandbox({ fakeMongo: true });
await s.init();
await s.createApp('myapp', 'compiler-plugin-static-html-error');
s.cd('myapp');
const run = await startRun(s);
await run.match("Attributes on not supported");
run.waitSecs(30);
await run.stop();
});