A lovely javascript testing framework -- want to contribute? join us in https://gitter.im/mochajs/contributors
'''UnhandledPromiseRejectionWarning: ElementClickInterceptedError: Element <button id="__button2" > is not clickable at point (1124,66) because another element <div id="shieldlayer-id-1600148583053-10" class="UiPopupShield"> obscures it''''
While running selenium with mocha How to fix this?
Is it possible to print a variable in an "it" statement title? For example:
describe("Get Build Version", function () {
let buildVersion;
it("Retrieve build version", function () {
buildVersion = common.getBuildVersion();
expect(buildVersion).to.not.equal('undefined');
});
it("Build Version: " + buildVersion, function () {
expect(buildVersion).to.not.equal('undefined');
});
}However, the printed buildVersion in the second "it" statement title shows as undefined, despite properly retrieving the build version. The tests pass fine, and console.log(buildVersion) shows the variable has its intended value, but still the "it" statement title shows as undefined.
How can I have it show the proper variable value?
I've changed to this code based off a solution I found online, but it still doesn't work.
describe("Get Build Version", function () {
let buildVersion;
it("Retrieve build version", function () {
buildVersion = common.getBuildVersion();
expect(buildVersion).to.not.equal(false);
});
it("Build Version: ", function () {
this.test.title = this.test.title + buildVersion;
console.log(this.test.title);
expect(buildVersion).to.not.equal(false);
});
}Even stranger is that the console.log(this.test.title); prints properly, but the test title is still reported as simply "Build Version: ". What am I doing wrong?
HI folks, I'm having trouble using beforeEach hook. A can't define a variable calling a function.
The code is:
let user;
let db;
beforeEach(async () => {
const password = generatePassword('******')
user = {
account_type: 0,
email: '*****@*****.com',
password: password,
name: 'Lukw',
last_name: 'wilkerson',
permission: 1
}
db = await model
})The error is: Error message
Causing a type error: Cannot read property 'password' of undefined
Hey all, I am struggling with getting thrown errors to output to the console. I have tests running and they just exit with no details. eg:
LocationGraphQL...
npm ERR! code ELIFECYCLE
npm ERR! errno 1There is no stack trace at all. I did set fullTrace to true. Please let me know if any more info is needed, just wondering at this point if there is perhaps a setting to force showing error output
@craigtaub the error comes from assign variables before the it and inside the describe. The beforeEach is called when and test (it) is executed, before this, the variables doesn't get setted.
I'm think in how to reuse the same variables configurations accross multiples test cases, but the mocha provides only one solution, that's is: the global setted variables using hooks is only provided on test cases, not before.
So, I will need to declared the same code on each test case.
@craigtaub Currently I'm attempt to set a callsFake method on a MongoDB native driver findOne function. There's one questio: if a function receives a param and a callback I'm just neet do do: .callsFake((params, callback) => callback(null, user));
The pattern of mongdo db native driver is error, content, so, calling the callback solves the issue, right?
Or you could test a full user interaction and add an event listener for the same even on a parent element and assert that
event.defaultPrevented is false
the code base (react-autosuggest) already uses React's Simulate.keyDown(input, { key: 'ArrowDown', keyCode: 40 }); in the other tests
i'd prefer to keep using that for consistency... hmm
@logikbyran
hi! i'm very very new to mocha. does anyone know a simple way to assert that a (keydown) event handler (inside a React component, in my case), did Not call event.preventDefault?
If your components are not using React Hooks, bypass the DOM and just call your event handler directly. I know people are going to automatically throw the "you're testing implementation details flag" but that's cargo cult and IMO BS in this case if I prefer as a developer, the public contract under test not to be webdriver or jsdom or the browser, and to be custom functions I choose to be part of my public API to test that behavior directly. Not it won't test your keydown but so what, you'll see that won't work immediately when you fire up the app. It's not a regression worth spending time requiring you to go through heavy tests just to test that wiring.
@rembeckyb_twitter I'd highly recommend not to name tests that way. Just don't, you're causing yourself more hell and people reading the tests hell and maintenance hell later on by doing so.
The point here is: Well formed tests. That means keep implementation details like technical words, function names, and worse variables out of your test names as test names should describe behavior in well written prose, not the how. That how or outcome should only be part of your test implementation details, so keep it there, not in your test names. Your test names should explain behavior, not "how" what's under test is derived. Let the assertion speak as to why or why it did not pass.
Hi all, I'm having a lot of trouble running mocha on some typescript tests on a single file.
My file structure is like this:
current_directory [
app.test.ts
nested_directory [
auth.test.ts
]
]The trouble is, when I run the command mocha --exit --require ts-node/register app.test.ts, I'm expecting it to run only the tests in app.test.ts, but somehow it's also attempting to run tests in auth.test.ts (that's weird thing #1), and those tests are failing (weird thing #2).
This is the error:
auth controller
1) "before all" hook for "can log in existing user"
2) "after all" hook for "fails to log in non-existent user"
App
express tracing might not work as /Users/cohenkarnell/selected/schoolfit/server/node_modules/express/index.js was loaded before the trace agent was initialized.
mongodb-core tracing might not work as /Users/cohenkarnell/selected/schoolfit/server/node_modules/mongodb-core/index.js was loaded before the trace agent was initialized.
(node:26674) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
Sep 30, 15:54:28:596 pm
user: unknown uid
/
✓ returns 200 when accessing an existing route that has no auth requirements (993ms)
Sep 30, 15:54:29:578 pm
user: unknown uid
/totally-fake-route-that-will-never-exist
✓ returns 404 when accessing a non-existent route (111ms)
3) "after all" hook for "returns 404 when accessing a non-existent route"
2 passing (5s)
3 failing
1) auth controller
"before all" hook for "can log in existing user":
TypeError: app_1.default is not a function
at Context.<anonymous> (controllers/auth.test.ts:21:14)
at process.topLevelDomainCallback (domain.js:126:23)
2) auth controller
"after all" hook for "fails to log in non-existent user":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/cohenkarnell/selected/schoolfit/server/app.test.ts)I have no configuration file.
I've narrowed the problem of the tests failing down to an import statement in the auth tests returning {} instead of the correct object which I don't understand, but my bigger concern is, why is it picking up the tests in the nested directory when I didn't specify --recursive??
Mocha version is 8.1.3
Hi! I'm trying to dynamically generate tests. There's a framework which calls
testFiles.forEach((file) => mocha.addFile(file));
const runPromise = new Promise<number>((resolve, _) => {
mocha.run(resolve);
});
process.exitCode = await runPromise;My test files need to await some information and then use that info to generate it() tests. Is there a way to do that without changing the framework code?
Hi gang!
Have searched in the docs but cannot seem to find a description or example of what i am trying to do. However, im pretty sure its supported as its such a trivial case.
How can i run and report on all tests while also passing arguments to the tests themselves?
Each test case requires a path to a config. I want to run and report on all configs, but then i naturally have to specify their path.
What would be the way forward with that?
Is it possible to change the port mocha allows the debugger to attach on?
mocha --debug=9228 --watch --inspect test/**/*.test.js
Debugger listening on ws://127.0.0.1:52851/49b1e489-3705-458f-b098-8912ccb4a10c
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Starting inspector on 127.0.0.1:9229 failed: address already in use
Waiting for the debugger to disconnect...
debug flags are not Mocha flags. They are Node options, which Mocha passes over to Node. The correct options are --inspect-port=[host:]port or --inspect[=[host:]port], I guess. I haven't done any testing. You can also pass these Node options via NODE_OPTIONS directly to Node.
client object explicitly, it is undefined in the after hook so I cannot disconnect it. According to SO, it's not recommended to force tests to exit, as it could reveal underlying memory issues. The unit tests have nothing to do with MQTT so far, the function I am testing just lives in the same page so I don't understand why it isn't exiting.
mocha --exit --require ts-node/register. Does anyone know how I can get it to show type errors but still run tests? Thanks for any help!
grep functionality to mark some of my tests as a specific suite (I’m not using suites itself because I already have 500+ tests and they are already structured, so I didn’t want to change anything). I’m marking some of my tests with specific markers like “@smoke”, “@mobile” etc. At this point, I have around 5 markers and the issue is that my reports started to look really ugly. What I’m trying to achieve is to edit the test names. I want to this before running the test but after grep fetched all the required tests.I’m able to get access to the
this.test.title or this.currentTest.title but no luck on actual editing the test names.The only one time it was successful in this scenario:
A
before hook inside the describe block.Inside the hook:
this.currentTest.title = ‘Name is changed!’But since the
before hook runs only once, it is changing the name of the first test in the suite only.Can someone help me to figure out at what point and how can I edit the test name. And most important to not affect the
grep functionality by doing so. (Maybe I’m taking the wrong way and I should look into after hooks...)
