mocha.js

问题 I am currently facing some problems getting my tests to debug properly with VSCode in Vue.js (I am using Mocha and Webpack) The first configuration I found which got me a bit closer was this one. Configuration in .vscode/launch.json { "type": "node", "request": "launch", "name": "Unit Tests", "program": "${workspaceFolder}/node_modules/@vue/cli-service/bin/vue-cli-service.js", "args": [ "test:unit" ], "console": "integratedTerminal", "internalConsoleOptions": "neverOpen" } Now this solution

问题 According to mocha-allure docs, if you want to use allure outside of before/beforeEach you should import the reporter directly. Or once added mocha-allure-reporter will create global allure object with the following API: https://github.com/allure-framework/allure-mocha https://github.com/allure-examples/mocha-allure-example/blob/master/test/simple.spec.js However I followed the example in the docs, but i get Cannot find name 'allure'. , when using it in either the before or afterEach. test

问题 I read all the related mocha "describe" is not defined posts but none of them seem to be suitable for my situation. I use meteor and installed the "mocha": "^3.5.0" package by npm I have created a /test folder in my meteor root directory. and a sample test mochatest.js var assert = require("assert"); // node.js core module describe('Array', function(){ describe('#indexOf()', function(){ it('should return -1 when the value is not present', function(){ assert.equal(-1, [1,2,3].indexOf(4)); // 4

问题 I'm trying to add some unit tests to a Visual Studio Code extension I'm developing. I've followed the recipe for setting up extension testing described here: https://code.visualstudio.com/api/working-with-extensions/testing-extension This recipe, however, doesn't show anything useful being done to actually test an extension, just the skeleton for getting set up to do so. For the testing I want to do, one of the first things I want to do is open a sample project . And that's where I get stuck.

问题 I am trying to wire the objects between 2 mocha test files. Here is my test1.js file which should export a variable once all the test cases are executed. var assert = require('assert'); var newUser = { email: "test@ex.com", name: "test@ex.com", password: "test@ex.com", confirmPassword: "test@ex.com" } var studentAcademicData = { marks: {}, activities: {} } var studentInterests = [] var testSummary = {}, loggedInUser = {}, avaialbleAssessment = {}, test = {}, interests = {}; var

问题 I like to use SuperTest to work with my auth system like this: const request = require('./valid_access_token')(require('supertest')); request(app) .get('/v1/bots') .valid_token() .expect('Content-Type', /json/) ... valid_token() would insert a valid access-token module.exports = function (Request) { const Token = require('../../../app/v1/models/loader')('token'); const UserFactory = require('../fixtures/user'); Request.prototype.valid_token = function() { return UserFactory.createAsync('user'

问题 I am trying to use nock to intercept/mock some HTTP traffic in my application for testing purposes. Our app authenticates to another one of our sites, and I need nock to imitate an HTTP 200 (with JSON data) and an HTTP 401 (with no data) to test behaviors when the user is or isn't logged in there (respectively). I have two tests which both work correctly when run alone, but if I run the entire test suite, one of them always fails. I realize that nock is shared state because it modifies how

问题 I'm trying to create a unit test for express node application. I want the configuration used for the test to be different than the one used in production, so I implemented the following. In my index.js , I load the configuration into the global variable like this: global.env = {}; global.env.config = require('./config/config'); // Create the server ... server.listen(3000); module.exports = server; In some other controller myController.js , I access the global variable like this var Config =

问题 I'm trying to test a function that calls the module cors . I want to test that cors would be called. For that, I'd have to stub/mock it. Here is the function cors.js const cors = require("cors"); const setCors = () => cors({origin: 'http//localhost:3000'}); module.exports = { setCors } My idea of testing such function would be something like cors.test.js describe("setCors", () => { it("should call cors", () => { sinon.stub(cors) setCors(); expect(cors).to.have.been.calledOnce; }); }); Any

问题 I'm trying to test a function that calls the module cors . I want to test that cors would be called. For that, I'd have to stub/mock it. Here is the function cors.js const cors = require("cors"); const setCors = () => cors({origin: 'http//localhost:3000'}); module.exports = { setCors } My idea of testing such function would be something like cors.test.js describe("setCors", () => { it("should call cors", () => { sinon.stub(cors) setCors(); expect(cors).to.have.been.calledOnce; }); }); Any