Security News
The Push to Ban Ransom Payments Is Gaining Momentum
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
serverless-test-plugin
Advanced tools
Readme
#Serverless Test Plugin
Simple Integration Test Framework for Serverless. This plugin is basically a
reimplementation of the run
command, validating a function's success. You can test all
functions of your component by passing the --all
option, and write the results into a
JUnit compatible reports XML by specifying --out <file-name>
.
This plugin is intended to run besides your regular Unit Tests such as Mocha, not as a replacement. It will solely validate that your functions have no compilation errors and can successfully run the provided event.json
. At this point there's no output validation other than checking for success, failure or a timeout (that is, if your Lambda code exceeds the specified timeout value).
Typically you want to run this plugin right before deploying your Lambda code.
The easiest example of running this plugin is
serverless function test --all
Note: Serverless v0.5.0 or higher is required.
###Configuration
This plugin can be configured on a function level by adding a test
definition to the custom
section in your s-function.json
.
Example:
"custom": {
"test": {
"skip": true
}
}
Available options are
skip
- boolean; skip this function from all testsevent
- string; name of the event JSON definition; defaults to event.json
###Usage
Test an individual function:
serverless function test <function>
To test all functions in the current path, invoke the plugin without any function name:
serverless function test
To test all functions in the project specify the --all
parameter:
serverless function test --all
You can also specify a stage and/or a region for your tests. If none is specified, the
first stage and region defined in your _meta
folder will be used:
serverless function test <function> --stage dev --region us-east-1
To test all functions and output results into a JUnit compatible XML, specify the
--out
parameter with a target file name:
serverless function test --all --out test_results/report.xml
Sometimes it is desirable to mock certain behavior in your code depending on whether it is running in a
test automation script or on an actual server. For this reason the serverless-test-plugin
introduces a dedicated environment variable SERVERLESS_TEST
:
if (process.env.SERVERLESS_TEST) {
console.log("This code runs as part of an integration test.");
}
else {
console.log("This code does NOT run as part of an integration test..")
}
FAQs
Serverless Test Plugin - Integration Tests for the Serverless Framework.
We found that serverless-test-plugin demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Application Security
New SEC disclosure rules aim to enforce timely cyber incident reporting, but fear of job loss and inadequate resources lead to significant underreporting.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).