austinkelleher
commented
6 years ago Hey @balzaczyy. Thanks for opening this issue. This is actually already supported by registering a custom test matcher in your marko-cli.js. marko test can take a glob pattern that tells it where it should look for tests, then you can define a custom test matcher inside your marko-cli.js to find the renderer path. Here is a working example of how to accomplish what you want:
CLI Command:
marko test ./components/**/*-test.jsmarko-cli.js in the root of your project:
const path = require('path');
module.exports = function (markoCli) {
markoCli.config.testMatcher = function (file) {
const testRegExp = /^(?:(.+?)[-.])?(?:spec|test)(?:[-.](server|browser))?[.]/i;
const basename = path.basename(file);
const testMatches = testRegExp.exec(basename);
if (!testMatches) {
// The file is not a test file
return false;
}
const componentDirectory = path.dirname(file);
const componentName = path.basename(componentDirectory); // header
// /components/header.marko
const rendererPath = `${componentDirectory}/${componentName}.marko`;
return {
groupName: testMatches[1],
env: testMatches[2] || 'browser',
componentName: componentName,
rendererPath: rendererPath
};
};
};
ironsweet
This is to extend the #6 further. In short, I'd like to use following organization of files,
I'm raising this because, per this Pro Tip, markojs seems to encourage use of single file component. So I would like to see test file along side this file too, save another folder, compared to #6.
Let's stretch it further a bit, is it possible to write test inside the single file component, and let bundler to auto-strip the test during production build.