Monorepo support about testify HOT 6 OPEN

Hey @felixjb I'm looking into this a bit and am working on the following approach

(pseudo code)

const { runnerHints, testNames } = parse(testFile)
const runner = findRunnerUp(testFile, runnerHints)
const testRoot = findPkgUp(testFile, runner.name)
runner.runTest({ cwd: testRoot, testFile, testNames })

The big difference being, the cwd of the runner command is set to the nearest package.json directory to the test file, that contains that runner. I can also work on moving runner command generation to a factory function and generalize the runTest,debugTest implementation.

from testify.

Medium: monorepo development with multi root workspaces in vsc

Extension: Monorepo to workspace config

from testify.

Hello @calebboyd !

This feature would really be a great addition to the project. The way it works today is:

• the extension looks for the test ruuner in the node_modules directory in the root of the workspace; or
• the extension looks for the test ruuner at the path you specified in the configurations;

I am trying to figure out a new method write a factory for this so it can be a little more flexible but couldn't find a way yet. I'll make this issue with help wanted

from testify.

Hey @calebboyd , thank you for picking this up.

That package.json idea is pretty cool. Maybe you could also base your implementation on how Git handles the commits in a repository, which seems similar

from testify.

Should this not work out of the box when using workspaces?

from testify.

@roggenbrot I don't know, maybe not. Some projects use a monorepo structure, some even use a framework called lerna which makes one repo have multiple package.json files

from testify.