feat: Add e2e testing support using Ava

[vinayakkulkarni]

This PR enables users to perform E2E testing the Nuxt app using Ava test runner.

• Based on Alternative configuration files option provided by the creators of Ava.

[clarkdo]

LGTM. Only a tiny point.

[clarkdo]

I can see some dir are test and others are tests, can me keep consistency?

[vinayakkulkarni]

I can see some dir are test and others are tests, can me keep consistency?

the reason for that was the /test directory holds the actual e2e & unit tests whereas the /tests directory holds the testing setup.

it could be /test/setup where the e2e.config.js & unit.config.js could stay.. would be much cleaner.

[clarkdo]

The config file can be just in test root dir or each own test dir ?

[vinayakkulkarni]

The config file can be just in test root dir or each own test dir ?

OK, according to the Ava docs

The configuration file must be in the same directory as the package.json file.

Hence the e2e.config.js & unit.config.js were created in the root dir rather than inside the test directory.

[clarkdo]

If so, can we only reserve ava.config.js and use process.env.TEST to apply different configurations?

[vinayakkulkarni]

With dedicated config files. It'll be better to modify / update individual testing settings rather than have one huge ava.config.js with if-else checks.

Plus, that's how its recommended in Ava docs.

[clarkdo]

With dedicated config files. It'll be better to modify / update individual testing settings rather than have one huge ava.config.js with if-else checks.

Plus, that's how its recommended in Ava docs.

If so, what the point for setting TEST for each script ?

[vinayakkulkarni]

`cross-env` is required for two reasons: 1. avajs/ava#2112 2. https://github.com/vinayakkulkarni/nuxt-ava-e2e-unit-testing/blob/master/test/_setup.js Usually, the `ava.setup.js` differs for unit & e2e too.

…

On Wed, Aug 7, 2019, 11:24 PM Xin Du (Clark) ***@***.***> wrote: With dedicated config files. It'll be better to modify / update individual testing settings rather than have one huge ava.config.js with if-else checks. Plus, that's how its recommended in Ava docs. If so, what the point for setting TEST for each script ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#303?email_source=notifications&email_token=AEW4K3NTW4XKQSSYYU7FCRLQDMD5RA5CNFSM4IHMYC5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ZGWQY#issuecomment-519203651>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEW4K3LBIIQSWVY4OCHRWDLQDMD5RANCNFSM4IHMYC5A> .

[clarkdo]

Sorry for the mis-clicking, I just wondered that unit.config.js and e2e.config.js may be a little confusing since they don't indicate that they're ava related config files.

[vinayakkulkarni]

Isn't that a good thing? They could be used to setup a whole testing framework within the nuxt app if anyone wants to use it in that bifurcated way?

Maybe using jest someone wants to do unit testing and using karma they want to do e2e testing and these two files could be modified for that purpose?

[clarkdo]

This pr can be merged after resolving conflicts

[clarkdo]

Thanks!