uvu-expect
aws-testing-library
uvu-expect | aws-testing-library | |
---|---|---|
1 | 3 | |
1 | 126 | |
- | - | |
1.8 | 8.5 | |
about 2 years ago | about 1 month ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
uvu-expect
-
Creating a Chai like assertion library using proxies
This setup works really good! But there’s some minor details: The assertion errors thrown by Chai are slightly different than those expected by uvu., so sometimes I’d get messages or extra details that are not so relevant to the test itself. Another issue is that I’d receive diffs comparing undefined to undefined when an assertion failed. As a proper developer with too much free time, I went ahead and decided to experiment with writing my own assertion library built on top of uvu’s assertions that I called uvu-expect. Here’s more or less how I did it.
aws-testing-library
-
Testing AWS Step Functions flows
First, I start the Step Function, and then I assert, using the aws-testing-library, whether the item was correctly saved into the Amazon DynamoDB.
-
Cloud Driven Development - Episode #001
aws-testing-library
-
Testing the Async Cloud with AWS CDK
When writing tests using something like aws-testing-library or sls-test-tools, we must have credentials to an AWS account that at least lets us send a few events and subscribe to or query the results in order to perform assertions. Depending on the stance of our organization about cloud access, this could be completely fine or it could be a never-gonna-happen dealbreaker. Often this kind of approach will be OK for a development environment, but it could be unlikely to fly in production.
What are some alternatives?
mocha - ☕️ simple, flexible, fun javascript test framework for node.js & the browser
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
tinyspy - 🕵🏻♂️ minimal fork of nanospy, with more features [Moved to: https://github.com/tinylibs/tinyspy]
sls-test-tools - Custom Jest Assertions for Serverless integration testing.
sveltekit-uvu-testing - SvelteKit uvu testing: how you can easily add fast component and utility function unit tests to your Svelte app using uvu with TypeScript.
jest-codemods - Codemods for migrating to Jest https://github.com/facebook/jest 👾
uvu-expect-dom - Dom assertions for uvu-expect built on top of jest-dom
cdk-eventbridge-socket - CDK construct that creates a WebSocket endpoint for you for any EventBridge rule you are interested in. (Built for debugging + testing )
uvu - uvu is an extremely fast and lightweight test runner for Node.js and the browser
qawolf - 🐺 Create browser tests 10x faster
cdk-async-testing-example
aws-cdk-rfcs - RFCs for the AWS CDK