You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed nightwatch 2.5 globally and ran npm init nightwatch
I selected to use the Nightwatch test runner and create a TypeScript project with Chrome as my browser.
When I ran npm run test I noticed I was getting .title is deprecated warnings which led me to notice the scaffolder created
and the top of github.ts it has the old version of the test which does not appear to match what is in create-nightwatch currently in the /asserts/ts-examples dir
// outdatedconsthome: NightwatchTests={'Github Title test': ()=>{browser.url('https://github.com').assert.title('GitHub: Where the world builds software · GitHub');},
// what should be there according to what is on https://github.com/nightwatchjs/create-nightwatch/tree/main/assets/ts-examplesconsthome: NightwatchTests={'Github Title test': ()=>{browser.url('https://github.com').assert.titleEquals('GitHub: Where the world builds software · GitHub');},
Is nightwatch using an old version of create-nightwatch for scaffolding?
The text was updated successfully, but these errors were encountered:
Fixed by using npm init nightwatch@latest instead of npm init nightwatch so init was using a cached version. I thought it would be tied to the version of Nightwatch, the latest as of writing (2.5), installed on the computer.
I installed nightwatch 2.5 globally and ran
npm init nightwatch
I selected to use the Nightwatch test runner and create a TypeScript project with Chrome as my browser.
When I ran
npm run test
I noticed I was getting .title is deprecated warnings which led me to notice the scaffolder createdand the top of github.ts it has the old version of the test which does not appear to match what is in create-nightwatch currently in the
/asserts/ts-examples
dirIs nightwatch using an old version of create-nightwatch for scaffolding?
The text was updated successfully, but these errors were encountered: