Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
easy-sql-tests
Advanced tools
Micro framework to execute tests for T-SQL logic in Node.js
$ npm install --save-dev easy-sql-tests
constructor to initialize easy sql tests module
dbConfig - mssql module database configuration
dbConfig.user
dbConfig.password
dbConfig.server
dbConfig.database
options - extra options for the module
options.cleanupQuery - (optional) query to be executed for cleanup() function
options.errorCallback - (optional) function callback to be executed if one of the prepQueries will fail to execute
function to open connection to the DB.
function to close connection to the DB.
function to execute cleanup query if it was passed into constructor
function to execute test steps
testSteps - array of testStep objects
testStep.storProcName - stored procedure name to be executed
testStep.args - object containing arguments for stored procedure
testStep.query - string containing query to be executed
testStep.assertionCallback - callback after query/storProc being executed. Put your assertions inside
testStep.queries - array of strings representing queries to be executed
property which contains MSSQL connection
property which contains DB Configuration
In order to create an instance of the module to use in your test follow this simple example:
var EasySQLTests = require('easy-sql-tests');
// ...
describe('my test suite', function() {
var easySQLTests;
var dbConfig = {
user: "USERNAME",
password: "PASSWORD",
server: "MY_SERVER",
database: "DB"
};
// ...
// runs before all the tests
before(function(done) {
easySQLTests = new EasySQLTest(dbConfig);
});
// ...
});
Most of the times you will need to open connection once and close by the end of your tests.
var EasySQLTests = require('easy-sql-tests');
// ...
describe('my test suite', function() {
var easySQLTests;
var dbConfig = {
user: "USERNAME",
password: "PASSWORD",
server: "MY_SERVER",
database: "DB"
};
// ...
// runs before all the tests
before(function(done) {
easySQLTests = new EasySQLTest(dbConfig);
easySQLTests.connectionOpen(function(error) {
if (error) {
console.log(error);
}
done();
});
});
// ...
// runs after all the tests
after(function() {
easySQLTests.connectionClose();
});
// ...
});
To ensure proper testing you might want to cleanup all temporarily generated data by your tests.
You can easily achieve that by defining a cleanupQuery and calling cleanup() function.
describe('my test suite', function() {
var easySQLTests;
// ...
// runs before all the tests
before(function(done) {
easySQLTests = new EasySQLTest(dbConfig, {
cleanupQuery: 'EXEC [test].[CLEANUP_LOGIC]'
});
easySQLTests.connectionOpen(function(error) {
if (error) {
console.log(error);
return done();
}
// cleanup before running tests
easySQLTest.cleanup(function(error) {
if (error) {
errorCallback(error);
}
done();
});
});
});
// ...
// runs after every test case
afterEach(function(done) {
cleanup(done);
});
// ...
});
it('My query test', function(done) {
var assertionCallback = function(error, recordsets) {
if (error) {
console.log(error);
return done();
}
// test that we returned a table
expect(recordsets.length).to.equal(1);
};
var testSteps = [
{
query: 'SELECT * FROM [MY_TABLE]',
assertionCallback: assertionCallback
}
];
easySQLTests.compileTest(testSteps, done);
});
it('My stor proc test', function(done) {
var assertionCallback = function(error, recordsets) {
if (error) {
console.log(error);
return done();
}
// test that we returned a table
expect(recordsets.length).to.equal(1);
};
var testSteps = [
{
storProcName: '[sp].[STOR_PROC]',
args: {
intArg: 1,
strArg: 'string'
},
assertionCallback: assertionCallback
}
];
easySQLTests.compileTest(testSteps, done);
});
If you need to run multiple steps to check that logic is correct then you can define multiple testSteps with their assertions.
it('Multiple steps inside the test', function(done) {
var assertionCallback = function(error, recordsets) {
if (error) {
console.log(error);
return done();
}
// asserions here
};
var assertionCallback2 = function(error, recordsets) {
if (error) {
console.log(error);
return done();
}
// asserions here
};
var testSteps = [
{
storProcName: '[sp].[STOR_PROC]',
args: {
intArg: 1,
strArg: 'string'
},
assertionCallback: assertionCallback
},
{
query: 'SELECT * FROM [MY_TABLE]',
assertionCallback: assertionCallback2
},
{
storProcName: '[sp].[STOR_PROC2]',
args: {},
assertionCallback: assertionCallback2
},
];
easySQLTests.compileTest(testSteps, done);
});
Some of the tests require initial setup of the data or state in your testing database.
it('Prep queries before test', function(done) {
var assertionCallback = function(error, recordsets) {
// ...
};
var testSteps = [
{
queries: [
"INSERT INTO [MY_TABLE] ([intVal],[strVal]) VALUES (1,'A');",
"INSERT INTO [MY_TABLE] ([intVal],[strVal]) VALUES (2,'B');"
]
},
// {
// another test step
// },
{
storProcName: '[sp].[STOR_PROC]',
args: {},
assertionCallback: assertionCallback
}
];
easySQLTests.compileTest(testSteps, done);
});
You might want to capture and execute special logic in case one of the prep queries will fail.
In order to do so errorCallback is executed whenever one of those queries fails.
describe('my test suite', function() {
var easySQLTests;
var errorCallback = function(error) {
console.error(error);
// DO SOME EXTRA LOGIC HERE
};
// ...
// runs before all the tests
before(function(done) {
easySQLTests = new EasySQLTest(dbConfig, {
errorCallback: errorCallback
});
});
// ...
});
A full blown example with open/close connection, cleanup query after each test will look the following:
var EasySQLTests = require('easy-sql-tests'));
describe('my test suite', function() {
var easySQLTests;
var dbConfig = {
user: "USERNAME",
password: "PASSWORD",
server: "MY_SERVER",
database: "DB"
};
var errorCallback = function(error) {
console.error(error);
};
var cleanup = function(done) {
easySQLTests.cleanup(function(error) {
if (error) {
errorCallback(error);
}
done();
});
};
// runs before all the tests
before(function(done) {
easySQLTests = new EasySQLTests(dbConfig, {
cleanupQuery: 'EXEC [test].[CLEANUP_LOGIC]',
errorCallback: errorCallback
});
easySQLTests.connectionOpen(function(error) {
if (error) {
errorCallback(error);
return done();
}
cleanup(done);
});
});
// runs after all tests in this block
after(function() {
easySQLTests.connectionClose();
});
// runs after every test case
afterEach(function(done) {
cleanup(done);
});
it('Different Vendors. Select all vendors', function(done) {
var assertionCallback = sinon.spy(function(error, recordsets) {
if (error) {
return console.error(error);
}
// we have data
expect(recordsets.length).to.not.equal(0);
});
var assertionCallback = function(error, recordsets) {
if (error) {
return console.error(error);
}
// we have data
expect(recordsets.length).to.not.equal(0);
// we have at least one row
expect(recordsets[0]).to.not.equal(0);
};
var testSteps = [
{
queries: [
"INSERT INTO [MY_TABLE] ([intVal],[strVal]) VALUES (1,'A');",
"INSERT INTO [MY_TABLE] ([intVal],[strVal]) VALUES (2,'B');"
]
},
{
storProcName: '[sp].[STOR_PROC]',
args: {
intArg: 1,
strArg: 'string'
},
assertionCallback: assertionCallback
},
{
query: 'SELECT * FROM [MY_TABLE]',
assertionCallback: assertionCallback
}
];
easySQLTests.compileTest(testSteps, done);
});
});
MIT license; see LICENSE.
(c) 2015 by Alexey Novak and Abdul Khan
FAQs
Micro framework to execute tests for T-SQL logic in Node.js
We found that easy-sql-tests demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.