Ok, so we don't really need these tests. I thought it would be a good way to create "action items" or "todos" so we could just fix them.
turns out that everything is an integration test....and there is not an issue in express.js
//TODO: something here is causing the integration tests to have a race condition...or something...connection issue.
if (process.env.NODE_ENV != 'test') {
app.use(express.session({
secret: 'MEAN',
store: new mongoStore({
db: db.connection.db,
collection: 'sessions'
})
}));
//connect flash for flash messages
app.use(flash());
}
Is this the problem that sometimes causes the users and talks tables in mongo to get dropped when grunt restarts the server following a controller change?
Ok, so we don't really need these tests. I thought it would be a good way to create "action items" or "todos" so we could just fix them.
turns out that everything is an integration test....and there is not an issue in express.js
//TODO: something here is causing the integration tests to have a race condition...or something...connection issue. if (process.env.NODE_ENV != 'test') { app.use(express.session({ secret: 'MEAN', store: new mongoStore({ db: db.connection.db, collection: 'sessions' }) }));