I have converted a number of integration projects to CLI projects, using zapier convert. I’ve noticed that they use mocha for their testing framework:
{
"name": "dummy",
"version": "1.0.1",
"description": "lorem ipsum.",
"main": "index.js",
"scripts": {
"test": "mocha --recursive -t 10000"
},
"engines": {
"node": ">=v14",
"npm": ">=5.6.0"
},
"dependencies": {
"zapier-platform-core": "^7.3.0"
},
"devDependencies": {
"mocha": "^10.2.0",
"should": "^13.2.0"
},
"private": true,
"zapier": {
"convertedByCLIVersion": "12.2.0"
}
}
If I start a new CLI project, using zapier init, it uses jest as its testing framework:
{
"name": ".",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "jest --testTimeout 10000"
},
"dependencies": {
"zapier-platform-core": "14.1.1"
},
"devDependencies": {
"jest": "^26.6.3"
},
"private": true
}
Before I created the CLI project (using zapier init), I updated my version of zapier:
$ zapier -v
* CLI version: 14.1.1
* Node.js version: v20.2.0
* OS info: linux-x64
* `zapier-platform-core` dependency: 14.1.1
Did the recommended testing framework change?
In any case, it would be helpful it you included nock in the devDependencies as an easier way to help with mocking.
