🚀 DAY 5 OF LAUNCH WEEK:Introducing Webhook Events for Alert Changes.Learn more →
Socket
Book a DemoInstallSign in
Socket

test-n-vac

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install
Package was removed
Sorry, it seems this package was removed from the registry

test-n-vac

![3t transform header](./assets/3t-transform-header.png)

unpublished
latest
Source
npmnpm
Version
1.0.0
Version published
Maintainers
1
Created
Source

3t transform header

⚡ Test-N-Vac

Version License: MIT

The Test-N-Vac is a helper service that can be included in any javascript tests. The helper allows the tests to set up an architecture in the cloud that allows us to test our stacks from event in to event out.

🏠 3T Transform Homepage

Requirements

  • AWS Account with the ability to:
    • Put Events
    • Create a SQS Queue
    • Create an Rule
    • Create an Event Target

Installation

NPM:

npm install 

Yarn:

yarn add 

Usage

The usage examples include the addition on an env file, this is a json/javascript file that contains the following:

  • The stage that we are testing e.g ote. This is used to construct the eventbridge name.
  • The region that the service is in that we are testing.

In your tests import the library:

const { testNVacClient } = require('test-n-vac');

Create a client passing in the required values:

const helperClient = TestNVacClient({
  serviceName: "XXX",
  serviceSource: `integration.testing.${randomString}`,
  busName: `eventbridge-${env.Testing.STAGE_NAME}`, // The event bus name that the service is attached to 
  region: process.env.AWS_REGION
});

For more information on the client inputs, the code is documented

Before and after your test you need to spin up the testing architecture:

before(async () => {
  await helperClient.createTestArchitecture();
});

after(async () => {
  await helperClient.destroyTestArchitecture();
});

In the test, construct your event how you expect the rule to fire and call teh fire event function:

await helperClient.fireEvent(request, 'Event Topic');

Immediately following firing the event you can then run the following to check for resultant messages:

// We must call this one first as there is no way of telling what is the original event vs resultant events as they all match the same source
const initialEvent = await helperClient.getMessagesFromSQS();

const resultant Event = await helperClient.getMessagesFromSQS();

If you have multiple events you can call this multiple times.

It's possible to increase the number of messages received but that can be funky, its better to get them one at a time from the queue

Author

👤 3t Transform

Show your support

Give a ⭐️ if this project helped you!

FAQs

Package last updated on 16 Jan 2023

Did you know?

Socket

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.

Install

Related posts