Security News
NVD Backlog Tops 20,000 CVEs Awaiting Analysis as NIST Prepares System Updates
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
By Sarah Gooding - Nov 19, 2024
Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
Summary
just-test is a browser oriented tests runner strongly oriented to a TDD of a client side libraries, frameworks and components.
Why would we have another one?
just-test is strongly oriented to dev real time process. It has actually began as a code running playground during my next framework development and from there evolved to be a tests runner.
The main point is to provide a shortest path for a developer to execute newly written code in the browser, re-run it while benefitting from the browser's debug tools, fix the source and re-test the whole again just in a click of refresh.
just-test became to myself a truly TDD enabler as I'm using it in over a few dozens of libraries as of now. While being perfect tool for a librarires/components development, I'm still looking to see is and how could it be used to test a full web application.
Highlights:
- running tests in browser, no server needed, import/link your code (static files) and just test, literally TDD oriented
- re-running any test in browser ad-hoc - convenient for debugging and developing on the fly
- friendly UI on top of the page of the tests, allows immediatelly observe the behavior of the code and the test
- running tests from NodeJS via headless browser (currently: Chromium) to run in CI/CD automation
- generating test results report (format: xUnit)
- collecting coverage and generating report (formats: lcov)
- flexible yet simple ability to run tests in sync as well as async (default) manner
- in general, a lot of attention was paid to create simple and usable framework even for a not-so-simple cases, like asynchronous tests etc
Attention: the doc below is still in construction, more updates and detailed one will be published very soon!!! Meanwhile, the best way to actually see how the library should be used is it look onto its own tests in
testsfolder, and for CI/CD case -travis.ymlis a good start.
How it works - dev process
- start from writing a first lines of your next component or framework
- create a test file,
test.jsfor example - import into it the
just-testAPIs and get the suite object by thegetSuiteAPI - import the stuff your are working on and write some testing code using suite's
runTestAPI - create an empty
htmlfile,test.htmlfor example - import
test.jsinto it and open it in browser
Congratulations! Your test/s are running.
You see the results organized in suites in the just-test UI.
You may re-run any test from the UI, see the errors if any, status, duration etc.
CI readiness
just-test is not only a convenient work frame to develop and test the code at once, but also a CI automation ready tool.
Provided additional configuration file (full example may be seen here) just-test is able to:
- run your tests in CI in the following browsers: Chrome, Firefox (experimental); Edge Chromium will be added as soon as
puppeteerplatform will handle the download of the Edge's executable - creates report in the following formats:
xUnit - creates coverage report in the following formats:
lcov
Examples
Typical usage of the JustTest would involve two steps:
(A) referring to the framework and the tests in your html page;
(B) writing the actual test logic using an API (look example below and APIs).
index.html
<body>
...
<script src="just-test.js"></script>
<script src="test1.js"></script>
<script src="test2.js"></script>
</body>
test1.js
(function() {
'use strict';
var JT = window.Utils.JustTest, suite;
suite = JT.createSuite({ name: 'Suite object APIs' });
suite.addTest({ // options list described in API section below
name: 'JustTest namespace created okay'
}, function (pass, fail) {
if ('your internal validation logic fails') fail(new Error('error notice'));
if ('another fail') throw new Error('calling "fail" and throwing have the same effect');
pass();
});
suite.run();
})();
test2.js
(function() {
'use strict';
var JT = window.Utils.JustTest, suite;
suite = JT.createSuite();
suite.addTest(function (pass, fail) { // can skip the options, defaults will be used
...
});
suite.run();
})();
API
Framework object (default window.Utils.JustTest):
Test (JustTest.Test):
Suite (JustTest.Suite):
FAQs
JavaScript tests runner
The npm package just-test receives a total of 7 weekly downloads. As such, just-test popularity was classified as not popular.
We found that just-test 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.
Package last updated on 12 Jun 2020
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.
Related posts
Security News
Research
Malicious npm Package Exploits WhatsApp Authentication with Remote Kill Switch for File Destruction
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
By Kush Pandya - Nov 15, 2024
Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
By Sarah Gooding - Nov 15, 2024