A lovely javascript testing framework -- want to contribute? join us in https://gitter.im/mochajs/contributors
promise.should.be.rejectedWith(StateNotSupportedError, 'Non-supported state');
.should is still being janky for me, so I used expect())
Object.setPrototypeOf(this, StateNotSupportedError.prototype); in my error's constructor to "repair the prototype chain"
Object.setPrototypeOf(this, new.target.prototype);
sinon.restore() but that is not reseting the stubs created with that function. I have to manually reset each stub. I don't think I should have to but I could be wrong. Here is an example https://hastebin.com/kerovecawi.js
how to write mocha test that have timeout and async both
createStream need to get permission of browser's video&audio，so i have to delay this test
both createStream and destroyStream return promise
i want to test destroyStream, this just not get what i want, anyone Help?
it("my test need to be delayed, and i want to test destroyStream", function () {
setTimeout(async () => {
// i need to create stream first
const publishStream = await createStream();
expect(streamCenter.previewVideoList.length).to.equal(1);
// then destory stream
await zg.destroyStream(publishStream);
expect(streamCenter.previewVideoList.length).to.equal(0);
}, 2000); // my test need to be delayed
});
Hi Guys,
I am just getting into TDD and am really enjoying Mocha.
I am trying to setup my tests outside the /test/ folder inside my project following the naming convention File.test.js
I am struggling to get mocha to pick them up. I can point to a specific depth in my packags.json:
"test": "mocha / / *.test.js --config .mocharc.js"
But this will not pickup tests deeper.
Any ideas how I can specify this in the config, currently:
'use strict';
module.exports = {
diff: true,
extension: ['js'],
package: './package.json',
reporter: 'spec',
slow: 75,
timeout: 2000,
ui: 'bdd',
'watch-files': [' / / *.test.js'],
'watch-ignore': ['node_modules'],
recursive: true,
watch: true
};
mocha --config .mocharc.single.js and one mocha --config .mocharc.multiple.js. However each spec file starts with a login and since mocha is "chaining" them together it will not not terminate the window session after each file completes even though I feel like it should be as the browser.quit() is in the after block but doesn't get executed.
var argv = require('yargs').default(
'CURRENT_DATETIME_FOLDER',
new Date(Date.now())
.toISOString()
.replace(/\:/g, '-')
.replace(/\./g, '-')
.slice(0, -1)
).argv;
module.exports = {
bail: true,
parallel: false,
timeout: 25 * 60 * 1000, // 25 minute timeout
spec: ['dist/examples/*.js'],
reporter: 'node_modules/mochawesome',
'reporter-option': [
'reportDir=./reports/' + argv.CURRENT_DATETIME_FOLDER,
'charts=true',
'timestamp=true',
'code=true',
],
};Examples of test spec files
dist/examples/test1.js
import { pages } from '../specs-v5/mocha-hooks';
describe('User needs to sign in', () => {
it('login', async () => {
await pages.login.signInAsLocalUser();
});
it('Logic for 1', async () => {
// Logic for 1
});
});dist/examples/test2.js
import { pages } from '../specs-v5/mocha-hooks';
describe('User needs to sign in', () => {
it('login', async () => {
await pages.login.signInAsLocalUser();
});
it('Logic for 2', async () => {
// Logic for 1
});
});
after() (I don’t see it in the example) is not being called, then Mocha is getting stuck on a test somewhere. you might want to use the default reporter for now, as I think mochawesome might trap the output?
describe? I wanted to wrap it to add a prefix to the test suite title. I've found #2737 but I'm not sure where to get a reference to the running framework from a required file or root hook. It seems straight forward to add a mocha.suite.on('pre-require',... otherwise. Thanks!!
I can resolve the issue using the timeout overrides from the document, but that feels arbitrary - e.g. I am hardcoding a number of something that is meant to take an unspecified amount of time to complete. A test failure could just as well mean the timeout was not long enough as mean there is an actual code issue.
The documents listing using a "done" call to mark the run as complete, but doing this in the ways shown in documentation and people's examples online net no change in response.
It is entirely possible I am just doing something wrong here. This is a sample of a situation where I see the error:
const asyncCall = () => {
return new Promise(resolve => {
setTimeout(() => {
resolve(1);
}, 5000);
})
}
describe('defaultSettersGetters.js', function() {
it('should work', async function() {
const resp = await asyncCall();
expect(resp).to.equal(1);
});
});This fails with the "Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves." message logged.
If I update the test to pass "done" in as an argument then call it, no change
const asyncCall = () => {
return new Promise(resolve => {
setTimeout(() => {
resolve(1);
}, 5000);
})
}
describe('defaultSettersGetters.js', function() {
it('should work', async function(done) {
const resp = await asyncCall();
expect(resp).to.equal(1);
done();
});
});What silly thing am I getting wrong here?
