6e2df8c64f
This PR brings assertOps and assertResources sanitizers to Deno.test() API. assertOps checks that test doesn't leak async ops, ie. there are no unresolved promises originating from Deno APIs. Enabled by default, can be disabled using Deno.TestDefinition.disableOpSanitizer. assertResources checks that test doesn't leak resources, ie. all resources used in test are closed. For example; if a file is opened during a test case it must be explicitly closed before test case finishes. It's most useful for asynchronous generators. Enabled by default, can be disabled using Deno.TestDefinition.disableResourceSanitizer. We've used those sanitizers in internal runtime tests and it proved very useful in surfacing incorrect tests which resulted in interference between the tests. All tests have been sanitized. Closes #4208 |
||
|---|---|---|
| .. | ||
| archive | ||
| bytes | ||
| datetime | ||
| encoding | ||
| examples | ||
| flags | ||
| fmt | ||
| fs | ||
| http | ||
| io | ||
| log | ||
| media_types | ||
| mime | ||
| node | ||
| path | ||
| signal | ||
| strings | ||
| testing | ||
| textproto | ||
| types | ||
| util | ||
| uuid | ||
| ws | ||
| manual.md | ||
| README.md | ||
| style_guide.md | ||
Deno Standard Modules
These modules do not have external dependencies and they are reviewed by the Deno core team. The intention is to have a standard set of high quality code that all Deno projects can use fearlessly.
Contributions are welcome!
How to use
These modules are tagged in accordance with Deno releases. So, for example, the
v0.3.0 tag is guaranteed to work with deno v0.3.0. You can link to v0.3.0 using
the URL https://deno.land/std@v0.3.0/
It's strongly recommended that you link to tagged releases rather than the master branch. The project is still young and we expect disruptive renames in the future.
Documentation
Here are the dedicated documentations of modules:
Contributing
deno_std is a loose port of Go's standard library. When in doubt, simply port Go's source code, documentation, and tests. There are many times when the nature of JavaScript, TypeScript, or Deno itself justifies diverging from Go, but if possible we want to leverage the energy that went into building Go. We generally welcome direct ports of Go's code.
Please ensure the copyright headers cite the code's origin.
Follow the style guide.