Skip to content

Latest commit

 

History

History
175 lines (131 loc) · 5.71 KB

README.md

File metadata and controls

175 lines (131 loc) · 5.71 KB
Raw

Contributors Forks Stargazers Issues MIT License


Logo

Halva Suite

⚠️ (Work In Progress)
Docs | Report Bug | Request Feature

🔥 ATTENTION 🔥
The module has been tested on Substrate 2.0.0-rc6 version, work on other versions is not guaranteed

w3f

About The Project

Inspired by Truffle

Halva is a toolchain for developing Decentralized Applications based on Substrate. It provides a high-level way to configure a development environment, interact with Substrate through external API and writing your test cases. Halva targets testing extrinsics via RPC calls this allows test Substrate (or clients compatible with Substrate RPC) as a black-box.

Built With

Halva uses Polkadot.js

Getting Started

  1. Install halva-cli
npm install -g halva-cli
  1. Configure your network in halva.js
const mnemonic = "bottom drive obey lake curtain smoke basket hold race lonely fit walk";

module.exports = {
  networks: {
    test: {
      mnemonic,
      ws: "ws://127.0.0.1:9944",
    },
  },
  polkadotjs: {
    provider: { },
    types: { }
   },
}

Usage

To run all tests, run:

halva-cli test  -p /path/to/tests/folder -n networkName

If you need help, use

halva-cli --help

To run REPL, simple run:

halva-cli console

Test global scope

You can use global variables provided by halva

describe('Halva test', () => {

  describe('test global', () => {
    it('Get global var', async () => {
        console.log(halva.accounts[0].address); // halva_account global var
    });
  });
});

Variable list:

  • halva.accounts - 10 Keyring pairs for tests
  • halva.polkadot - ApiPromise object of polkadot
  • alicePair - KeyringPair object of Alice
  • bobPair - KeyringPair object of Bob
  • charliePair - KeyringPair object of Charlie
  • networkName - Current network name
  • chainMetadata - Metadata object
  • mochaConfigure - Current Mocha configuration object

Assertions

Halva has its own assertion for working with extrinsic and contracts (in the future)

Assertion list:

  • passes(asyncFn, message, signer) - Error if extrinsic call fails
  • eventEmitted(asyncFn, eventName, section, message, signer) - Error if the event was not emitted in the transaction
  • eventNotEmitted(asyncFn, eventName, section, message, signer) - Error if the event was emitted in a transaction
  • fails(asyncFn, errorName, module, signer, message) - Error if the call ended without errors or with some other error

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Project Link: https://github.com/halva-suite/halva