npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@testx/keywords-postgres

v3.0.1

Published

Keywords to test postgres db with testx.io

Downloads

1,010

Readme

@testx/keywords-postgres

A library that extends testx with keywords for testing Postgres databases.

How does it work

From the directory of the art code install the package as follows:

npm install @testx/keywords-postgres --save

After installing the package you add these keywords to testx by adding the following line to your protractor config file:

testx.keywords.add(require('@testx/keywords-postgres'))

Example testx script:

- execute sql:
    sql: SELECT 1;
    expected result:
      - ?column?: 1
    save result to: saved
- execute sql:
    sql: SELECT 1;
    expected result: '{{saved}}'
- execute sql:
    sql: |-
      DROP TABLE IF EXISTS test;
      CREATE TABLE test (first varchar(20), second integer);
      INSERT INTO test(first, second) VALUES ('test1', 12), ('test2', 34);
      SELECT * FROM test;
    expected result:
      - first: test1
        second: 12
      - first: test2
        second: 34

Keywords

| Keyword | Argument name | Argument value | Description | | ---------------------- | ------------- | --------------- |------------ | | execute sql | | | Connect to the database, execute the SQL query/statement and optionally check the expected result and/or save it in the test context. | | | connection string | Connection string in the format of postgres://user:password@host:port/database.| Optional. If not set, the postgresConnectionString command line (or config file) parameter will be used.| | | sql | SQL query/statement to execute. | Required. | | | expected result | Expected result of the query. | Optional. It will be compared to the result of the query. The keyword will fail if they are different. The expected result should be a list of rows. Every row is an object (see the example). | | | save result to | varname | Optional. The name of a context variable, that will be used to save the result of the query. |