feat: resolve rootDir

[ricardogobbosouza]

Resolves #346, #279

[mrazauskas]

For apps it might be better to set options.fixture = process.cwd() instead of options.rootDir = process.cwd(). The app is the fixture in this case. So obvious, but took me few days to understand.

If the app is at /the-app folder and options.fixture = process.cwd() is set loadNuxtConfig is called with:

testDir: /the-app/test
rootDir: /the-app
buildDir: /the-app/.nuxt/<randomID>

Seems perfect for app testing or I missed something? If I get it right loadFixture function simply overwrites anything what was set in options.rootDir. To avoid calling loadFixture one could pass options.fixture = false.

Another thing – how do we know if an app or a module is under test? It might be I found a solution. Playing with working prototype right now. Will send in a PR in few days.

[pi0]

• Value of rootDir, can be determined by searching in an array of [options.rootDir, resolve(options.testDir, options.fixture), process.cwd()]
  • We have a match if dir exists and dir/pages or dir/nuxt.config exists
  • If non of array items do match, we should throw an error asking to explicitly set options.rootDir pointing to a valid nuxt app

[mrazauskas]

What if dir/pages is found, but these are just some pages, but not Nuxt routes? Don’t get me wrong, I agree that it would be very smart to do this check. At the same time dir/pages is so generic.

Might work, of course. But in some case it will fail. Perhaps it would be helpful to console.info why the algorithm made one or another assumption. One could see what the app was trying to do and then it is easier to debug.